Blade VS compose-samples

I liked https://github.com/bluelinelabs/LoganSquare for example, but annotation processors are hard to maintain. Look at libraries like Mortar-Architect https://github.com/lukaspili/Mortar-architect or Blade https://github.com/FrantisekGazo/Blade or even better Permissions-Dispatcher https://github.com/permissions-dispatcher/PermissionsDispatcher/issues/775 which actually breaks builds after certain Kotlin versions.

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

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

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.

And what was learned from Flutter has produced something I consider even more interesting: Compose UI (https://developer.android.com/jetpack/compose) and JetBrains' Compose Multiplatform (https://www.jetbrains.com/lp/compose-mpp/)

Now, same story, in the current documentation the list is replaced by a single UserMessage without any explanation of the previous example. It just says "For a more advanced use case, displaying a list of user messages on screen, check out the Jetsnack Compose example." .

As for the strange infix syntax, you're correct - it's not important (for Dart anyway). Kotlin supports writing code that have DSL like syntax making things like typesafe HTML or Jetpack Compose possible.

Sample apps