From Mono to MAUI: the History of Xamarin
summary
A clear lineage from Mono (2001) to MonoTouch/Mono for Android to Xamarin.Forms is traced with concrete milestones: a $2.5M seed round in 2011, Xamarin formed and then acquired by Microsoft in 2016, and MAUI shipping as the unified UI layer across .NET 6–8. Tools listed include Mono, Roslyn, Visual Studio/VS Code, Xamarin Test Cloud/App Center, and Unity integrations; MAUI misses initial deadlines but by MAUI v3 the work largely just fixes bugs and the cross‑platform UI stack actually works.
AI-written summary · about
chapters (28)
- 0:00Xamarin lineage introduction
- 1:50GNOME and Mono origins
- 5:43Mono project announced
- 7:08Novell acquires Ximian
- 9:12Longhorn, Avalon, and the birth of WPF
- 11:25Unity adopts Mono
- 13:30iPhone impact on cross-platform
- 15:18Silverlight rise and fall
- 19:50Flash demise and Apple
- 20:55MonoTouch restrictions
- 22:01Windows Phone missteps
- 24:12Xamarin breakthrough
- 25:57Mono rescue
- 27:00Windows 8 and Build
- 29:50TypeScript success
- 31:35Xamarin testing cloud
- 32:58Satya Nadella and .NET future
- 34:43Microsoft acquires Xamarin
- 36:28VS 2015 and Windows 10
- 37:55Visual Studio Code rise
- 39:41Journey to .NET MAUI
- 41:06Fragmentation in .NET
- 43:12WinUI struggles
- 44:36.NET Core 3.1 updates
- 45:19.NET 5 unification
- 46:21Mono and BCL unification
- 47:28MAUI development
- 48:52MAUI adoption challenges
related talks
45mXamarin: How to Build, Test and Deploy for Android...
21mIndustrialization of mobile development
28mThe ever increasing convergence of native iOS and Android mobile development
46mCross-Platform Mobile Development vs. Native
42mCompose Multiplatform on iOS: On the Road to Stable
48mMobile Developer Productivity at Scale
35mBuilding Multi-Platform Projects with MVI Architecture
44mKeynote - The Future of Android...And How to Prepare For It