groupie VS Retrofit

I've been hearing for 2 years that the primary benefit of Compose is that you "no longer need to write a RecyclerView.Adapter", not realizing that you can use something like Groupie and effectively turn RecyclerView into adapter.setItems(listOf(Item1(), Item2())) just like in Compose.

https://github.com/lisawray/groupie Maybe it can help for your purposes

Been using RecyclerView and haven't written an adapter in a very long time because you can abstract it away

Technically you can also use a library that hides this from you, for example I tend to use https://github.com/lisawray/groupie with BindableItem

There are also libs that help you handle this, there's gorupie here https://github.com/lisawray/groupie and also Expandable RV here https://github.com/thoughtbot/expandable-recycler-view

RecyclerView utilities: Epoxy, Groupie, AdapterDelegates

I think Groupie is nice, although Google seems to think of each Adapter being able to describe itself "as an item view type". So you could build "multiple item view types" using a concatAdapter of N ListAdapters. Tricky.

We've been using https://github.com/lisawray/groupie/ which offers a common GroupAdapter for all Items, so that each RecyclerView Item type can be encapsulated in its own class, Item.

Don't write adapters or view holders for RecyclerView, use something like Groupie.

from this point on, I will assume, you have a basic understanding of Retrofit. To get the most out of this tutorial I would actually suggest you have a retrofit client already implemented in your application.

Now you might think that in order to make the request we are going to use Retrofit but in reality we are going to be sending out an implicit intent like so:

This particular blog post will be us building on the information from the previous blog post and using the authorization code from the GitHub OAuth API in combination with Retrofit. To finally get a access token, which allows us to make requests to the API on a behalf of a user.

Hey HN!

If you're a fan of Swift you may have noticed that with WWDC 2023 came the (beta) release of macros. They're super powerful and expressive!

I've been wishing Swift had a [Retrofit](https://square.github.io/retrofit/) style API definition library for years, and with macros it seemed like this was now possible.

I'd like to show you all Papyrus, a library that turns your APIs into type-safe Swift protocols.

Would love to get your feedback.

https://github.com/joshuawright11/papyrus

When it comes to consuming APIs I can definitely recommend Retrofit. Hopefully that's enough to get you started on where to look!

For Android you should use a more mobile friendly framework like Retrofit or if you use Kotlin you can use the multi-platform Ktor library with it's client module

for example https://square.github.io/retrofit/ have mentioned it in at the bottom. Similarly there maybe other rules for other dependencies. Usually I search the missing classes error in google and find some proguard rule for it.

Retrofit in combination with OkHttp for fetching data from server (which hopefully already exists)

The first get request is to retrieve a list of objects and the second one is to get a single one. You can read more about RetroFit here.

So I've been playing around with search.maven.org and perhaps I'm not quite understanding it. For example, if I look for Retrofit I'm not seeing anything that resembles retrofit above https://central.sonatype.dev/search?q=Retrofit.