jetpack-navigation-ftue-sample VS compose-samples

Not a complex example per say, but I did write this sample and it'd scale as it looks right now, just more packages in core and in features.

The whole circus around login/logout is a mess in jetpack navigation. It assumes a world where your app always has a fixed starting point which imo doesn't make sense with apps where the entire content is behind auth. I recommend checking out https://github.com/Zhuinden/jetpack-navigation-ftue-sample

A simplified variation can be seen in this repo, a LiveData variant with Jetpack stuff can be seen in this repo, my issue with this sample is that as there is no input + debounce + filter + async data load example in it, there is no switchMap (and even for combineTuple, I can use my other helper validateBy here), and those would be key to understanding the difference in terms of expressibility and power...

I have a non-Compose "MVVM + Hilt" sample here

See https://github.com/Zhuinden/jetpack-navigation-ftue-sample/blob/master/app/src/main/java/com/zhuinden/jetpacknavigationdaggersavedstatehandleftueexperiment/features/login/LoginViewModel.kt#L30-L41

Yes it works wonders

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.