accompanist VS compose-samples

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

The official documentation provides a comprehensive guide on the basics of Jetpack Compose, components, layouts, theming, and more advanced topics.

Apparently Jetpack Compose is an Android copy of SwiftUI?

https://developer.android.com/jetpack/compose

Only two HN threads with comments: https://hn.algolia.com/?q=jetpack+compose

If you want to take a look at code, we have the Jetnews sample app that support different screen sizes. And Jetcaster also implements features such as table top mode.

check this out : https://github.com/android/compose-samples/tree/main/Crane

So I would say that instead if learning everything from Android SDK, you should just set a goal to create some app. Learn about Activities, their lifecycle, layouts (or Compose if you want to be more up to date). Try to implement your app based on this. Then improve your app using Fragments and their lifecycle. If you truly want to understand Views, which are essentially the building blocks of Android UI then I would recommend implementing your own custom View, which will have completely custom look - it is cool thing to try and you will learn how it all works inside.

The compose samples by Google are a good reference to look into: https://github.com/android/compose-samples

Basic understanding of Jetpack Compose.

The compose-samples repo has a comprehensive list of samples ranging from low to complex projects which might be worth a look.

For instance, there is a link to this repository, that contains all sorts of samples, that are up to date and ready to use. That's cutting edge, which is a recommended start.