Linked by Thom Holwerda on Fri 11th Feb 2011 11:35 UTC
PDAs, Cellphones, Wireless A lot of people are wondering why Nokia didn't choose to go with Android. How can Nokia differentiate themselves when Android is a lot more open and free than Windows Phone 7? As usual, the key to this is in the details. If you read the announcements carefully, you'll see that Microsoft offered Nokia something Google most likely didn't. Update: What a surprise. Elop just confirmed Nokia has a special deal with Microsoft. Whereas HTC, Samsung, and so on are not allowed to customise WP7 - Nokia is, further confirming my theory.
Thread beginning with comment 462018
To read all comments associated with this story, please click here.
by kragil on Fri 11th Feb 2011 13:43 UTC
Member since:

Thom, it is not like good .net developers are instantly available and will have great customizations ready in no time. Maybe you should learn a few things about software development. There won't be any deep customizations of WindowsP7 from Nokia anytime soon.
Hiring and integrating people takes time. Especially when you have fire hundreds(thousands) of C++ devs.

And anyways, it is not like a Nokia WP7 phone will be ready tomorrow. It will be the end of the year. A Meego phone could have been ready by that time.

Reply Score: 2

RE: Reality??
by Nelson on Fri 11th Feb 2011 14:42 in reply to "Reality??"
Nelson Member since:

Windows Phone 7 OEMs have access to the native SDK. I'm sure their C++ expertise won't go to waste.

Reply Parent Score: 2

RE[2]: Reality??
by _txf_ on Fri 11th Feb 2011 15:00 in reply to "RE: Reality??"
_txf_ Member since:

Right... Do I have access to native apis? No...Do I want them? Yes...Can I apply anywhere to get them? No.

I like developing in Silverlight, very neat and great for thin web frontends. Good for customising the phone in any meaningful way? NO.

Meego would have allowed that. Android allows it...however android suffers from code dumps and if you wanted to send in a patch to fix any problem with android, google does not accept it (see their non Gmail mail app).

This kind of restriction limits creativity in the platform (see how some very cool iOS apps and customizations need to have jailbroken phones).

There also isn't that much general widespread available knowledge of the winCE kernel unlike iOS with darwin and WebOS and Android with the linux kernel. This also limits the fun one can have with the phone.

One might say that so what....Windows mobile had Cooked ROMs so obviously people could do something; Cooked ROMs were hacks and often rather crappy. On Android you have CyanogenMod, something simply not possible with any other platform barring meego (which I was excited for as it would have allowed CyanogenMod++ type distros and that it might even have allowed changes back into Mainline).

Edited 2011-02-11 15:03 UTC

Reply Parent Score: 2

RE[2]: Reality??
by dsmogor on Sun 13th Feb 2011 13:55 in reply to "RE: Reality??"
dsmogor Member since:

MFC/ATL are world different than QT (which isn't even pure C++). These apis are not even in the same league productivity wise. Swithing nokia lowlevel devs to these apis is completely pointess. They'd better be switched to .net or (more efectively) replaced with fresh exprienced .net team.
Let me reiterate, letting MS do the UI for N phones wasn't the baddest idea they could convey, but wasting QT potential definately was.

Reply Parent Score: 2