@Antanas A. HTML and CSS are not desirable. Just look at the massively inconsistent ecosystem of WEB UI frameworks and helpers. We don't want to be lost in a jungle of solutions that all have unsatisfying drawbacks. The cascading nature of CSS leads to many display bugs where some style is often applied to elements that were not designed for it. HTML is more verbose than what Kotlin can bring us, and lacks any logic. That's why there's "magic" frameworks or things like JSX. There are plenty of other reasons, but I think that's enough to justify trying to make something better, without the decades of legacy HTML and CSS have.

Most of the points don't resonate or make no sense

Like you can't mix Vue with JSX and React that easily.

Encapsulate each in a web component and they'll compose well

I was thinking interop with multiple ways of doing things. I meant it's not so much better as Android's current situation in a way that just having web technologies of 2019 to make UIs on Android would be a satisfying improvement. It's been a long time I did HTML and CSS though, like 4+ years ago. I was lost as I was seeing the rise of web components with Polymer and AngularJS OTOH made by the same company, and vanilla HTML/CSS. Having to use JS (dynamic types, tooling) was what made me lose the train as I was starting Android Dev in apprenticeship. Nowadays, there's a gazillion ways (maybe not literally) of doing UI on the web, and sure, you can heavy load your app with web components composition from multiple frameworks if you change your mind down the road because of a "gazillion" possible reasons.

You're conflating a cherry-picked set of things and packaging them as an argument. It's trivial to do that same with Android or iOS or Kotlin or just about anything because you either are using ng-repeat or a simple for loop in JSX, not both at the same time.

You can see it this way. Anyway, I think we all want UI development to be simpler. Personally, I don't look for more options, but for a straightforward choice because there's only one good option. The WEB ecosystem for UI dev doesn't seems to be that to me. That's why I cherry picked what I had at the top of my mind among the massive amount of thoughts that and confusion I have about WEB dev. And I can do the same for Android where it's hard to pick between Drawable(s), Canvas, "composing" Views, with a bit of inheritance… adding transitions and animations, along with manual way with coroutines… Yes, Android UI is a struggle too, and as I started iOS recently with full Kotlin/Native it felt almost worst with the constraints system I didn't get yet, with multiple APIs for it. Isn't that a few reasons wht we are all looking towards Compose (and SwiftUI)?

Nothing about those things are intrinsic to the web

HTML is quite intrisic to the web as of 2019, and HTML alone is only declarative, unlike Kotlin or Swift which can take advantage of higher order functions, control flow, and <drop><this><kind><of><little> <repetitive>noise.</repetitive></little></of></kind></this></drop> that adds up and makes readability a little harder. With such a base that you can't really circumvent, I think it's hard to make something as satisfying as Compose or SwiftUI (opinion based on the snippets and comments I read about it). JS is also intrisic to the WEB as of 2019 (although there are ways to avoid it somehow), but let's not debate all the wrongs and opinions about JS.