Retrofit is an wonderful network library to deal with api's and Rx java can be used to do async task operations effectively. Using retrofit with RxJava will results in seamless network calls in mainthread. Retrofit can be used without RxJava, though to perform huge api calling and to do api calls in background, they pair a better combination.
An android asynchronous http client based on
DownZ is an HTTP library that boosts networking in Android apps and makes it significantly easier and faster.
An android restful api/networking library using okhttp library as backbone.
An android api client based on Retrofit2 and RxJava2.
Star DNS Changer is a DNS Changer application.
A Library to provide Http post request easily.
A library, based on Google's Volley library, that makes android HTTP requests easier and requires no boiler plate code that volley usually needs.
CustomVolleyRequester is used to make developer's lives easier. Making HTTP calls is a common requirement for most apps and we believe that using it does not require the developer to repeat the initialization process each time. With CustomVolleyRequester, all you need to do is specify the request fields needed for your request, give it the desired model class to be returned, and the library will deliver your model.
A network abstraction layer over Volley, written in Kotlin and inspired by Moya for Swift.
A simple to use networking library that makes it easy to retrieve data from REST APIs. Also provides a mock function to build/test your app without actually making the http request.
Let Retrofit support multiple baseUrl and can be change the baseUrl at runtime.
Android Simple Network Library for HTTP and Image Requests with cool features implemented with Simple Demo using some Material Design UI Elements.
This lightweight library makes it easy to use HTTP requests. Although the purpose is to make the use of Json data easy, it also allows to retrieve the server response using other formats, XML and TEXT.
SimpleHttp is a library that will help you to make Http Restful in easy way for Android.
A library which helps to create Retry Policy when using Retrofit 2.0 for API calls.
Convenient wrapper library to perform network queries using Retrofit and Android Priority Job Queue (Job Manager).
By default OkHttp3 provides only in-memory implementation of CookieStore thus all the cookies won't survive for a long term changes. This is persistent cookie storage based on SharedPreferences.
NetSugar is an Android + AOP framework. It was a way of Aspect-Oriented Programming with AspectJ(ApsectJ 5) on Android. It is an easy-use and lightweight framework to check network state.
NoNet is an Android library for monitoring network connectivity.
OkHttp-Stats is an android library built on top of OkHttp3, which is responsible for intercepting all the network calls and for calculating network stats such as the average network speed of the user.
This is more of an analytical tool which can be used to track the success and error response logs.
Can be plugged in to any app which uses okhttp in their networking stack.
TrustKit Android is an open source library that makes it easy to deploy SSL public key pinning and reporting in any Android App.
A persistent CookieJar implementation for OkHttp 3 based on
Android Http Client is a small library to make requests to any internet service simple and practical way. You can implement multiple interfaces for the management of the responses. It also includes interfaces for managing upload and download of files.
Connecting to webservices from Android devices is now easy. The sending and receiving of data to and from webservices can be customized in a desired way and can be done by a single method.
Pacman is a lightweight and easy to use Parallel API Calls Manager.
You might need to execute multiple API calls at once to speed up loading of your app and proceed only when you have the data from all the required API calls. Managing this using normal boolean flags or such methods can be a pain and can result to incorrect data or behaviour.
That is where Pacman comes to play, as you just set it up with some CallGroup, make the API calls and then update Pacman as and when you get a response from the call.
After all the calls are done processing, Pacman will fire a callback to an attached listener (which you have set up) and then you have do whatever processing you needed to do after the calls were done.