guide-to-kotlin VS Retrofit

Read through https://github.com/Zhuinden/guide-to-kotlin/wiki and you'll know Kotlin. That, and you can also check the collection APIs which are pretty much the best thing in Kotlin compared to Java.

I would recommend learning Kotlin for Android though, it does help. I wrote this guide https://github.com/Zhuinden/guide-to-kotlin/wiki but you can also look at this video https://www.youtube.com/watch?v=wuiT4T_LJQo

I wrote this guide for Java => Kotlin a few years ago, other than me not adding coroutines it still holds: https://github.com/Zhuinden/guide-to-kotlin/wiki

Check this guide by me to learn Kotlin: https://github.com/Zhuinden/guide-to-kotlin/wiki

but you can read through https://github.com/Zhuinden/guide-to-kotlin/wiki and you will know what you need to know for Kotlin basics (except coroutines, then you watch https://www.youtube.com/watch?v=6P20npkvcb8 )

I wrote https://github.com/Zhuinden/guide-to-kotlin/wiki a few years ago for people who know Java and don't know Kotlin, I've heard many positive feedback for how simple it is to transition from Java to Kotlin once reading through it.

you should probably look into Kotlin (see https://github.com/Zhuinden/guide-to-kotlin/wiki and/or https://www.youtube.com/watch?v=wuiT4T_LJQo ),

You actually can just read through https://github.com/Zhuinden/guide-to-kotlin/wiki and you'll know how to use kotlin lo

I wrote this guide a while ago specifically to cover this kind of migration https://github.com/Zhuinden/guide-to-kotlin/wiki it should be fairly no-nonsense and I've heard people like it (they said it helped them).

I didn't need to because by the time it came out I already knew Kotlin, personally I wrote this https://github.com/Zhuinden/guide-to-kotlin/wiki

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.