Learn-Jetpack-Compose-By-Example VS accompanist

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

The truly disheartening part is that whenever you choose something that works, for example ViewPager1, you need to defend that yes, this thing actually works as intended, yes, there's nothing in it that would "break over time" just because Googlers added the @Deprecated on it, and yes, you still don't want to use Compost for this because you still cannot scroll vertically in a horizontal Pager if your view is a WebView.

Compose on the other hand came out half-baked, significant performance issues, missing features, bugs and bugs and bugs and bugs and bugs and bugs and bugs and bugs and bugs.

Just to add to the list, Accompanist is a collection of compose libraries that helps a lot with some features. I can recommend Navigation-Animationand Permissions. https://github.com/google/accompanist

To give a bit of context, libraries not released as Jetpack libraries as experiment projects. Once they're released as Jetpack libraries, we have stricter release schedule in place and more resources to provide better stability for developers. That's why some Accompanist libraries end up as part of Compose foundation set, while others are still being shipped as part of the Accompanist project.

So you're going to get support for Parcelables in argument passing, animation support without having to fear crashes, and if you drink the ScopedServices koolaid you even get to get DI with lifecycle management and scope inheritance.

Here's a fun bug though https://github.com/google/accompanist/issues/1233

There is a bug the preview is not working when System UI controller is used. See issue tracker here.

👋 I have been using Mobius personally and for work for over two years now. It's a lot of fun to use and I would definitely recommend the community to consider using it. I frequently visit their GitHub repo because they still have their documentation in the GitHub wiki, unlike new repos such as Accompanist. So, I thought what better way to give back than do the grunt work of porting their wiki to GitHub Pages + MkDocs ❤️🔥

Accompanist for unofficial stuff that's still useful