Linked by Thom Holwerda on Thu 8th Apr 2010 22:38 UTC
Apple John Gruber has found out that cross-compilers are no longer allowed in iPhone OS 4.0. "My reading of this new language is that cross-compilers, such as the Flash-to-iPhone compiler in Adobe's upcoming Flash Professional CS5 release, are prohibited. This also bans apps compiled using MonoTouch - a tool that compiles C# and .NET apps to the iPhone. It's unclear what this means for tools like Titanium and PhoneGap, which let developers write JavaScript code that runs in WebKit inside a native iPhone app wrapper. They might be OK."
Thread beginning with comment 417891
To read all comments associated with this story, please click here.
Major reason for this...
by whartung on Thu 8th Apr 2010 23:13 UTC
Member since:

The primary reason behind this is to fragment the developer space.

It will simply not be practical to create an application, from a single source base, that can be run on the iPhones C runtime, Adroids Java runtime, and Windows 7 Silverlight runtime.

Consider this another shot of the platform wars.

With scarce mobile developer resources, companies will have to choose where to put their dollars. And right now, the iPhone still has the mobile mindshare if you're targeting the mobile market.

Now, a company can write something for the iPhone, perfect any server technology, etc. and then release a new client for the other platforms leveraging their "done it once" expertise from the initial iPhone project. But what that ends up being is having a product on the iPhone first, with other platforms later.

Obviously not all shops will follow this course, but since the iPhone is the "800lb" gorilla right now, MANY will, and all of these efforts, incrementally, push the iPhone system as the premiere mobile platform.

Reply Score: 7

RE: Major reason for this...
by ebasconp on Fri 9th Apr 2010 00:13 in reply to "Major reason for this..."
ebasconp Member since:

The primary reason behind this is to fragment the developer space.

As far as I remember, Microsoft tried to do this several years ago with its IE and a lot of time they won a lot of market share and a lot of developers developing just for IE instead of doing the cross-platform thing. But in the long term, this kind of dirty plays did not triumph because the open standards and interoperability always win.

Reply Parent Score: 2

whartung Member since:

Yea, long term I don't see this going well for them. It's a matter of how long they retain their 800lb Gorilla-ness.

Basically it's a Windows vs Unix war in the enterprise space. Windows is windows, Unix is Everything Else. MS wants to promote windows development as it ties folks to their platform. Windows is the platform for First Choice for most client applications.

So, you can write applications for the iPhone, or for Everything Else. But not both (with the same source base). As long as the iPhone is dominant (and this will help keep it dominant), it's a win for Apple. But once Everything Else becomes the platform of first choice for consumers and developers, Apple can simply remove the clause from the dev agreement and join the band wagon, having held their lead as long as possible.

Reply Parent Score: 2

RE: Major reason for this...
by cb88 on Sat 10th Apr 2010 15:36 in reply to "Major reason for this..."
cb88 Member since:

Or... they will forgo iPhone development altogether as their working codebase no longer fits the platform

Android has made a significant dent in the iPhone market people that once would have had an iPhone now have a selection of various Andriod Phones to pick from that fit their taste (and not steve jobs') for instance it just so happens that a lot of people *like* having a physical keyboard

Reply Parent Score: 1