This an introduction to series of blogs which I will cover few topics related to Xamarin Forms application development. Even though these topics unrelated to each other, I will use these to create one single application which utilize each technology to certain extent.
Topics which I plan to discuss are
- MVVM for Xamarin Forms
- MVVM based navigation Xamarin Forms
- Utilize Azure B2C for Xamarin Forms
- Utilize Azure AAD for Xamarin Forms
- Local databases with SQLite
- Custom rendering
I will add navigation to each topic as it completes, hope this will be an exiting journey.
To help solve the cross-platform problem, Xamarin has produced Xamarin.Forms and added this product to the list of tools for developers. Xamarin.Forms is a cross-platform API that maps to device-specific APIs. This article will delve into an examination of Xamarin.Forms with an application that I had to write for our startup and how well it meets several requirements:
- How well does it display on a platform? How much platform-specific code is necessary? Does the application “look” like a native platform?
- When a developer has to resort to native API calls, how easy is it? Can it be done? Does it work?
- When something else has to happen, how much third-party support is there?
Source: Realities of Cross-Platform Development: How Platform-Specific Can You Go? — Visual Studio Magazine