compose-samples VS tivi

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;

It's definitely the most verbose part of our app and one of the weakest parts of the Jetpack library. We used https://github.com/chrisbanes/tivi for some inspiration on how to organize your navigation structures.

I have considered a few variants around this route. One easy way out would be just to launch a ComponentActivity with a PreferenceFragment like what Chris Banes does in TiVi ... but if you go with PreferenceFragment(Compat) it seems you are kinda stuck with SharedPreferences. If one attempts to supply DataStore wrapped in PreferenceDataStore, it seems types get messed up (TextPreference will store as a String, even if the InputType is number, etc).

I would read and study nowinandroid and tivi apps.

Check out the approach from tivi https://github.com/chrisbanes/tivi/blob/main/app/src/main/java/app/tivi/AppNavigation.kt as an idea.

They probably want you to do a module split like in https://github.com/chrisbanes/tivi or https://github.com/igorwojda/android-showcase, but what they probably don't realize is that modularization is a trade-off, namely greatly increased build configuration complexity for... well, having modules.

This case is used in [Tivi](https://github.com/chrisbanes/tivi) and it is also a sample in android [compose-samples](https://github.com/android/compose-samples)

I tend to look for projects by devs that I respect, ex: Chris Banes - Tivi

Apps for inspiration/examples: Plaid, Tivi

If we want database operations to show up in Sentry, we need to wrap them into special objects called Spans. In short, Spans are application events that have a start and end time and some metadata like operation name, description, etc. For example, this is how the performance breakdown looks for a popular open-source app tivi: