architecture-components-samples VS tivi

https://github.com/android/architecture-components-samples/ was historically better

uh, maybe https://github.com/android/architecture-components-samples/tree/a87535608564103423415baddb1e586f0337be44/LiveDataSample/app/src/main/java/com/android/example/livedatabuilder

But Google invented a set of guidelines in "Guide to App Architecture" in 2017 which you can see here in action that after the re-org the new devrels didn't really understand so they ended up making their own version of "clean architecture" where the data layer depends on the domain layer and not vice versa, + never learned how top-level layering like this doesn't even scale ever and they should be creating components, not "layers".

5.) check the https://github.com/android/architecture-components-samples/ repo for samples (if it is a Google library, and only for some things)

When I take the advanced navigation project and update it's dependency to navigation 2.4.0 we get the working backstack as shown here.

That's still an issue .

Hey guys, Im trying to recognise more about api calls in a contemporary architecture. I am using retrofit with livedata/coroutines to make my api calls, but I'm struggling with error handling. Most of the solutions I find, even in googles own example, includes writing a wrapper around your api request and handle the error that. It seems overly complicated and frankly stupid to do something like that for, what I consider at least, rudimentary functionality. Even with Dart/Flutter, google has made this easy ‏‏‎ with async/await and Futures. Am I being lazy to think that if even google needs to write extra code to solve a common use case, they should probably add it to the framework? I dont know, maybe I just needed venting.. what do you think? google's project: https://github.com/android/architecture-components-samples/tree/master/GithubBrowserSample

/uj if you're reeeeaaaalyyyy interested, I found them here lol

Look no more: https://github.com/chrisbanes/tivi

It's definitely the most verbose part of our app and one of the weakest parts of the Jetpack library. We used https://github.com/chrisbanes/tivi for some inspiration on how to organize your navigation structures.

I have considered a few variants around this route. One easy way out would be just to launch a ComponentActivity with a PreferenceFragment like what Chris Banes does in TiVi ... but if you go with PreferenceFragment(Compat) it seems you are kinda stuck with SharedPreferences. If one attempts to supply DataStore wrapped in PreferenceDataStore, it seems types get messed up (TextPreference will store as a String, even if the InputType is number, etc).

Thanks I think what's confusing is that UI events are recommended to be modeled as Flows, which I guess is why Tivi uses Flows for even the simplest actions, but it does a lot of very fancy things. Most repository interactions seem to have an entire class extending an Interactor (e.g.) which catches and emits errors, progress and handles timeouts and does all that crazy queuing stuff with UI "messages" Flow

I would read and study nowinandroid and tivi apps.

Check out the approach from tivi https://github.com/chrisbanes/tivi/blob/main/app/src/main/java/app/tivi/AppNavigation.kt as an idea.

They probably want you to do a module split like in https://github.com/chrisbanes/tivi or https://github.com/igorwojda/android-showcase, but what they probably don't realize is that modularization is a trade-off, namely greatly increased build configuration complexity for... well, having modules.