kittinunf/fuel

The easiest HTTP networking library for Kotlin/Android

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 59 minutes ago
Added to GitGenius on September 14th, 2026
Created on June 4th, 2015
Open Issues & Pull Requests: 99 (+0)
GitHub issues: Enabled
Number of forks: 439
Total Stargazers: 4,648 (+0)
Total Subscribers: 74 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.4 days
Mean response time: 97.2 days
90th percentile: 216.2 days
Tracked items: 15

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 621 days
Stale 30+ days: 6
Stale 90+ days: 5

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • :gem: feature (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Fuel is an HTTP networking library for Kotlin and Android that uses Kotlinx Coroutines to simplify HTTP requests.

The library addresses the need for straightforward HTTP communication in Kotlin projects by providing suspend functions for all HTTP methods, allowing developers to make network calls with minimal boilerplate. It backs JVM requests with OkHttpClient and Apple platform requests with NSURLSessionConfiguration, abstracting away the underlying platform differences while maintaining access to platform-specific configuration options when needed.

Fuel suits developers building Kotlin or Android applications who want a lightweight networking solution without complex abstractions. It requires Java 8 or higher and Android 5 or later on mobile platforms. The tool is fully compatible with R8 out of the box; Proguard users may need to add configuration rules for Coroutines, OkHttp, and Okio, with additional rules required if using serialization modules like Moshi or Kotlinx Serialization. The library throws exceptions on network errors, so production applications must implement proper exception handling.

The project maintains active development with ongoing updates to its core branch, having transitioned from earlier versions while preserving a separate branch for legacy code. The tool provides straightforward integration with minimal configuration overhead for standard use cases, though developers should be aware that exception handling is mandatory rather than optional in production environments.