Okay hold on, Xamarin forms doesn't just work. That is a bold faced lie. Xamarin, like many other languages and frameworks has its share of zealots. Coming from

Okay hold on, Xamarin forms doesn't just work. That is a bold faced lie. Xamarin, like many other languages and frameworks has its share of zealots. Coming from a basically agnostic position on mobile development technologies I have found Xamarin to be pretty difficult to work with. Doing UI work in Xamarin is incredibly verbose while at the same time being underpowered. It certainly does not just work. To give you a better idea of the real state of Xamarin we are JUST NOW getting the ability to underline text https://xamarinhelp.com/hyperlink-in-xamarin-forms-label/ https://xamarinhelp.com/hyperlink-in-xamarin-forms-label/. But Xamarin is chock full of other gotchas. A few off the top of my head: - there is no real file picker (even third party) let alone a great file picker that can pick files locally and remotely (like from google drive). - there are a surprisingly limited number of controls available and native or not they often look terrible. - build times average one to two minutes and the debugger doesn't work about 50% of the time. - a lot of APIs that you think are supported are not. for example, they say System.Drawing is supported but it's not. So what you end up doing is writing custom implementations for each platform. I could go on but suffice it to say developing in Xamarin is not something that just works. It ONLY works because developers spend a great deal of time making sure that it works. As an aside, for my next Xamarin project I am considering doing the UI in a WebView while using C# as the back end. It would be more like a web application than a Xamarin application which would hopefully mean a nicer UI while still being able to leverage C#.