ktlint VS compose-samples

In my experience, I have faced these issues while trying to keep the code style consistent across the team - 1. ktlint and "Reformat Code" in Android Studio produce different outputs. This causes issues as most developers find it easier to use "Reformat Code" in AS but if you have a ktlint check on CI, the checks sometimes fail. 2. Different AS versions produce different `codeStyles.xml` file. Sometimes, on updating AS, it automatically adds new rules to the `codeStyles.xml` file. These rules might not be compatible with ktlint and might only work on specific AS versions.

Ktlint

Not even an Android Studio-specific feature, but rather a feature of the underlying IntelliJ. Just select Code > Analyze code > Silent code cleanup and your entire project will be cleaned up using the default linter (this can be combined awesomely with Ktlint).

Ktlint + Detekt: Kotlin linting/static analysis (https://ktlint.github.io, https://detekt.github.io/detekt)

Refs. Klint Page Klint Github

Linting is the process of analyzing code for potential errors and one of the ways we can do that in Kotlin is using Ktlint. As per the documentation:

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.