Sunday, January 7, 2018 6:59 PM by Mykhail Galushko

Why do we use Xamarin.Forms?

We have been working with Xamarin Platform for more than 5 years. And last 1.5 years we are focusing heavily on Xamarin.Forms. Why did we select Xamarin.Forms platform?

Main mobile product (codename=“Project A”) of our partners, that we are working on, is built with Xamarin.Forms and it is in Beta now. And I think we did right decision in the beginning when we selected Xamarin.Forms as main development platform.

Let’s go back to definitions and learn basics:

Xamarin: platform, that was built by the developers behind Mono, an open source development platform based on the .NET Framework, led by Miguel de Icaza and first introduced in 2001.

alt text

Xamarin.Forms: cross-platform UI toolkit, based on Xamarin. It allows to describe UI once and get platform-specific UX/UI.
Supported platforms: iOS, Android, UWP, MacOS, Tizen, Windows (WPF is coming), Linux.

alt text

Main pros of Xamarin platform:

  1. You are using part of existing .NET world.
  2. You can use existing tools and services from .NET. Perfect integration with Microsoft ecosystem.
  3. Very similar to native development process, since you have 100% access to all platforms native API.
  4. Native UX/UI per platform (tools like Phonegap doesn’t provide this).
  5. You can share code between platforms.
  6. You get nearly native performance.
  7. There are a lot of partners, like Telerik that have built wonderful toolkits for Xamarin and Xamarin.Forms.
  8. Now it is part of Microsoft, which means that future is bright.
  9. You can reuse any existing native library.

And if we are talking about Xamarin.Forms:

  1. Shared UI between platforms (you write once and get platform-specific UI). You can cover multiple platforms with the same code and get native UX/UI.This means that in general you write 70–80% shared code and 20–30% platform-specific code. So it is great impact on budget and time.
  2. Open source.

Why are we using Xamarin.Forms for Project A and other apps:

  1. It is applications for business, that allow to automate business flows and consume data from multiple sources. So our goal is provide native experience to users. For example, using XF for games it not a right choice, because you don’t get any benefits.
  2. We are delivering custom flows very quickly to new customers and they are able to use platform and identify benefits for their business.
  3. Part of our team has great experience in .NET development (web, desktop, mobile), so they are able to reuse this knowledge.
  4. Developers that have experience with native development also can easily switch to Xamarin and reuse all their knowledge as it is. And this works really great. Especially now, when Swift and Kotlin appeared.
  5. We can continue using Visual Studio and other well-known tools.
  6. We are using VSTS for CI/CD, HockeyApp (plan to switch to AppCenter later) and it works really smooth: as soon as developer makes change, build in VSTS is running, tests are checked, QA gets new build and can check the feature.
  7. Now we are in progress with building automated UI tests, that will be run on our local build machines via simulators and in Test Cloud - means that we can cover most of flows with automated tests. We are building it using Xamarin.UITest framework.

Of course every platform and tools have disadvantages and issues, so I should cover this also:

  1. Package size: bigger than for apps, that are built with native tools. With each update Xamarin reduces it, but it is still big. More details: https://developer.xamarin.com/guides/android/advanced_topics/application_package_sizes.
  2. You can have performance issues with Android in specific cases. With latest 2.5 update situation is much better, so I expect great improvements in next release.
  3. Weird bugs happens, as in every library/tool, but they are quickly resolved and delivered.
  4. Compilation speed is slower, than with native tools. But things go better with each release.

So each time when you plan to build mobile app - think carefully about platforms, requirements and your users - maybe Xamarin.Forms is a perfect choice for you.


Feel free to contact me if you need any help for selecting right framework for your application!

For more details, please, see presentation about Xamarin and Xamarin.Forms that I did recently:

other posts

Thursday, January 11, 2018 3:03 PM

Azure Cognitive Services #1: Speaker Recognition API

Cloud-based service, that provides REST API for a recognition of a speaking person in a given audio.

Friday, January 5, 2018 2:48 PM

Solving classification problems with Azure Machine Learning for blood donations prediction

By current article, we show how to apply ML classification methods to the blood donation system.

Tuesday, March 21, 2017 11:18 PM

How to make cities smart?

What is a "smart city" and what we need to do with our cities?