// the find
amitshekhariitbhu/Fast-Android-Networking
🚀 A Complete Fast Android Networking Library that also supports HTTP/2 🚀
A Java library for Android that wraps OkHttp and Okio in one fluent request builder covering GET and POST, multipart upload, file download, bitmap loading, and optional JSON or RxJava parsing. It suits Android apps that want a single callback-style API over OkHttp without writing their own plumbing, though most new projects would now reach for Retrofit with coroutines.
- A per-request OkHttpClient override through setOkHttpClient lets you change timeouts or interceptors for one call without rebuilding the shared client. Cancellation works by tag, and forceCancel bypasses the percentage threshold when you need a hard stop.
- Download cancellation has a percentage threshold, so a file that is nearly finished completes instead of being thrown away when the screen closes. That is a sensible default for flaky mobile connections.
- AnalyticsListener reports time taken, bytes sent and received, and whether the response came from cache. ConnectionClassManager buckets bandwidth into quality levels you can branch on, which helps when you want smaller payloads on slow links or need to debug a request in the field.
- The last push was 2026-02-05, and the only install path shown is JitPack coordinates pinned to 1.0.4. Your build then depends on JitPack building that tag, and the README mentions no Maven Central artifact.
- The API is callback-only. Every call ends in an anonymous listener class, and the README shows no suspend or Flow wrapper, so Kotlin code ends up adapting each call by hand. That is the main reason to pick Retrofit or Ktor for new work.
- The README lists a known bug where the GZIP request interceptor breaks multipart upload progress. It also claims Okio means no GC overhead, which overstates things: Okio reduces copying and allocation but does not remove GC pressure from the request path.
- Every example in the README points at a herokuapp demo host, and Heroku retired its free tier in 2022. The examples, and probably the androidTest suite, need their endpoints replaced before they mean anything. The pitch also leans on the Marshmallow HttpClient removal and Android 2.3 support, which are old reasons, since Retrofit, Coil or Glide, and coroutines now cover the same ground.