To view parent comment, click here.
To read all comments associated with this story, please click here.
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
I like developing in Silverlight, very neat and great for thin web frontends. Good for customising the phone in any meaningful way? NO.
WP7 is not meant to be heavily customized. WP7 is meant to provide a consistent experience across a broad range of devices. This is why WP7 performs, looks, and feels the same across the 10 devices it launched on.
Find me 10 Android devices that do the same. Hell, find me 5. 2?
All native code does is pave the way for bugs, leaks, and performance losses. Managed code is the saving grace of the platform, and I for one hope that they never release a native SDK for general consumption.
I'd much rather them wrap native APIs in managed code and release them over time, than let people start dealing with raw pointers on WP7.
Furthermore, this was largely besides the point, I merely mentioned that OEMs get native SDK access, and that Nokia would have no trouble adapting its existing talent to WP7.
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.




Member since:
2005-11-29
Windows Phone 7 OEMs have access to the native SDK. I'm sure their C++ expertise won't go to waste.