Channels ▼


Xamarin 2.0 Readies Developers For A 4:1 Mobile World

Xamarin 2.0 has been released this week along with the Xamarin Studio IDE and the Xamarin Component Store. The Xamarin platform is based around a developer proposition to be able to build fully native mobile apps across all major platforms.

More Insights

White Papers

More >>


More >>


More >>

According to analyst firm Gartner, the ratio of projects focused on mobile vs. PC app development is expected to shift to 4:1 by 2015.

The Xamarin team uses this conveniently rounded off statistical projection to suggest that many projects are delayed because of the technical complexities of developing for multiple platforms coupled with the severe shortage of developers skilled in each platform's distinct programming languages.

Xamarin bids to solves these challenges by unifying native iOS, Android, and Mac development in C#, the language used by an estimated eight million developers worldwide.

"With Xamarin, businesses leverage existing in-house developer skills, code, and tools to build apps that share up to 90 percent of their source code across device platforms, essentially transforming existing teams into mobile developers virtually overnight," said said Nat Friedman , CEO and cofounder, Xamarin.

Since launching less than two years ago, Xamarin confirms that it has a community of over 230,000 mobile developers.

Xamarin 2.0 features the Xamarin Component Store, an app store for code, where developers add third-party libraries and native UI controls and themes to their apps with a few lines of code. Also included here is Starter Edition — a free tier that makes it easy for individual developers to get started and experience the power of the platform.

Related Reading

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.