Its a pain though. We tried last year at work to build something a little bit more complex than their examples, and it was a pain. Gave up after a month and built our apps in Flutter instead. Works like a charm.
I’ve been building this way since 2018 using MvvmCross[0] and it's become much less painful with LLMs where you can simply ask to recreate an iOS UI on Android. I even managed to implement experimental hot reload[1] for native UIs on Android from .NET, but ended up not using it because, again, nowadays it's faster to iterate with Claude Code – it just one-shot things most of the time.
Currently I'm building an app with Uno Platform[2], which is basically .NET Flutter, and while it's cool to get things working across five different platforms at once, you can note the difference, especially on scroll. No automatic Liquid Glass / Material 3 for it either.
So it's a choose your poison situation: either building native interfaces on each platform separately, or fighting later with an additional layer of abstraction and a canvas-based UI wheel reinvention.
