Dagger-Hilt is fine and all. Unfortunately, it arrived a bit too late in the android dev lifecycle. If I had to guess, most projects out there are still stuck using plain Dagger2. The official google android docs use Hilt (it really helps on brevity 😅) to showcase Jetpack Compose code. …

These are not the droids you are looking for — Android has a curious way of handling locale. With the introduction of per-app language preferences, things have gotten even more complicated. This post won’t go deep into explaining the nooks and crannies of localization. Better blog posts (and the actual android documentation) exist for that. Theory is boring enough, let’s…

On a long enough timeline, every test is a flaky test — Now why would anyone use this? Toasts cover the UI for a while, preventing other actions and matchers from working. Time sensitive. We are in compose world and.. Matchers suck. 🫠 The only good toast is French Toast Create a generic Toaster interface that will be responsible for all toasts in the app. Install the implementation into the SingletonComponent :

Wot I think — Was trying to create a silly custom lint rule the other day. Of course, I played around with https://github.com/googlesamples/android-custom-lint-rules (monkey-see-monkey-do). I was under the impression that for editor highlighting to start working, I only had to build the app. (oh boy) When I did manage to make it show up…

Start a work request — (see how-to-hilt+workmanager in the previous episode) A method in a ViewModel will do: Observing the state WorkManager.getWorkInfoByIdLiveData returns LiveData , which isn’t really useful at the moment. Turn that into a flow by adding the livedata-ktx dependency. Print out the state of the work request while you are at it. Job done. Or maybe.. The collection will be alive as long as the ViewModel is alive, patiently waiting for updates for a job that might be finished already.

Add (more) dependencies — Declare a dagger module Make it easy to inject the singleton WorkManager instance anywhere. Debug logging level is optional. Customize the application class We already declared the WorkConfiguration up above in the dagger module. Might as well use it. Fix up the manifest Declare a worker to try things out Assisted is the trick here. Use WorkManager anywhere

Kotlin Coroutines 1.4 is here, as is another chance to stave off boredom. StateFlow Imagine we have a fragment that is interested in a todo task from the classic JsonPlaceHolder API. Since we are working with flow, we need to launch a coroutine to collect it. A small button will…

Flow is fun to play around with. In short, it represents a cold stream of values. Kind of like my typical afternoon drinking a stream of too many cold ones. Aside from looking at memes all day we might as well write some code. FlowGuy holds this stream that…

🤖::execute order process death::🤖 — The android framework has a curious case of killing any app that’s in the background for more than a few minutes. Take this for example: The RedditViewModel is responsible for fetching a post from Reddit while the calling activity/fragment is responsible for observing the redditPostData variable. Once the post…