androidx VS android-dev-challenge-compose-design

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

you're asking about how to do this

I still don't know why I needed this Layout, but it's true that replacing drawables and styleables with mere function calls and function arguments respectively is promising

You can extract logical components to the top of a composable as local functions and retain reasonable scoping while also creating local components, thus making the actual code straightforward to read (even if you sometimes need to also add hacks because Compose be Compose)

Yeah, both for measuring the current width/height of the layout (like getting the screen size), and also when things like Modifier.fillMaxSize(0.5f) doesn't work and I have to write code like this

Oh, that's unique to Navigation-Compose's design, and has nothing to do with declarative UI in particular. For me, navigation in compose is just this

Although I personally would rather pass in lambdas and then make the connection