We used Portable Class Libraries to share code between our iOS and Android and our server-side web application.įor one thing, sharing our models was huge. Sharing code between iOS and Android is (relatively) obvious. ![]() With Xamarin Forms we got a fully native look and feel for our app while achieving 76.3% code reuse (most of which was the important stuff), plus an easy out if the abstraction failed us. Animations, completely custom pages, and dynamic rendered controls, all quite doable once you're up to speed. But once we mastered Custom Renderers we were able to accomplish pretty much anything UI-wise. We occasionally ran into hiccups with controls that failed to offer the UI customization we wanted. The two-way databinding, native support for the MVVM design pattern, and easy to understand (for me) XAML were just icing on the cake. We eventually went back and replaced every single platform specific UI page with a cross-platform Xamarin Forms version that rendered fully native controls. ![]() Mindful of the advice, we started with mostly MvvmCross and Interface Builder story boards.īut the more Xamarin Forms pages we built, the more we loved it. When our team started I heeded the rumors that Xamarin Forms isn't ready for anything more than settings pages. ![]() Xamarin Formsĭon't listen to the detractors. I'd choose it again in a heartbeat despite having built pure native apps for every major platform, and having built a mobile app in JavaScript with PhoneGap and Ionic. That about sums up how I feel regarding Xamarin development after working with it on two separate projects over the last year.
0 Comments
Leave a Reply. |