moko-mvvm VS compose-samples

With KMM we can share entire layers of code, for example, the entire use case layer with its logic can be in KMM, the entire data part with its respective repositories and data sources can also be in KMM. There are even some early-stage libraries that help us to share ViewModels to manage the state of the UI.

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.