Just hope they don't kill flutter please.
It's "kitchen-sink" approach is resource-intensive to maintain. E.g., there's a language to maintain and a full suite of controls (doubly hard since integration with OS UX conventions is a constantly moving target) in addition to everything else you need for a full cross-platform app development platform.
Yet, where's the revenue stream to pay for it?
I think it's a matter of time before Goggle pulls resources off it.
It's open I believe, so it won't just stop, but it will quickly sink into disrepair without significant resources maintaining it.
It's also the primary UI for their next generation OS, Fuschia, though that could be canned down the road as well.
They really have something here, and I think they know it. Hopefully they don't pull resources anytime soon.
Plus there are the ongoing political wars with Chrome team (alongside Microsoft) pushing for PWAs, and Android reacting to continuous stream of Flutter questions by producing Jetpack Composer. It wouldn't surprise me, if there happens to exist a Jetpack Composer variant targeted at Kotlin/Native.
Not to mention greenfield OS development can be catnip to engineers - it probably serves as a good retention tool.