172

I am confused between Xamarin.Forms and Xamarin native.

What is the difference between the two?

So what are the technical positives and negatives of using Xamarin.Forms over Xamarin Native?

Ninad Kulkarni
  • 61
  • 1
  • 11
Ajay Kumar
  • 2,031
  • 2
  • 13
  • 17
  • 1
    Have a look at [The Good and The Bad of Xamarin Mobile Development](https://www.altexsoft.com/blog/mobile/the-good-and-the-bad-of-xamarin-mobile-development/) for an excellent discussion as of January 2017. – Oliver Feb 22 '17 at 13:21
  • 1
    Bottom line... Just go for Native! I am telling this based on my own experience. I re-wrote forms app to Native. – Tejasvi Hegde Sep 15 '18 at 17:56
  • 2
    Comments from 2015 no longer reflect the reality of Xamarin Forms. It has come a long way and has seemed to explode after .NET Core\Standard matured. – Sean Anderson Mar 05 '19 at 05:07
  • This question needs to be re-opened. It has now 4 years old and there have been huge developments within the Xamarin.Forms framework to enable the development of enterprise applications. – James Mallon Dec 17 '19 at 13:03
  • As of 2022, here's a guide on how to [get started with Xamarin Native](https://prototypemakers.medium.com/getting-started-xamarin-native-vs-xamarin-forms-maui-for-ios-android-d07139737722) – Saamer Apr 28 '22 at 14:55

3 Answers3

185

Xamarin.Forms

Pros

  • Create one UI for all platforms
  • Use basic components that are available on all platforms (like Buttons, Textfields, Spinners etc.)
  • No need to learn all the native UI frameworks
  • Fast cross platform development process
  • Custom native renderers give you the ability to adjust the appearance and feeling of controls

Cons

  • It's still a new framework and still contains bugs
  • Especially Windows RT is not yet stable
  • It's sometimes slower than accessing the native controls directly
  • Custom native renderers have boundaries and are poorly documented

Xamarin.Android, Xamarin.iOS, Windows Phone, Windows RT

Pros

  • Create one UI per platform
  • Easy ability to adjust the platform specific UI features and components
  • Get the maximum out of your UI

Cons

  • Cross platform development process is much slower
  • You need to learn all native UI frameworks
  • You may result in having duplicate code (as you describe almost the same UI in three different platform specific ways)

In addition to that Xamarin says on https://xamarin.com/forms:

Which Xamarin approach is best for your app?

Xamarin.Forms is best for:

  • Data entry apps
  • Prototypes and proofs-of-concept
  • Apps that require little platform-specific functionality
  • Apps where code sharing is more important than custom UI

Xamarin.iOS & Xamarin.Android are best for:

  • Apps that require specialized interactions
  • Apps with highly polished design
  • Apps that use many platform-specific APIs
  • Apps where custom UI is more important than code sharing
Wosi
  • 41,986
  • 17
  • 75
  • 82
  • Regarding "apps that require little platform-specific functionality", are there examples to get a sense of what kind of functionalities we're talking about? – NS.X. Jun 22 '16 at 05:25
  • Little platform functionality means you are doing data binding and other business rules primarily as the app. Not a lot of custom drawing, or trying to render everything pixel perfect. If you are ok with a common layout that is responsive, then Xamarin.Forms is a good fit. – Jason Short Oct 31 '16 at 17:14
  • Best answer in my opinion. This cleared it up for me: "Xamarin.Forms: Create one UI for all platforms" and "Xamarin.iOS, Xamarin.Android: Create one UI per platform". Thanks! – tedi Aug 14 '17 at 08:05
  • @Wosi It's 2017 and I am still wondering If anything has changed. Is xamarin forms still suitable only for prototypes and basic apps ? – Dibzmania Aug 21 '17 at 03:57
  • 1
    @Dibzmania I've never said it's suitable for prototypes and basic apps only. If you want to have a cross platform app with an almost identlical UI on each platform then Xamarin.Forms is great. If you want to have a custom UI per platform then you probably won't benefit from Xamarin.Forms and should use the native UI libraries instead. – Wosi Aug 21 '17 at 09:43
  • 1
    I think this article by Nathan Williams is useful: https://arctouch.com/blog/xamarin-forms-xamarin-native/ – Alt-WN Apr 13 '18 at 17:45
152

Aside from the points shown in the Xamarin Website, you should also consider:

Your team's background

Does anyone in your team have a previous experience coding natively for Android or iOS (using Java or Obj-C/Swift)? This experience is reused in native Xamarin, but they'll have to learn another platform to code in Forms.

The same is true if they know nothing about iOS/Android but know some XAML. Sure Xamarin.Forms are different from WPF/Silverlight, but knowing XAML surely helped me using Forms.

Performance

Xamarin Forms still has some issues, such as initialization time. You should consider whether or not this will be a problem for your final user. I wouldn't bother to wait a while for a dashboard app that I use once in a while to open, but I'd be angry if the same happened to a messaging app.

Time until delivery

Since the code sharing is bigger when using Forms, you may expect a quicker delivery time.

Complexity of your app

Considering the previous point, using Forms you may stumble on some show stopper bug (it's a very new technology after all) that will null the time gains. Consider the complexity of your application before choosing.

Saamer
  • 4,687
  • 1
  • 13
  • 55
William Barbosa
  • 4,936
  • 2
  • 19
  • 37
  • 2
    I'll add to this if you are expecting to have good looking app you'll end up having a lot of custom interfaces with Xamarin Native code for each platform – Roman Nazarevych Aug 22 '16 at 10:17
  • 3
    this answer and comment above are super too old. Performance isnt a big issue today if you enable AOT. regarding good looking app in the comment is also not true. xamarin forms improved and you can achieve good looking apps easily. – Emil Jan 28 '19 at 16:15
  • Xamarin Forms has not improved much in terms of getting a good-looking UI easily. Xamarin.Shell will make big improvements in that regard, but as of now, Xamarin is still difficult to get anything remotely attractive from without writing custom components for each platform. – Alexander Apr 27 '19 at 01:17
  • @Alexander, please explore the standard and community provided UI components available in Xamarin. My guess is that the high level of customisability is what makes beginners feel that achieving good UI is difficult. – Abhijith C R Oct 22 '21 at 11:56
45

From the Xamarin Website

Xamarin.Forms is best for:

  • Data entry apps
  • Prototypes and proofs-of-concept
  • Apps that require little platform-specific functionality
  • Apps where code sharing is more important than custom UI

Xamarin.iOS & Xamarin.Android are best for:

  • Apps that require specialized interactions

  • Apps with highly polished design

  • Apps that use many platform-specific APIs

  • Apps where custom UI is more important than code sharing

Guilherme Torres Castro
  • 15,135
  • 7
  • 59
  • 96
  • 3
    This answer is stale/old. Use Forms with Prism. Enjoyable experience. I'm a single developer building a huge app and I am very productive and my app just works on everything. If you want stunning looking apps there are various third-party views like Grial UI Kit (check out their free XAML live previewer). Remember, Xamarin Forms still uses the native controls by default. – Sean Anderson Mar 05 '19 at 05:05