A couple of years ago I built a talk comparing .NET MAUI, Uno Platform, Flutter, Avalonia and React Native. I had tables, pros and cons, and a winner for almost every scenario. Then I started working on two of them.

Since then I've done tooling and NativeAOT work on .NET MAUI, and implemented controls, accessibility and platform APIs in Uno. I should say up front that I now work on MAUI, so treat my scoring with suspicion - which is roughly what I'm going to argue you should do with anybody's framework comparison, including my old one.

What changed isn't the ranking, it's the questions. Who actually owns the control you're using, and what happens the day you need it to do something its author never intended? What do you do when the accessibility tree, the native view tree and the XAML tree disagree about what is on screen? A demo that looks identical on six devices tells you almost nothing about month six of the project.

So: real bugs, public pull requests, and a proper look at native versus drawn UI, plus the evaluation questions I'd ask now instead of the ones I asked then. There is no universal winner. I checked twice.

For developers and technical decision-makers evaluating or maintaining cross-platform applications. This is a new follow-up to my earlier framework-comparison talk, now based on public implementation work in .NET MAUI and Uno Platform. No product pitch. Preferred duration: 60 minutes including Q&A.