Succeeding with Xamarin
summary
Company transit app evolves over four years from shared Xamarin code to full native after performance and maintenance pain points: Android startup sometimes ~15s versus iOS ~0.5s, Xamarin builds balloon to ~15–20MB while native APKs drop to ~2–3MB. Concrete fixes: move platform glue out of shared projects, use dotnet standard for services, prefer dependency injection over a global service locator, embed selective UI with Xamarin.Forms embedding, enable Ahead-of-time (AOT) compilation and Prism MVVM for DI/navigation to speed startup and improve testability.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:06Switching from Xamarin to native
- 2:10Xamarin tooling and performance
- 3:54Code sharing in cross-platform
- 6:43Platform-specific code pitfalls
- 10:35Code organization patterns
- 15:28Dependency injection patterns
- 21:09Testing and maintainability
- 27:18Xamarin.Forms embedding
- 34:27Dependency service patterns
- 41:12MVVM with Prism
- 45:53Testing versus manual QA
- 48:01AOT compilation on Android
- 50:50Xamarin versus native
- 53:17Final thoughts and Q&A
related talks
42mCross-platform mobile apps development
58mBuilding Fast and Beautiful apps with Xamarin.Forms
57mCross Platform Mobile with XAML and MVVM
39mAn overview of the Xamarin programming platforms
01h 01mGo Mobile with Xamarin
34mBuilding mobile applications with .NET Xamarin
42mWhat’s new with Xamarin?
47mCross Platform Mobile Fishbowl