android-dev-challenge-compose-design VS Shrine-Compose

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

For example, I’m rebuilding the Shrine Material study in Compose. https://github.com/c5inco/Shrine-Compose It’s just capturing design intent for now but you can see in the code that I didn’t use the Layout primitive once. I may consider it for the Home Screen in the future since it’s like a Pinterest board, but overall one can get a lot done with Row/Column/Box.