Compose is fun. I do get the feeling that there are quite a few “gotchas” when working with it, though. Here are a few questions that kept bugging me: * Are all functions equal in the eyes of the compiler? * Are suspend functions stable/immutable? * Do recomposition scopes even matter much?
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 to showcase Jetpack Compose code. What if you are stuck in
These are not the droids you are looking for
On a long enough timeline, every test is a flaky test
Wot I think
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
Android Shorts 🩳: WorkManager + Hilt 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
Kotlin Coroutines 1.4 is here, as is another chance to stave off boredom.
🤖::execute order process death::🤖
This is part of a series head-scratching my way into coroutines. It can be read as a standalone although you might be missing out on some spicy memes here and here. Testing ViewModels without losing the will to live A ViewModel “sits” quite close to the activity/fragment. Something that
Or how to pretend you know what you are doing on pull requests
A callback story