-
Website
http://www.1800pocketpc.com/ -
Original page
http://www.1800pocketpc.com/2009/11/18/ray-ozzie-all-good-apps-on-iphone-will-be-ported-to-windows-mobile.html -
Subscribe
All Comments -
Community
-
Top Commenters
-
Ravicai
45 comments · 5 points
-
thulasi
3 comments · 1 points
-
zephnath
3 comments · 1 points
-
brainscrew
7 comments · 1 points
-
GTRoberts
6 comments · 2 points
-
-
Popular Threads
-
[ RUMOR ] Windows Phone 7 Features
2 days ago · 19 comments
-
The most useful feature in Windows Mobile is arguably its backup feature !!!!! What the ….
1 week ago · 26 comments
-
Thanks for your Comments
1 week ago · 11 comments
-
Does this ad work ?
1 week ago · 13 comments
-
EasyShares – Monitor your stock portfolio on the go
4 days ago · 3 comments
-
[ RUMOR ] Windows Phone 7 Features
This just shows again MS has no clue about smartphones and their users and developers...
Besides: To port an app from iPhone to WM, the iPhone developer would also require licenses for Windows and Visual Studio 2009 Pro, which sum up to about the sum (s)he paid for the Mac that was necessary for iPhone development. I doubt a lot of hobby developers would do that... But of course, all "important" apps come from professional software companies, where this and Marketplace fees are just minor costs compared to developer wages...
OK, WM is really terrible with its several installation methods (exe/PC, exe/PPC, cab, zip), and it could have been so easy - just rename .cab to e.g. .pcab, and when run on PC, install it via ActiveSync. Anyway, most users got used to that, and in most cases, it was a quite simple PC exe...
But the main reasons are 1. iPhone had big marketing (hey, how many people even knew about WM before? Even S60 was pretty unknown to the common user!) 2. iPhone offers quite easy development, given you own a Mac - WM has to cope with old APIs and a plethora of different hardware (and again, missing unified APIs for that. There even isn't a 3D API supported by all devices with 3D chip, some do DirectX, some OpenGL ES, some propietary APIs...).
(Not to mention difficulties with stability and user experience...)