Learn-Jetpack-Compose-By-Example VS datmusic-android

Other samples https://github.com/vinaygaba/Learn-Jetpack-Compose-By-Example/tree/f7d7dc2f597f1946ace0c63194ddd89cd004f641/app/src/main/java/com/example/jetpackcompose

Airbnb did start working with Jetpack Compose during the early preview[1]. They have also developed a library to easily browse all the Composables within your app[2] — Vinay Gaba, Airbnb Tech Lead, is one of the biggest Jetpack Compose advocates. I recommend watching his Jetpack Compose by Example GitHub repository and going through his Compose Snippet library, which looks like it has potential to become Android Arsenal future successor 😜.

Anyway, to not just sound rude, Google Codelabs are quite nice when it comes to Compose. There is also https://github.com/vinaygaba/Learn-Jetpack-Compose-By-Example, I found it quite useful when first starting with Compose. If spmething can be set in a lambda vs through a variable, it's probably better.

Hello fellow droids! It's launch day and I'm here to talk about another Jetpack Compose feature that you will hopefully find useful. For some context, I'm the creator of projects like JetpackCompose.app, Learning Jetpack Compose By Example and Showkase.

I have a really similar motivation behind a project that aims to teach Jetpack Compose in the same fashion and funny enough, the name is also pretty similar to the title of this thread - Learn Jetpack Compose By Example. You can find it here - https://github.com/vinaygaba/Learn-Jetpack-Compose-By-Exampl...

There's a ton of comments in every example (even though they might be redundant across the examples) and the idea is that you should be able to learn this new framework by merely reading through the examples.

- https://github.com/vinaygaba/Learn-Jetpack-Compose-By-Example

I have learned a lot from reading Tivi's code over the years, here's my app using similar libraries & arch datmusic-android

Didn't expect the migration process to M3 would be this much involved. I thought just changing the MaterialTheme would be enough (new color schema/names, all different Typography names, no Shapes yet etc.). But all other components such as Text, Button, Icon, Progress/Slider, Scaffold, Surface need to be replaced with M3 versions..

I'm using it in production in my small music app (source) and I couldn't be happier about it. I was worried about scrolling until I tried release/prod build. navigation-compose and bottom-sheet integration also has some bugs. But we're not far from a perfect UI toolkit.