snapdroid VS Retrofit

It's all done with Mopidy + Snapcast. Mopidy has various frontends, but the Iris web frontend supports Snapcast and can be controlled from any web-capable device; it can be used to assign/change device groups, assign certain streams to certain groups (you can have multiple sources playing on multiple devices/groups and control them from there), etc. I also used the Snapdroid app, which will allow you to adjust things like latency, individual device volumes and stream volumes, etc on your phone or tablet. Beyond that, you can integrate Home Assistant and pretty much get it to act however you want, including being fully controlled via voice on both Google and Amazon (and ultimately Cortana, ick) platforms. Of course that takes some setting up that some wouldn't consider "easy", so YMMV.

* Server running mopidy [1] with all your audio loaded up on it and connected to Spotify.

* Install the Iris plugin for UI [2] on server

* Install snapcast [3] server on the audio server and snapcast client on raspberry pi's near all stereos you want to pipe audio into

* Put bookmarks to the Iris page on all family member's phone home screens.

* Add the snapdroid app [4] to each phone so people can adjust volume of each stereo and also play audio on their phone (or anything it's bluetoothed into)

[1] https://mopidy.com/

[2] https://mopidy.com/ext/iris/

[3] https://github.com/badaix/snapcast

[4] https://github.com/badaix/snapdroid

The Snapdroid app for Android is pretty basic. AFAIK there still isn't a UI for iOS.

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.