idiomatic-gradle VS nowinandroid

You should look into how https://github.com/jjohannes/idiomatic-gradle and similar projects handle it (nowinandroid has a good set up as well).

And finally, look at the idiomatic gradle repo. There is also a free video series that goes with this Understanding Gradle – Video Series. There are lots of bad practices in gradle that will slow your builds down, like using allProjects {}

I'd suggest getting rid of buildSrc, and just using build composition. I mentioned in another response, but check out https://github.com/jjohannes/idiomatic-gradle for how to use precompiled script plugins that are connected to the project via includedBuilds. The only issues I've had with this are generally resolved by just running the sub-build independently to resolve any caching issues in the 'primary' build. A simple gradlew build --settings-file ./build-logic/settings.gradle.kts run will generally resolve that, and that issue seems largely because of the 'root' build being a peer or anscestor of the included build (due to legacy structure of the project, an issue the linked example repo does not have).

When we initially migrated from buildSrc to an included build, it seemed an elegant solution to the problems outlined above. We were dropping buildSrc, with all its problems, and using the modern facility that Gradle considers the preferred, idiomatic replacement for buildSrc. (For a very elaborate example of this, see the idiomatic-gradle repo by former Gradle engineer Jendrik Johannes.) Included builds are indeed the best of both worlds in many ways: they can exist under version control in the same repository as the build that uses them; they can be easily opened in a separate IDE instance, improving build engineer productivity; they don't have the automatic test behavior of buildSrc, which improves feature engineer performance; and they're generally very well-behaved, without any of the magic of buildSrc.

The experiment was executed with 100 iterations(fresh agent without cache) for each variant, using the nowinandroid project and focusing on the assembleRelease task. By comparing the results, we aimed to assess the effectiveness of jemalloc in reducing memory usage and improving build performance in a CI environment.

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.