MonetCompat VS OkHttp

There isn't an official way to do this, you'd have to use a third party re-implementation of Monet (the colour library). My own MonetCompat contains code for generating palettes, based on colorkt, but doesn't expose the ability to give it a colour and it give back a palette - it's something I want to add in the future though. Feel free to fork or copy it and take just the code you need to generate one though.

Repainter was bypassing the generation code, as you mention, using kdrag0n's recreation of Monet (the same one used in my own MonetCompat - shameless plug for devs - on an app level), and allowed tweaking of the colour generation. Of course you can't do that with a live wallpaper and passing custom colours to the generation, as good as your app is.

It's needed because the app reads your wallpaper in order to do the dynamic color theme thing so that the default theme matches your wallpaper color. You can read more about why this is needed in the MonetCompat library and the monet pub package which my app uses under the hood

The MonetCompat library by /u/Quinny898 , which uses /u/kdrag0n's custom monet implementation, also provides backwards compatibility all the way to Android 5.0 through the Palette API, but the Niagara developers said they opted for the above approach for simplicity.

WallpaperManager has a method to get the wallpaper's colours, it has done since API 27, so it's used for that. I've only ever seen it used in some launchers for UI elements until now. It's actually been possible to do Monet on the app-level for years, even before getWallpaperColors existed - because you've always been able to get the wallpaper as a bitmap and throw it into an extraction engine like Palette. This, combined with kdrag0n's Monet reconstruction, is how my own MonetCompat library works.

Oh and I already wrote a library that does that.

Someone else has already mentioned my library MonetCompat, but if you want to use the raw colours, they're accessible on Android 12 only, check android.R.color: https://developer.android.com/reference/android/R.color (the system_accent and system_neutral sets are the ones you want)

Google haven't released related libraries yet but it didn't stop some developers implementing their own that supports older Android versions.

There's also kdrag0n's reproduction of Monet, and my implementation of it in a library, compatible with Android 5.0+ (shameless plug)

We will use Square’s Mock Webserver to spin up a mock server which we can use to simulate real api's request to the get coffee endpoint.

OkHttp Documentation

mockwebserver -> https://github.com/square/okhttp/tree/master/mockwebserver

I searched in the OkHttp GitHub project for an advice on which values may be suitable for Android apps nowadays but found no answers (only this old issue which does not help). Since we share a single OkHttp client Singleton for all our retrofit APIs and even Coil, I wonder if the default 5 maxRequestsPerHost is really enough.

You can technically add a Content-Length header for each part. It's not forbidden by the RFC, but nor is it common. It caused [problems](https://github.com/square/okhttp/issues/2138) for OkHttp, and they eventually removed it. Might be fine for internal-only use, though.

Boundaries are a lot like UUIDs, and rely on the same logic. When generating random data, once you have enough bits, the odds are against that sequence of bits ever having been generated before in the universe.

Lets be specific. This is the gradle build file for Squares okhttp client library. How exactly would your bld tool "predict" or "help" with all the parameters needed? There is no need to be defensive. Replace those large build files with your own, show where your approach is better and then understanding will lead to better solutions.

And adding to that: The asynchttpclient library is just a thin wrapper around OkHttp3, so it might be easier to just go with that instead: https://square.github.io/okhttp/

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

OkHttp