Android Ported to C#
Oracle and Google are currently in a $1 billion wrestling match over Google's use of Java in Android. — But Java is not the only way to build native apps on Android. In fact, it's not even the best way: we have been offering C# to Android developers as a high-performance …
Context & Ripple Effects
Xamarin timed its announcement to the open wound in Android's stack: Oracle's patent-and-copyright suit against Google over Java, filed in August 2010 and now a $1 billion case, has put every Java-based Android build under a legal cloud. The company's pitch — C# as a high-performance native path to Android — lands on a platform that ComScore puts at 51% of U.S. smartphones at the time of the filing-era coverage.
The pickup was unusually broad for a developer-tools announcement: The H Open Source, Ars Technica, InfoQ, SlashGear, GitHub, TechEye and 9to5Google all carried it on or about May 1, 2012, which suggests the story resonated less as a product launch than as a referendum on whether Java remains Android's necessary foundation while the technical questions behind Oracle v. Google remain unresolved in court.
First-order effects
- Xamarin gains a litigation-driven marketing window: developers worried about Java's legal standing on Android now have a shipped C# alternative, converting Oracle v. Google from a threat into a sales argument.
- For teams already building Android apps in Java, the announcement reframes toolchain choice as a risk decision rather than a default — the first credible non-Java native path pitched directly at the lawsuit's uncertainty.
Second-order effects
- If meaningful developer share migrates to C#, Oracle's core leverage in the dispute — that Google cannot easily replace Java — weakens, since the suit itself is seeding the very exit path that devalues Oracle's claim.
- Microsoft's .NET ecosystem gets an unintended mobile beachhead: every C#-on-Android app extends the language's reach beyond Windows servers and desktops, at no cost to Microsoft and entirely on Oracle's dime.
Third-order effects
- The episode points toward mobile platforms competing on the replaceability of their foundational runtimes: when a $1 billion lawsuit can threaten a platform's primary language, vendors and toolmakers alike are pushed toward abstractions that survive any single API's legal fate.
- Developer tooling consolidates around cross-platform managed languages as insurance against platform-level legal risk — a structure where the tools vendor, not the platform owner, captures the value of hedging the ecosystem.
The trend: Mobile development is diversifying beyond each platform's native language as cross-platform managed runtimes turn platform-owner legal disputes into market openings for third-party toolchains.