apollo3-android-sample VS compose-samples

I use manual DI whenever I don't want to force Koin or Dagger on a project, or I want to keep things super simple. This method gives you either single instance or factory, no lazy initialization, and no scoping (you'd have to add the ViewModel scoped stuff) simple app that has it: https://github.com/erdo/persista/tree/main/example-app/src/main/java/foo/bar/example (dependencies constructed here): https://github.com/erdo/persista/blob/main/example-app/src/main/java/foo/bar/example/OG.kt (getting the dependencies into your UI here): https://github.com/erdo/persista/blob/main/example-app/src/main/java/foo/bar/example/ui/wallet/WalletsActivity.kt ``` private val wallet: Wallet = OG[Wallet::class.java] ``` another larger app example: https://github.com/erdo/apollo3-android-sample It looks quite like a ServiceLocator but the difference is these things are not statically referenced and can easily be mocked in tests

Go ahead and clone the sample app, but the basic steps if you're doing it for your own app are:

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.