Choosing the Right Framework for Your Cross-Platform Development
summary
Compares concrete tradeoffs: MAUI offers native controls and easy Xamarin migration but no web or Linux and older Xamarin support ends May 1, 2024; UNO targets web + desktop + mobile with pixel‑perfect WinUI compatibility and a hot design paid feature; Avalonia focuses on GPU‑accelerated desktop with WPF‑migration ease but mobile/web remain experimental; Flutter gives fast canvas rendering but reports like three of 20 plugins discontinued warn of ecosystem churn; React Native fits JS/TS teams but needs native bridges for deep APIs.
AI-written summary · about
chapters (23)
- 0:00Cross-platform intro
- 3:44Case studies and benefits
- 6:16Framework selection factors
- 8:24.NET cross-platform overview
- 10:30.NET MAUI deep dive
- 13:23.NET MAUI pros and cons
- 15:54.NET MAUI app showcase
- 16:58UNO Platform intro
- 18:23UNO Platform benefits
- 21:38UNO Platform features demo
- 23:48UNO Platform success stories
- 25:39Avalonia UI intro
- 27:25Avalonia UI pros and cons
- 29:56Avalonia UI showcase
- 31:46Flutter cross-platform option
- 33:56Flutter advantages and challenges
- 35:45Flutter production apps
- 37:57React Native cross-platform
- 39:38React Native pros and cons
- 41:24React Native debugging
- 43:14Choosing the right framework
- 45:26Framework recommendations
- 48:18Summary and resources
related talks
52m.NET Is Dead. Long Live .NET!
44mHow Real is this Cross Platform .NET Thing Really?
55mKeynote: The Future of Modern Application Development with .NET and Azure
23mTeam × Technology
21mSuper-Powered, Server-Rendered Progressive Native Apps
46mMobile CI/CD: A Cross‑Platform App Approach
40mHow to build Mobile DevOps for X-plat applications
01h 01mEnterprise Mobile DevOps