camera-samples VS OkHttp

For the device formats, what you get on CameraX should be what you get on Camera2, but you can verify with the Camera2Video sample app. It lists the available resolutions and framerates (which notably calculates it in largely the same way that you're already doing).

It's been many years since I used camera APIs, and only camera1. I don't have experience with camera2 and cameraX. The android camera docs https://developer.android.com/training/camerax/choose-camera-library lists the available libraries and in additional resources at bottom of pages, there are samples available. You probably need https://github.com/android/camera-samples/tree/master/Camera2Basic or https://github.com/android/camera-samples/tree/master/Camera2Extensions

https://issuetracker.google.com/issues/178121821 https://issuetracker.google.com/issues?q=camerax%20leak https://issuetracker.google.com/issues/141188637 https://groups.google.com/a/android.com/g/camerax-developers/c/j8T9iRtTGtw https://github.com/android/camera-samples/issues/94

https://github.com/android/camera-samples They have both Camera2 and X code.

Have you checked out the official samples: https://github.com/android/camera-samples/tree/master/CameraXBasic

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