Xamarin.Forms - allows you to use one library of elements (text fields, buttons, radio buttons, labels, list views, etc.) for all systems (Android, iOS, Windows)

You add elements in your Xamari application, and on a specific platform (iOS or Android or Windows) for each of your elements generation is called and native elements are drawn (iOS has its own buttons, Android has its own buttons, etc.)

You can add elements in both Xamarin c# code and XAML format.

• First of all, it's the well-known C# and .NET. If you've been writing in sharpies for a long time, then you don't need to spend a lot of time learning several new frameworks, or even languages. Or, at least, at the beginning, you don't need to, and you can start quickly enough using your current knowledge.

• Secondly, the approach to creating and working with the user interface is close to what we are all used to in Windows. WPF developers will be especially happy, since Xamarin Forms supports working with XAML, bindings, templates, styles, and other joys of life. I think it's clear that they're a bit stripped down and we shouldn't expect the full power of WPF, but it still adds convenience.

• You can reuse code that has already been written. For the most part, it will work correctly. Platforms have limitations, but they are not so great.

• The fact that Xamarin.Forms is similar to WPF leads to the following advantage of this platform: MVVM. Indeed, Xamarin.Forms has XAML, visuals have a BindingContext (analogous to the DataContext in WPF), and there is a BindableProperty (analogous to the DependencyProperty). In this way, you can bind a View to a ViewModel in a similar way to WPF.

• Another advantage of this framework is that since the UI is described only in one place, applications under different systems will look very similar. Which can be important, for example, in corporate development.

• Incomplete implementation of the functionality WPF ...
• Trade-offs in the implementation of functionality that differs on different platforms
• Different behavior on different platforms
• Performance

To solve problems, you have to get into native mobile parts and write your renderers on elements and solve what default renderers cannot cope with.

Xamarin.Forms can be used when you need a quick start on multiple platforms at once, when performance isn't very important, or when there is a lot of old code that you want to reuse in a new application.

If you care about some unusual design, or high speed, and you write applications for sale in stores, then maybe it is better to write in native or in Xamarin Mobile.

Although the Xamarin team is actively developing its product at the moment, updates are released quite often.