MyGoodDoggoApp VS YouTooBeAlike

On the other hand, reducing events by validating uuids is absurd. All you need to do is define a sealed interface implemented by data classes and objects as your event types. Use a single view model function that takes the type as input to reduce events. Examples can be seen here.

Regarding state persistence, I'm currently relying on the activity/fragment itself to store and restore. I've used SavedStateHandle before and one problem I've found is that it doesn't persist across fragment attachments. I implemented state restoration in ThumbnailInfoFragment and ThumbnailInfoViewModel of demo project. I'm wondering if this is a good approach or if I should switch to SavedStateHandle. It seems I can directly store the State object in SavedStateHandle instead of reloading it with persistent parameters after process death.

Not sure why you're asking specifically about recycler view. If your application shares most of the code, I highly recommend modularization by feature and layer. You can then create a second application as a second application module in the same project. Check out the official guide, or if you're interested in my codebase with a slightly different approach.

If your error message is cleared after being displayed, it has a different lifecycle than UiState. This means you should declare another value to describe this one-time operation instead of just clearing the error message in UiState. This Github Gist is a possible UiState declaration that fits your scenario. If you want to reference a sample project, here is the Github repo.