nowinandroid VS androidx

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.

To diagnose whether our composables and models meet these criteria, we leveraged Compose Compiler Metrics. These gave us stability information about the composable parameters and allowed us to update our UiModels and composables to make sure that they could be skipped. We ran into a few snags. At first, we were not using immutable collections, which meant that our list parameters were mutable and hence composables using these params could not be skipped. This was an easy fix. Another unexpected issue we ran into was that while our composables were skippable, we found that when lambdas were recreated, they weren't considered equal to previous instances, so we wrapped the event handler in a remember call, like this:

I am trying to manually copy and paste out the pieces of code I need from the glance source code and put into my Android Studio project but as you can imagine there are hundreds of errors to address. I also tried a git clone of a specific chunk of the source code from here without any luck.

One mistake I made is naming conversion of a composable function, that I didn't start with a noun. This is quoted from Compose API guidelines

https://github.com/androidx/androidx The androidx repo might be what you're looking for

Haven't looked too closely yet, but so far this seems similar to AndroidX Playground (albeit Playground isn't exactly meant for public consumption, of course).

This is the implementation of CoroutineLiveData: https://github.com/androidx/androidx/blob/androidx-main/lifecycle/lifecycle-livedata-ktx/src/main/java/androidx/lifecycle/CoroutineLiveData.kt

SafeArgs VM isn't safe?

preferences datastore is similar to SharedPreferences. Proto datastore is the one you should be using, and is based on protocol buffers to give you type safety among other advantages. Even in the case of preferences datastore though, it doesn't appear to even mention SharedPreferences. You can see the source for all datastore components here: https://github.com/androidx/androidx/tree/androidx-main/datastore