2 ms·
As a Xamarin subscriber, I'm guessing the future success of the merger (and product future) depends on: 1) addressing the price-point, 2) core clr integration,
by devdenver 11y ago
As a Xamarin subscriber, I'm guessing the future success of the merger (and product future) depends on:
1) addressing the price-point,
2) core clr integration,
3) retaining the top engineering talent at Xamarin,
4) addressing the iOS designer-specific issues
A couple notes:
For most LOB apps, I'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 / ios specifics. Despite noble effort, the iOS design essentially needs to be done in xcode (point 4 above).
The build/release process is and (presumably) always will be locked behind the gates of technology's North Korea (Apple). They can throw a switch and restrict 3rd party runtimes if and when they choose.
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's probably a bad move.
For msft devs (and we are aging) it's win-win. The lure of C# gets you into mobile dev, and you will learn iOS and Android in the process.