Coming from a conventional web app world, the world of mobile always fascinated me. However, I always felt like a misfit there because of dot net world’s obvious limitations in mobility.
I had read about Xamarin sometime in early 2014 and it instantly grabbed my interest, and I patiently waited for a Xamarin opportunity to come my way.Xamarin sometime in early 2014 and it instantly grabbed my interest, and I patiently waited for a Xamarin opportunity to come my way.
So, the moment I was presented with a chance to work on Xamarin, I just couldn’t wait for a second and decided to take the plunge.
Xamarin seemed like a very attractive option for .NET developers to be able to create mobile apps with minimum learning curve, leveraging .NET framework to its fullest.
However, after actually taking the deep dive, I figured that although you do feel at home with the entire .NET similarity in the environment, it’s not just .NET that would ensure a smooth sail.
There is a substantial learning curve involved with Xamarin, having come from a non-mobility background. One additionally needs to acquire the knowledge of basic native mobile application development concepts.
However, the following features in Xamarin studio makes one life much easier compared to the other mobile app development suites –
1. Look and Feel : Xamarin leverages the native look and feel of iOS, Android Studio as well as Visual Studio, which gives it an edge over the other native competitors.
2. Cross-platform Support: Xamarin Forms largely follows the write-once-run-anywhere philosophy where you could write your business logic and database code in common utility classes and reuse them across your iOS and Android apps.
3. Impact on regular development time : You substantially save on the development time when you write code that could be re-used by multiple platforms, with only the UI to be re-created.
4. Xamarin is fully native: Contrary to PhoneGap or Cordova or the likes, Xamarin is fully native; meaning that Xamarin’s bindings on any given platform mirror the native calls so closely that if you know the API, you can easily find its equivalent Xamarin, with very few exceptions. Xamarin also compiles its code to native c# code.
In the end, it all comes down to what your current project requirement is, and whether Xamarin fits well into the entire scheme of things and also, the skill set of the programmers at hand.
Follow me on Twitter