Xamarin.Forms not ready for combat conditions?

Xamarin is a product that makes it possible using .NET to write an application directly under 3 mobile platforms - Android , iOS and Windows Phone . Not so long ago a new technology was added to the product - Xamarin.Forms , which allows you to write one XML file with markup on all platforms at once. But how much is this technology ready for use in production?

Visual editor and autocompletions

So far, there is no visual editor or preview of what is obtained from XML (more precisely, XAML ). Yes, yes, I myself wrote quite a long time ago PHP and HTML in editors like Notepad ++, and I remember that it is quite real. But there I needed seconds to see what was going on — save and press F5 in the browser. Here you need to compile and build the application, upload it to devices or emulators, go to the necessary page ... it doesn't come out so fast.



Even more striking is the fact that when editing the markup we will not have hints on the available objects and their properties. Even when working from native Xamarin Studio. Welcome to the past ...
')

Support for ReSharper and Visual Studio

Another problem with Xamarin.Forms is that code files are generated over markup XML. It's good. But unlike the generation of code by the Storyboard editor, these files are generated when the project is directly assembled, in the temporary directory. From such joy, ReSharper goes crazy and can not highlight and advise anything normally, as indeed Visual Studio itself.



In the native Xamarin Studio with this order, but I do not really like this studio. Why are only occasionally flying errors worth trying to do the simplest thing - save the file by pressing Ctrl + S! Specifically, this does not apply to Xamarin.Forms, but this error has “stably pleased” me since last year.

Trivia from the comments

From the comments of other developers, it also turned out that, at least

• Own fonts without problems can be used only under iOS - for Android, you will have to write your own render ( Custom Render )
• There are problems with the logic of specifying the size and padding of elements, more details here.

In general, the idea is good, but right now, having played and felt the tools, I still chose the development of an individual interface for iOS and Android. Of course someone can say that I snicker, but damn it! Today, tools sometimes decide no less than the technology itself. An experienced developer using IDE hints, autocompletions and other modern joys (like statistical analyzers) can save a lot of time and avoid a lot of errors. In the case of Xamarin.Forms with this until everything is pretty bleak.

What is your experience with using Xamarin.Forms? Are you ready to endure all the flaws or have you taken it in production? Or maybe I misunderstood everything and in fact all the features necessary for me are already available, you just need to poshamanit with the settings? Waiting for your comments!