architecture-samples VS modernstorage

Here's an example project on GitHub that demonstrates how to use a ViewModel in practice: https://github.com/android/architecture-samples/tree/master/BasicSample

For me this one is the best: Architecture samples it's easy to understand and covers lots of concepts.

Since I never had a mentor or any courses I decided to follow anyone in their development approaches and my choice was google team. There are repo which is supported and update for years, it changes and might slightly differ in branches. But it could answer your questions.

For merging multiple data-sources, like network and database, I can use Repository backed with NetworkDataSources and DbDataSources. For data manipulation, Kotlin's collection has many useful functions (map, reduce, groupBy, count, etc.). If I want to ensure a data can only be emitted once, a simple modification to LiveData is enough (SingleLiveData

Take a look on Android blueprints https://github.com/android/architecture-samples

Check this library from Google: https://github.com/google/modernstorage

The developer experience could definitely improved and that's why we're making this library. If you've looked at the getting started section of modernstorage-storage, you can see it mentions a SharedFileSystem. The goal is to have one for the cache & internal files with the same API, making it much easier for you to interact with files. If you have any feedback or idea, feel free to create a discussion topic here.

I believe Google is working on modern storage library to deal with developer nuances. https://github.com/google/modernstorage

Yes it does, it's because the code outlined here belongs in the ViewModel, the launch should be triggered as one-off events. But as we know, Google samples often didn't use Channel(UNLIMITED) even though it's a solution to this problem