But Google seems to be betting on multiple horses here. They also created Jetpack Compose. And of course Jetbrains extended that to Compose Desktop and Compose Web so that ecosystem is actually becoming quite interesting together with their multi platform Kotlin compilers. Compose Desktop does not currently use the Kotlin native compiler unfortunately but it does use Skia, which is the same graphics library that Google uses for Chrome and Flutter. If they'd fix the desktop variant to use the native compiler, they'd be able to target basically any platform. Including IOS.
IMHO that is such an obvious thing to do for Jetbrains that I pretty much assume that they are planning to go there. That would make this a direct competitor to Flutter.
Compose is getting quite popular despite still being relatively new. IMHO, if Jetbrains (or Google) get their act together and make that usable for IOS, there would be a lot of developers that would use that. I know I would. Flutter is not for me. I'm sure it's great but I have no desire to learn Dart.
We are currently using Kotlin js to be able to target mobile and web and kotlin jvm on our servers. We package up our app using Cordova and we have integrated a few plugins to e.g. do things with NFC. It works great. Performance is not an issue for us. And having just one code base and 1 UI team is critical for us. But I wouldn't mind some more options for cross platform development. Browsers are a necessary evil currently to target mobile and desktop with 1 application. But the boundaries between these platforms are increasingly artificial.
Just to give you example In many ways I prefer Ruby than Python as a language but Python is just swiss army knife and in many cases you are one PIP install away to finding library that solves your problem. Maybe Python doesn't have such a nice web framework as Ruby on Rails but ruby is not much used elsewhere.
I think people complaining about Dart as a chosen language not because of it's features but because
1) you have to learn and/or redevelop new SDK for it,
2) language doesn't have good interrop with any other languages (like Kotlin -> Java, Swift -> Objective-C, TypeScript -> JavaScript, Objective-C -> C++, Rust -> C, C++ -> C)
3) ecosystem is small