architecture-components-samples VS nowinandroid

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

As a simple example, today we will apply a performance test within an experiment on the new Gradle version in the project nowinandroid. The goal is to verify that the update has no impact on our codebase. In the experiment, we will cover the worst-case scenario where all tasks are executed and we don't have build-cache available.

So clean and simple! Though I would really advise respectively moving every single dependency AndroidConventionPlugin for added structure, development speed and maintainability. Remember: the true salvation of deprecated dependencies is making sure you always use unstable dependencies!

Here's an example of Embedded. Pull and look through the database module for ForeignKey and other concepts.

I remember it. This is a more up to date version from Google: https://github.com/android/nowinandroid There's also lots of sample apps and codelabs on https://developer.android.com/?gclid=CjwKCAjw-IWkBhBTEiwA2exyO7rWOvWd5yxCtFE5tmogy5LvA7HbxqQGpEQZz7_2ke579DPIHN06rhoCa-sQAvD_BwE&gclsrc=aw.ds

Check out the NowInAndroid repository: https://github.com/android/nowinandroid

Also check out https://github.com/android/nowinandroid which is the official app that includes the latest features.