Will Apple bundle the Mono Touch runtime with every iPhone?
Posted
by Zoran Simic
on Stack Overflow
See other posts from Stack Overflow
or by Zoran Simic
Published on 2009-09-20T06:24:34Z
Indexed on
2010/05/27
2:01 UTC
Read the original article
Hit count: 313
It strikes me as a good idea for Apple to negotiate with Novell and bundle the Mono Touch runtime (only the runtime of course) into every iPhone and iPod Touch. Perhaps even make it a "one time install" that automatically gets downloaded from the App Store the first time one downloads an app build with Mono Touch, making every subsequent Mono Touch app much lighter to download (without the runtime).
Doing so would be similar in a way to adding Bootcamp to OS X: it would make it easier for C# developers to join the party, but that wouldn't mean these developers will all stick to C#... What convinced me to buy a Mac is Bootcamp - I figured I could always install Windows if I didn't like OS X (and I liked the hardware, so no problem there). 6 months later, I'm using OS X full time...
Would there be any technical issues in doing so? I see only advantages for all parties, not one disadvantage to anyone (except maybe for the few unfortunate Apple employees who would have to test the crap out of the Mono Touch runtime before bundling it):
- Novell wins because Mono Touch becomes much more viable (Mono Touch apps become much lighter all of the sudden)
- Developers win because now there's one more tool in the tool belt
- Many C# Developers would be very interested by this
- Apple wins because that would bring even more attention to the platform, more revenue in developer fees, more potential great apps, etc
- Users win because less space is used by different Apps having copies of the same runtime accumulating on their devices
Would there be a major technical obstacle in bundling Mono Touch to iPhone OS?
Edit: Changed the title from "Should" to "Will Apple bundle the runtime?", I think the consensus on predicting that means a lot to those considering going with Mono Touch.
© Stack Overflow or respective owner