As a Xamarin subscriber, I&#x27;m guessing the future success of the merger (and product future) depends on:<p>1) addressing the price-point,
2) core clr integration,
3) retaining the top engineering talent at Xamarin,
4) addressing the iOS designer-specific issues<p>A couple notes:<p>For most LOB apps, I&#x27;m not convinced the code re-use is significant.  The bulk of work is in the interface and navigation which is, necessarily, handled by coding android &#x2F; ios specifics.  Despite noble effort, the iOS design essentially needs to be done in xcode (point 4 above).<p>The build&#x2F;release process is and (presumably) always will be locked behind the gates of technology&#x27;s North Korea (Apple).  They can throw a switch and restrict 3rd party runtimes if and when they choose.<p>For businesses in the 5-100 million range, writing an expense app in 2017, MSDN Xamarin should be a logical choice - but it has to be a platform with the reliability of .NET and a simple cross-platform designer.  For app-centric startups, games, POS systems, etc. - it&#x27;s probably a bad move.<p>For msft devs (and we are aging) it&#x27;s win-win.  The lure of C# gets you into mobile dev, and you <i>will</i> learn iOS and Android in the process.