The Year of Xamarin Development?

1423190333_thumb.pngXamarin may now be a viable tool for cost-efficient hybrid app development since it’s recent acquisition by Microsoft.

The current app marketplace is highly competitive and as the general startup market cools in

terms of funding, launch runway for apps is going to be even more important to early stage startups. Xamarin may allow cash-strapped startups to leverage code-reuse and the large pool of global C# developers while targeting both iOS and Android.

In general, developing an app natively for both platforms will nearly double the cost of client-side development and require a team to staffed with developers well-versed in Java as well as

Swift / Objective-C. Even with today’s outsourcing resources, the cost of this duplicated effort can stretch the budget of many startups.

Microsoft’s challenge will be finding a way to keep Xamarin attractive to mobile developers ontoday’s leading platforms by keeping up with the innovations and platform updates brought by future iOS and Android versions. They have to not only keep up with Apple and Google but also attract developers to develop apps for Windows 10, something that has to date proven near impossible.

 

  • Nicholas Quirk

    Nice post. I can’t figure out whom they’re trying to sell to. If I had to guess I’d say enterprises, not start-ups and contractors. For a small shop, the liscensing is really expensive. If you’re a large company and want to deploy to iOS and Android, the cost is a drop in the bucket.

    If my company wanted me to start writing mobile apps, Xamarin is definetly an option I would consider.

    If I’m looking to broaden my skillset outside of work then no way. I’d rather use Ionic as the new cross platform hotness.

  • NorwegianThirtySomething

    Xamarin has some very good developers that have been excellent at keeping up with Android and IOS SDK versions. Generally they release updates on the same day Apple do, at least. Happened with watchOS and tvOS, as well as IOS 9.2 and 9.3.