A type-safe HTTP client for Android and the JVM (by square)

Retrofit Alternatives

Similar projects and alternatives to Retrofit based on common topics and language
  • GitHub repo guide-to-kotlin

    [GUIDE] This tutorial assumes all you know is Java, but you want to learn Kotlin.

  • GitHub repo tutorial-push-notifications-with-firebase-api-v2

  • Scout

    Get performance insights in less than 4 minutes. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.

  • GitHub repo Dropwizard

    A damn simple library for building production-ready RESTful web services.

  • GitHub repo Feign

    Feign makes writing java http clients easier

  • GitHub repo Rapidoid

    Rapidoid - Extremely Fast, Simple and Powerful Java Web Framework and HTTP Server!

  • GitHub repo springdoc-openapi

    Library for OpenAPI 3 with spring-boot

  • GitHub repo Elide

    Elide is a Java library that lets you stand up a GraphQL/JSON-API web service with minimal effort.

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better Retrofit alternative or higher similarity.


Posts where Retrofit has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-02-19.
  • Integrating Push Notifications with Firebase Java API | 2021-02-19
    ‍ We will now create the interface for the API call. We will be using the Retrofit library in Android to make the API calls. Retrofit is a lightweight and very easy-to-use HTTP client available for Android and Java. All you need to start using it is to add the dependency in the build.gradle file. You can read more about it on their official website given above, to get a better picture of the library. It is always a good practice to read the documentation whenever using a library for your application.
  • Hilt - okhttp scopes, variants and overall app performance ?
    Let's move to Retrofit. From a performance point of view, I'd say it's better to keep one instance per service rather than one instance per feature. Retrofit relies on annotations and reflection to parse them. Since this operation has some cost, the result is cached. If you keep creating new instances as you explained, you don't use this cache across multiple features, but each feature will have to build its own cache. It's also true that the application will spend most of the time of the operation doing some I/O.
  • Using Java for Android app development in 2021
    Looks pure-JVM to me


Basic Retrofit repo stats
7 days ago

square/retrofit is an open source project licensed under Apache License 2.0 which is an OSI approved license.