compose-samples VS MVICore

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

This is what Jetpack Compose according to the Android Developers team;

Redux is called MVI in Android world. There are plenty of MVI libs: MVICore, orbit-mvi, mobius and other.

In this case maybe you should diff your view state and render only parts that have changed. I have written a diff-dispatcher library to help with this, but there's now a better one from badoo guys which doesn't need kapt.