I am not sure where to post this, but the Forum seems to be the most appropriate place..
Let me start to say that I am a fan of Xamarin and have been using Xamarin Studio for over 3 years now. We have a couple of apps in the IOS and Google Play app store and would like to continue with the product. Since we are developing in C# Xamarin seemed to be the logical choice.
So far the good news..
Recently we have started to use the more "advanced" features of Visual Studio for Mac. We needed to develop a new app for both IOS and Android and already quite early on in the process it turned out that Xamarin Forms was not the right way forward. The app did not give the IOS "feeling" on IOS and neither the "Android" feeling on "Android". Our experience is that Xamarin Forms is perhaps okay for simple applications, but anything sophisticated needs a more native approach. Apart from this experience we lost a lot of time because of bugs in Xamarin.
In the next iteration we split the app in a common part and two specific UI projects. To be a bit more "modern" than our previous apps, which uses separate XIBS for the UI we decided to go for a storyboard. With hindsight we should not have done this. The Xamarin Storyboard editor is so buggy that is is almost impossible to work with. Controls suddenly disappear, Code behind code is inconsistent, Deletion of object does not delete everything. It really feels like "developing by trial and error", something that I explicitly teach my younger colleagues not to do! On a number of occasions it was necessary to switch to Xcode Interface Builder to resolve some problems.
I understand that I cannot express this general quirkiness in a single support ticket and also that if I did a support engineer would not have a clue where to start resolving it. Being a software producer myself I also know how important this "general feeling of unreliability" is for a product, even when it is maybe only attributable to a handful of bugs.
It would be very good if Xamarin would do some user observation to see how the product is used in practice and how often Visual Studio responds in imcomprehensive ways. We would definitely volunteer to be the guinea pig ;-)
Now seriously: at this moment in time I think that Visual Studio for Mac is not suitable for professional software development and would urge Microsoft and Xamarin to do something about this. I would like to know how Microsoft would address this and also would like to see feedback from other users on this topic.
Bert Degenhart Drenth
CTO Axiell Group