# retrofit Published articles for retrofit. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Starting Android at Khan Academy DevFeed: [Starting Android at Khan Academy]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-02-29T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Android](), [android-development](), [Development](), [Library](), [modules](), [ci](), [Mocking]() Tags: [android](), [android-development](), [development](), [engineering](), [libraries](), [mobile](), [mocking](), [module](), [modules](), [news](), [open-source](), [picasso](), [play-store](), [pre-commit](), [retrofit](), [test](), [tests]() ### AI overview Khan Academy describes its first Android app, launched in August 2015, and the engineering practices used to build it. The team adopted established Android and open-source libraries, separated Android-independent core code from the app module, and used fast JVM tests and continuous integration. ### Source excerpt By Ben Komalo The journey of a thousand miles... In March, 2015--almost 1 year ago to the day--we ... Read more ## Deconstructing OkHttp DevFeed: [Deconstructing OkHttp]() Original publisher: [Read original article]() Author: Jesse Wilson Published: 2026-05-22T12:00:00Z Content type: article Language: en Sources: [Public Object]() Topics: [Library](), [Network](), [Code](), [Kotlin](), [implementation](), [Cache](), [certificates]() Tags: [architecture](), [cache](), [certificates](), [https](), [implementation](), [kotlinconf](), [ktor](), [library](), [network](), [okhttp](), [performance](), [presentation](), [retrofit](), [testing]() ### AI overview A KotlinConf talk examines OkHttp's implementation rather than its basic usage, covering interceptor-based architecture, connection lifecycles, cache state machines, URL decoders, HTTPS testing certificates, performance, and extension mechanisms. ### Source excerpt I presented this at KotlinConf on May 22, 2026. Also available on slides, YouTube, and Speaker Deck. OkHttp is a popular library for making network calls. You might use it directly, or with Ktor, Retrofit, Coil, or gRPC. But this is not a talk on how to use OkHttp. Instead, ## Scalable API Response Handling Across Multi-Layered Architectures with Sandwich DevFeed: [Scalable API Response Handling Across Multi-Layered Architectures with Sandwich]() Original publisher: [Read original article]() Author: Jaewoong Eum Published: 2026-02-08T06:25:14Z Content type: tutorial Language: en Sources: [Stories by Jaewoong Eum on Medium]() Topics: [Android](), [Kotlin](), [API](), [kotlin-coroutines](), [Error Handling](), [Network]() Tags: [android](), [api](), [code](), [communication](), [coroutines](), [error-handling](), [exceptions](), [flow](), [kotlin](), [kotlin-multiplatform](), [mvi](), [mvvm](), [network](), [networking](), [presentation](), [responses](), [retrofit](), [viewmodel]() ### AI overview This tutorial explains how to handle Retrofit API responses, errors, and exceptions across multi-layered Android architectures such as MVVM and MVI. It presents Sandwich as a type-safe, composable approach and covers response handling, composition, merging, global error mapping, and Flow integration. ### Source excerpt Unsplash@picoftasty Modern Android applications commonly adopt multi-layered architectures such as MVVM or MVI, where data flows through distinct layers: a data source, a repository, and a ViewModel (or presentation layer). Each layer has a specific responsibility, and network responses must propagate through all of them before reaching the UI. While this separation produces clean, testable code, it introduces a real challenge: how do you handle API responses, including errors and exceptions, as they cross each layer boundary? Most developers solve this by wrapping API calls in try-catch blocks and returning fallback values. This works for small projects, but as the number of API calls grows, the approach creates ambiguous results, scattered boilerplate, and lost context that downstream layers need. You end up with ViewModels that cannot tell whether an empty list means "no data" or "network failure," repositories that swallow important error details, and data sources that repeat the same error handling pattern dozens of times. In this article, you'll explore the problems that emerge when handling Retrofit API calls across layered architectures, why conventional approaches break down at scale, and how Sandwich provides a type safe, composable solution that simplifies response handling from the network layer all the way to the UI. You'll also walk through the full set of Sandwich APIs, from basic response handling to advanced patterns like sequential composition, response merging, global error mapping, and Flow integration, each with real world use cases that show when and why you would reach for them. Retrofit API calls with coroutines Most Android projects use Retrofit with Kotlin coroutines for network communication. A typical service interface looks like this: https://medium.com/media/ebcba33386d664d1cf69a89234d2e22a/href The service returns a List directly. Retrofit deserializes the JSON response body and gives you the data. This works perfectly when the ## runBlocking in practice: Where it should be used and where not DevFeed: [runBlocking in practice: Where it should be used and where not]() Original publisher: [Read original article]() Published: 2025-09-01T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [runBlocking](), [Coroutines](), [Kotlin](), [kotlin-coroutines]() Tags: [android](), [async](), [await](), [best-practices](), [blocking](), [coroutines](), [dispatcher](), [guide](), [kotlin](), [pitfalls](), [retrofit](), [runblocking](), [workshop-learning-programming]() ### AI overview A practical guide to runBlocking in Kotlin Coroutines. It explains how runBlocking converts suspending calls into blocking calls, blocks the calling thread until completion, and creates a new coroutine hierarchy. The article discusses appropriate uses, code smells, and alternatives, including an Android Retrofit interceptor example. ### Source excerpt A comprehensive guide to using runBlocking in Kotlin Coroutines, including best practices and common pitfalls. ## Developing for Android with a local REST API server DevFeed: [Developing for Android with a local REST API server]() Original publisher: [Read original article]() Author: Sanskar Agrawal Published: 2022-12-26T09:17:38Z Content type: tutorial Language: en Sources: [Sanskar's Stuff]() Topics: [Android](), [REST API](), [Server](), [Development](), [HTTP](), [networking]() Tags: [android](), [backend](), [gson](), [http](), [local](), [networking](), [rest-api](), [retrofit](), [security](), [server]() ### AI overview This tutorial explains how to connect an Android app to a REST API server running locally on a development machine. It covers configuring endpoints, using the machine's local address and port, connecting an emulator or physical device, and enabling HTTP while avoiding that setting in production. ### Source excerpt When you're building an Android app, chances are that it'll be interacting with the internet in some way. More often than not, this is through the use of REST API. First, a refresher Ideally, you'd have a couple of base URLs, one for production usage... ## Basic Auth with OkHttp and Retrofit DevFeed: [Basic Auth with OkHttp and Retrofit]() Original publisher: [Read original article]() Author: James Shvarts Published: 2022-11-05T22:25:12Z Content type: tutorial Language: en Sources: [Android Blog - Mobile Dev Notes]() Topics: [Kotlin](), [Android](), [HTTP](), [API](), [Dagger](), [Library]() Tags: [android](), [api](), [auth](), [authentication](), [dagger-hilt](), [dependencies](), [http](), [json](), [kotlin](), [libraries](), [payload](), [request](), [retrofit](), [viewmodel]() ### AI overview A tutorial showing how to perform authenticated HTTP GET requests in a Kotlin Android project using Basic Authentication with OkHttp, Retrofit, Dagger/Hilt, and Moshi. ### Source excerpt Basic Auth example using OkHttp, Retrofit, Dagger in a Kotlin project ## Unconfined Enums Adapter for Moshi DevFeed: [Unconfined Enums Adapter for Moshi]() Original publisher: [Read original article]() Author: Isuru Rajapakse Published: 2022-05-11T12:08:49Z Content type: tutorial Language: en Sources: [Stories by Isuru Rajapakse on Medium]() Topics: [Kotlin](), [LineageOS](), [API](), [enum](), [interfaces]() Tags: [android](), [api](), [data-class](), [enum](), [enum-class](), [how-to](), [interfaces](), [kotlin](), [moshi](), [retrofit]() ### AI overview This tutorial presents a Kotlin pattern for handling previously unknown enum-like values from REST APIs with Moshi. It explains Moshi enum adapters, the unknown-value fallback, and an interface-based approach that preserves the server's raw value instead of mapping it only to a generic unknown value. ### Source excerpt If you wonder what an Unconfined Enum is, wonder no more because it is a thing I just made up. Enums by definition are confined, or finite. Therefore "unconfined enum" is really an oxymoron. Nevertheless, say you have this Fruit enum and want to map each value to an Android string resource. Kotlin's enum properties make this convenient enum class Fruit(@StringRes val stringRes: Int) { Apple(R.string.fruit_apple), Oranges(R.string.fruit_orange) } When we want to consume this enum from a Restful API with a Moshi converter, Moshi automatically generates the enum adapter for you, but if you want to customise the behaviour for whatever reason, you can do object FruitsAdapter { @ToJson fun toJson(type: Fruit): String = type.name @FromJson fun fromJson(name: String): Fruit = Fruit.values().first { it.name == name } } Happy days. Everything is working as expected. When things go bananascom.squareup.moshi.JsonDataException: Expected one of [Apple, Oranges] but was Bananas at path $ Good APIs don't break contracts. Not all APIs are good APIs, so some can break contracts. What do we do now? push out an update with added enum value and its string resource? Perhaps we can make use of EnumJsonAdapter's .withUnknownFallBack() enum class Fruit(@StringRes val stringRes: Int) { Apple(R.string.fruit_apple), Oranges(R.string.fruit_orange), Unknown(R.string.fruit_unknown) } Moshi.Builder() .add(KotlinJsonAdapterFactory()) .add(Fruit::class.java, EnumJsonAdapter.create(Fruit::class.java) .withUnknownFallback(Fruit.Unknown)) .build() This certainly stops the app from crashing, but what if we actually want to show the "bananas" that the API sends? you know, as a fail safe so that users wouldn't end up seeing "unknowns". Let's open up the Enums Enums are by definition finite. Enums are final by design. Enums can't be subclassed but they still can inherit interfaces. We will exploit this to create our "unconfined" enum interface Fruit { val name: String data class Unknown(override val name: ## Adventures in Tracking Upload Progress With OkHttp and Retrofit DevFeed: [Adventures in Tracking Upload Progress With OkHttp and Retrofit]() Original publisher: [Read original article]() Author: Márton Braun Published: 2021-12-10T16:00:00Z Content type: tutorial Language: en Sources: [zsmb.co]() Topics: [Android](), [SDKs](), [API](), [Code](), [implementation](), [Usability](), [User experience (UX)]() Tags: [android](), [api](), [coding](), [community](), [development](), [engineering](), [implementation](), [inclusive](), [networking](), [okhttp](), [retrofit](), [sdk](), [software](), [usability](), [ux]() ### AI overview This article explains how Stream's Android team refined file-upload progress tracking in the Stream Chat Android SDK. It presents an initial Retrofit and OkHttp callback-based implementation, discusses its usability issues, and describes a cleaner implementation using a custom OkHttp request body with progress callbacks. ### Source excerpt Tracking file upload progress can have some unexpected complexities. This article tells the story of how we refined our implementation of this feature in the Stream Chat Android SDK. ## Going Fully Multiplatform #1: Migrating your Android Project to Kotlin Multiplatform DevFeed: [Going Fully Multiplatform #1: Migrating your Android Project to Kotlin Multiplatform]() Original publisher: [Read original article]() Author: Isuru Rajapakse Published: 2021-10-21T13:24:07Z Content type: tutorial Language: en Sources: [Stories by Isuru Rajapakse on Medium]() Topics: [Kotlin Multiplatform](), [multiplatform](), [Kotlin](), [Android](), [iOS](), [Ktor](), [Web](), [Jetpack Compose](), [koin](), [RxJava](), [navigation]() Tags: [android](), [caching](), [dependency-injection](), [kotlin](), [kotlin-multiplatform](), [ktor](), [libraries](), [moshi](), [multiplatform](), [navigation](), [okhttp](), [retrofit](), [rxjava]() ### AI overview The article describes migrating an Android-only application to Kotlin Multiplatform. It compares the existing Android stack with a planned multiplatform stack targeting Android, JVM, iOS, and Web, including changes to networking, serialization, caching, dependency injection, asynchronous plumbing, navigation, and UI. ### Source excerpt Earlier this year I started a mission to start migrating one of our long-lasting Android-only apps to Kotlin Multiplatform to go beyond just Android. This is the story of how that went. Migration from Only-Android to Kotlin Multiplatform!The Android stack This is our current "stack" our android app was set up as follows Targeting Android SDK API 23 or above, we had a few libraries to help us out. The Android-only stack OkHttp for Networking Retrofit for.. also Networking Moshi for serialisation Okio for caching Koin for Dependency Injection/ Service Locator Plumbing with RxJava Navigation with Conductor Imperative UI with Android Views written in XML The Multiplatform stack To go beyond just Android, I had to make some hard decisions to step outside of the comfort zone that we've been so fond of To target Android, JVM, iOS and Web -- we will be making use of The Multiplatform stack Ktor for Networking Kotlin Serialisation for.. serialisation Caching with SQLDelight Koin for Dependency Injection (that one can stay) Plumbing with Coroutine Flows Navigation with Decompose Declarative UI powered with Jetpack/Jetbrains Compose That's the plan! In the next few articles, we'll take a look at each step in more detail. Before jumping on to that -- I want to take a close look at how we can fully modularise a Kotlin Multiplatform project with Going Fully Multiplatform #2 Modularising your Kotlin Multiplatform Project! ## Converting LiveData to Flow: Lessons learned DevFeed: [Converting LiveData to Flow: Lessons learned]() Original publisher: [Read original article]() Author: Chao Zhang Published: 2021-04-03T01:13:26Z Content type: tutorial Language: en Sources: [Stories by Chao Zhang on Medium]() Topics: [Kotlin](), [kotlin-coroutines](), [Android](), [Coroutines](), [App]() Tags: [android](), [android-app-development](), [coroutines](), [flow](), [kotlin](), [kotlin-coroutines](), [lifecycle](), [livedata](), [network](), [retrofit](), [rotation](), [viewmodel]() ### AI overview This tutorial examines lessons from converting Kotlin Flow to LiveData with Flow.asLiveData() in an Android app. It explains why flow collection may be re-executed after screen rotation and identifies creating a new LiveData instance instead of preserving it as a property as the bug causing recollection. ### Source excerpt Photo: Robert Lukeman from Unsplash Android KTX provides opinionated methods, such asFlow.asLiveData(), facilitating using Kotlin Coroutines in Android Architecture Components. Make sure to understand their behaviors underneath before using them! The official documentation on Kotlin coroutines on Android is quitewell-written, while there are numerous article posts covering the basics. In this story, we will focus on the lessons learned when using these extension methods, usingFlow.asLiveData() as an example. Setup Let's start with a concrete example using the orthodox Android App Architecture: Repository + ViewModel + Fragment https://medium.com/media/a59f3702376fe64d61dd5c3dd72c9c15/href RedditService is a simple Retrofit service. We also added logging statements inside the flow collecting block. https://medium.com/media/a904400508a241bae454d44e0f01a9b9/href We use Flow.asLiveData() to convert the flow into a LiveData. https://medium.com/media/97cb5995c53c5d86606a371ef905d25d/href In the fragment layer, we added logging statements for the fragment lifecycle calls and used Thread.sleep(500)to simulate complex layout inflation. Lesson I: Flow collection is re-executed after rotating the screen When we run the app, it looks fine. However, after rotating the device screen to recreate the fragment, we can observe more logs like flow running... indicating the flow is executed. 2021-04-02 16:41:32.246 I: Fragment onCreate... 2021-04-02 16:41:32.247 I: Fragment onCreateView... 2021-04-02 16:41:32.754 I: Fragment onStart... 2021-04-02 16:41:32.755 I: flow running... 2021-04-02 16:41:32.756 I: Fragment onResume... 2021-04-02 16:41:33.309 I: Observer called... That is weird! The original intention of ViewModel is to persist data that can survive UI recreation. After we rotate the device screen, the data should be retrieved from the storage. Contrarily, what we saw is that the data is fetched again from the service, which may cause unnecessary network calls or UI flic ## Using Retrofit and Alamofire with Kotlin Serialization on Kotlin Multiplatform DevFeed: [Using Retrofit and Alamofire with Kotlin Serialization on Kotlin Multiplatform]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2020-12-10T00:00:00Z Content type: tutorial Language: en Sources: [Posts on Marco Gomiero]() Topics: [Kotlin Multiplatform](), [Kotlin](), [Mobile](), [Android](), [iOS](), [Library](), [API]() Tags: [android](), [api](), [backend](), [kmp](), [kotlin](), [kotlin-multiplatform](), [kotlin-serialization](), [ktor](), [library](), [mobile](), [network](), [rest](), [retrofit](), [serialization](), [swift]() ### AI overview This tutorial explains how to use Retrofit on Android and Alamofire on iOS in a Kotlin Multiplatform Mobile application while sharing DTO definitions and Kotlin Serialization-based deserialization across the KMP module and mobile clients. ### Source excerpt If you are starting a project with Kotlin Multiplatform and you want to share the network layer, the best way to go is definitely with Ktor. But if you don't want to share the entire network layer but maybe only the DTOs? There could be many reasons for wanting this. Maybe you are starting to integrate Kotlin Multiplatform (I'll call it KMP in the rest of the article) into an existing project and the work for sharing the entire network layer is simply too much. ## Repository Pattern: Properly Organizing Your Data Layer DevFeed: [Repository Pattern: Properly Organizing Your Data Layer]() Original publisher: [Read original article]() Author: Adam McNeilly Published: 2019-05-20T00:00:00Z Content type: tutorial Language: en Sources: [Android Essence]() Topics: [App](), [Code](), [Programming](), [API](), [GraphQL]() Tags: [api](), [code](), [developers](), [graphql](), [how-to](), [implementation](), [programming](), [retrofit](), [viewmodel]() ### AI overview This tutorial explains the Repository Pattern for organizing an application's data layer. It shows how separating data access from a ViewModel or Presenter can keep those classes focused on requesting data while allowing the underlying source to change, such as between a Retrofit service, GraphQL API, or local database. ### Source excerpt How to properly architect your application is a concern we as developers constantly face. There's unfortunately no one size fits all answer to it, and sometimes we don't even know where to begin. I've learned along my Android journey that the answer can also vary depending on what portion of your app you're trying to organize. Of course, you might say, it depends. When it comes to your data layer, though, there are some really good tips on how to write clean, maintainable code. One of them is the Repository Pattern, and I'd like to provide a quick walk through of what it is and why it's important. ## Retrofit meets coroutines DevFeed: [Retrofit meets coroutines]() Original publisher: [Read original article]() Author: Márton Braun Published: 2019-02-15T22:00:00Z Content type: tutorial Language: en Sources: [zsmb.co]() Topics: [Coroutines](), [kotlin-coroutines](), [REST API](), [API]() Tags: [android](), [cancellation](), [coroutines](), [demo](), [exception](), [gson](), [implementation](), [kotlin](), [kotlin-coroutines](), [marton-braun](), [networking](), [rest-api](), [retrofit](), [serialization](), [zsmb](), [zsmb-co](), [zsmb13](), [zsmbco]() ### AI overview This tutorial explains how to use Retrofit 2.6.0 or later with Kotlin coroutines. It demonstrates coroutine-based API calls, Gson serialization, exception propagation, cancellation, and response-handling variants using the SpaceX REST API. ### Source excerpt Retrofit's coroutine support has been a long time coming, and it's finally coming to completion. Take a look at how you can use it to neatly integrate networking into an application built with coroutines. ## Reactive Pipelines in Action DevFeed: [Reactive Pipelines in Action]() Original publisher: [Read original article]() Author: Artur Dryomov Published: 2018-11-07T00:00:00Z Content type: article Language: en Sources: [Artur Dryomov]() Topics: [reactive](), [Functional programming](), [Programming]() Tags: [architecture](), [connectivity](), [data](), [functional-programming](), [network](), [pipelines](), [programming](), [reactive](), [retrofit](), [state](), [stream](), [triggers](), [ui]() ### AI overview An exploration of reactive programming and functional-reactive pipelines, describing how producers and consumers can be connected into consistent event flows. Examples include network connectivity changes and refresh actions triggering requests, state updates, and UI redraws within a multitier architecture. ### Source excerpt Human beings are reactive by nature -- fortunately or not. The reason is mostly physiology. The dopamine hormone helps us to feel comfortable and secure while we do familiar things. Eating a sandwich sounds and feels far better than gardening, doesn't it? Essentially it is a fight between psychology (the mind, proactive actions) and physiology (the body, reactive actions). The same thing happens in CS. Object-oriented programming (OOP) is the king of the hill and functional programming (FP) is on the outskirts. Well, it is this way because the OOP is more comfortable for the majority. We, as a society, made it this way. The educational system includes a mandatory OOP course and rarely there is an FP one. And then there is reactive programming which forms a wild beast called functional-reactive programming (FRP)... ## Band-aiding legacy networking libraries with Retrofit and OkHttp DevFeed: [Band-aiding legacy networking libraries with Retrofit and OkHttp]() Original publisher: [Read original article]() Author: Saket Narayan Published: 2018-04-30T09:22:05Z Content type: tutorial Language: en Sources: [Saket Narayan]() Topics: [legacy](), [networking](), [HTTP](), [Library](), [API](), [MQTT](), [Code]() Tags: [android](), [apis](), [http](), [legacy](), [libraries](), [networking](), [okhttp](), [refactor](), [retrofit]() ### AI overview This tutorial explains how to use Retrofit with a legacy networking library by adding an OkHttp interceptor that redirects network requests to the existing library. It also describes exposing nonstandard data sources through Retrofit converters. ### Source excerpt When Uncommon was brought in to refactor a big legacy app last year, we found ourselves in a strange situation. Our client was maintaining a common library for handling networking -- HTTP, FCM, MQTT -- across all apps under their brand. This library (let's call it SadLibrary) had an API that was badly designed and dated, but not using [...] The post Band-aiding legacy networking libraries with Retrofit and OkHttp appeared first on Saket Narayan. ## Opinion, should we prefix JAX-RS Path value with a slash ? DevFeed: [Opinion, should we prefix JAX-RS Path value with a slash ?]() Original publisher: [Read original article]() Author: brice.dutheil@gmail.com (Brice Dutheil) Published: 2018-02-20T00:00:00Z Content type: opinion Language: en Sources: [The Coffee Workshop]() Topics: [HTTP](), [client](), [browsers](), [Linux]() Tags: [browsers](), [http](), [linux](), [okhttp](), [opinion](), [retrofit](), [server](), [standards]() ### AI overview This opinion examines whether JAX-RS path annotations should use a leading slash. It explains that JAX-RS treats paths with and without leading or trailing slashes similarly, while Retrofit and OkHttp resolve a leading slash as an absolute URL path, making slash placement semantically significant on the client side. ### Source excerpt In the past months I have been using extensively the infamous HTTP client OkHTTP, I have been impressed by the will power of committers to respect HTTP standards. My co-workers which have various degrees of knowledge and experience in different language ecosystem work on a server-side application with some JAX-RS endpoints, and this question arose: ## Doppl Sample Update - Kevin Galligan DevFeed: [Doppl Sample Update - Kevin Galligan]() Original publisher: [Read original article]() Published: 2017-10-04T15:00:55Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Android](), [RxJava](), [Gradle](), [Kotlin](), [Xcode](), [Objective-C]() Tags: [android](), [android-library](), [architecture](), [built-by-touchlab](), [code-sharing](), [dependencies](), [gradle](), [java](), [kotlin](), [objective-c](), [retrofit](), [rxjava](), [update](), [version](), [xcode]() ### AI overview A progress update on Touchlab's Doppl libraries and sample apps. The update covers compatibility work for J2objc 2.0.4, redeployed libraries, Party Clicker, reactive Room architecture code, and planned work on RxJava 2, Retrofit 2, Xcode support, the Gradle plugin, Architecture Components, and Kotlin. ### Source excerpt We're going through and updating Doppl libs & sample apps. For the next few months, we'll be working with 2.0.4 and locking down the libraries and versions. ## How to use Retrofit on android with Kotlin (KAD 21) DevFeed: [How to use Retrofit on android with Kotlin (KAD 21)]() Original publisher: [Read original article]() Published: 2017-04-18T00:00:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [Android](), [Kotlin](), [API](), [Library](), [Gradle](), [Gson](), [Java]() Tags: [android](), [api](), [build](), [gradle](), [gson](), [how-to](), [java](), [kotlin](), [okhttp](), [retrofit]() ### AI overview A Kotlin tutorial showing how to integrate Retrofit 2 into an Android application for making LastFM API requests. It covers Gradle dependencies, OkHttp logging, Gson conversion, request interfaces, service initialization, and making requests with extension functions. ### Source excerpt Everything Android, Kotlin and other random topics ## How a JDK Throwable API Design Issue Caused Bugs in RxJava and Retrofit DevFeed: [How a JDK Throwable API Design Issue Caused Bugs in RxJava and Retrofit]() Original publisher: [Read original article]() Author: P-Y Ricau Published: 2016-11-02T19:47:30Z Content type: tutorial Language: en Sources: [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [API](), [Exception](), [debugging](), [debug](), [Code](), [LineageOS]() Tags: [android](), [api](), [code](), [debugging](), [engineering](), [exception](), [jdk](), [retrofit](), [rxjava]() ### AI overview This technical write-up explains how an API design issue in the JDK Throwable class caused bugs in RxJava and Retrofit when RxJava assembly tracking was enabled. It traces the resulting exception behavior through logs and source code. ### Source excerpt Last week, we found an interesting API design issue in the Throwable class of the JDK that led to bugs in RxJava and Retrofit. This is a... ## Retrofit 2.0 Samples DevFeed: [Retrofit 2.0 Samples]() Original publisher: [Read original article]() Author: Chris Hager Published: 2015-10-12T00:00:00Z Content type: tutorial Language: en Sources: [Chris Hager]() Topics: [Library](), [API](), [client library](), [Java](), [Gson](), [HTTP](), [Android](), [Gradle](), [JSON](), [GitHub]() Tags: [android](), [api](), [articles](), [client-library](), [github](), [gradle](), [gson](), [java](), [json](), [retrofit]() ### AI overview A tutorial on using Retrofit 2.0 beta to consume HTTP APIs in Java and Android applications. It covers project setup with Gradle, JSON serialization with Gson, API client definitions, and sample GET and POST requests against httpbin.org. ### Source excerpt This post is about using Retrofit 2.0 (beta) to consume HTTP based APIs. Retrofit is a great and popular API client library for Java (and by extension also for Android) developed by Square. Here's a few links to start things off: Retrofit Homepage Retrofit Source on Github Retrofit Javadoc Blog post about Retrofit 2.0 Source code with samples for this post is available on Github. Retrofit makes it easy to develop API clients by describing API endpoints and the results like this: ## Easy HTTP Requests with Retrofit DevFeed: [Easy HTTP Requests with Retrofit]() Original publisher: [Read original article]() Author: Square Engineering Published: 2013-05-13T16:03:00Z Content type: tutorial Language: en Sources: [Jake Wharton](), [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [HTTP](), [Application Development](), [API](), [Library](), [Open Source](), [Java](), [GitHub](), [GitHub API]() Tags: [api](), [application-development](), [code](), [declarative](), [development](), [engineering](), [github](), [http](), [implementation](), [java](), [library](), [network](), [open-source](), [request](), [responses](), [rest](), [retrofit]() ### AI overview This tutorial introduces Retrofit, Square's open source library for making HTTP requests through declarative, type-safe interfaces. It demonstrates calling GitHub's contributors API for the OkHttp project and explains how annotations, method arguments, and RestAdapter map interfaces to network requests. ### Source excerpt A declarative, type-safe REST client.