Linked by Thom Holwerda on Thu 8th Apr 2010 22:38 UTC
Permalink for comment 417891
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2005-07-06
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.