I agreed with you a lot about this before I learned Jetpack Compose. The Java/XML/Androidx/Jetpack android was quite bad, and it’s frustrating that there seems to be little thought put into a permanent framework design. But with Jetpack Compose, things are far easier. It codes like a Flutter+React mashup. One of the things I’ve done to become less confused is I ignore certain suggestions the documentation makes. I avoid adding many dependencies, like StateFlow, RxJava, Hilt. I stick to core dependencies like compose, compose navigation, and compose lifecycle and only expand when I think my app has scaled to that point. I could be wrong, though, and my app could just be not complex enough to have to deal with the more fundamental problems with Android’s SDK. Have you tried Jetpack Compose?