[cs_content][cs_section parallax=”false” style=”margin: 0px;padding: 0px;”][cs_row inner_container=”false” marginless_columns=”false” class=”cs-ta-right” style=”margin: 0px auto;padding: 0px;”][cs_column fade=”false” fade_animation=”in” fade_animation_offset=”45px” fade_duration=”750″ type=”2/3″ class=”cs-ta-left” style=”padding: 35px 0px 0px;”][cs_text class=”cs-ta-justify”]With the recent Microsoft Xamarin takeover it might be the right time to re-evaluate your current mobile app (strategy) and the technology stack it’s based on.
If you have been in the position where you needed to define and give shape to a mobile strategy then you’re probably familiar with the choice that needs to be made with respect to the technology stack to use.
In general this choice always ends up with 2 possibilities: either go native or choose a cross-platform solution (MADP). Within the cross-platform domain Xamarin has been one of the best alternatives there is, probably right next to going for a hybrid (HTML5) solution.
However, while being a technical sane solution Xamarin always had a few down-sides, the steep license price being one of them. While this is common in enterprise IT-land in general, it is not in the mobile space: both Apple and Google have made their mobile toolchain completely free and available for everyone. And it’s not that these respective toolchains aren’t any good; the constant battle to favour developers has resulted in arguably the best developer environments available.
So there are many ‘Microsoft houses’ out there that decided to go either native or go HTML5 for their mobile strategy, resulting in the challenge to integrate and incorporate ‘alien technology’. And while you might have climbed that hill and think you’re on top of it, now is the time to re-evaluate.
The first thing that Microsoft did when they bought Xamarin was announcing that the whole stack would be open-sourced. In the past few months they’ve kept word and indeed open-sourced various Xamarin components with an impressive speed and tenacity.
And it is exactly this move that makes it possibly worthwhile to rethink your mobile strategy. Even if you’ve got mobile apps that are mature on all levels, the idea of having them build with open-source technology that is common throughout your organisation is tantalizing. Imagine the possibilities of knowledge sharing, code reuse, efficiency improvements etc.
“But what about all those investments we’ve made into our mobile strategy? Are we’re throwing that away?” Certainly not, you should think about this as the next step. As with every other piece of software mobile apps have a (technical) life span as well, and it’s arguably even shorter than enterprise software in general. So re-thinking your mobile strategy on a regular base is good approach anyhow, and switching technology could be an additional trigger to this.
We at Xablu are in the perfect spot to help you out and guide you in this process. Not only are we senior on Xamarin and native app development, we’re also deeply knowledgeable about the processes involved. Would you want to know more about the possibilities? Get in touch!
[/cs_text][/cs_column][cs_column fade=”false” fade_animation=”in” fade_animation_offset=”45px” fade_duration=”750″ type=”1/3″ class=”cs-ta-center” style=”padding: 0px;”][x_custom_headline level=”h5″ looks_like=”h5″ accent=”false”]What can we do for you?[/x_custom_headline][cs_text]Would you want to know more about the possibilities? Get in touch![/cs_text][x_button size=”global” block=”false” circle=”false” icon_only=”false” href=”https://www.xablu.com/contact/” title=”” target=”” info=”none” info_place=”top” info_trigger=”hover” info_content=””]Go to contact[/x_button][/cs_column][/cs_row][cs_row inner_container=”false” marginless_columns=”false” style=”margin: 0px auto;padding: 0px;”][cs_column fade=”false” fade_animation=”in” fade_animation_offset=”45px” fade_duration=”750″ type=”1/1″ style=”padding: 0px;”][x_author title=”About the Author” author_id=””][/cs_column][/cs_row][/cs_section][/cs_content]