Click here to Skip to main content
15,891,951 members
Articles / Mobile Apps / Windows Phone 7

Windows Phone & WinRT….why?

Rate me:
Please Sign up or sign in to vote.
0.00/5 (No votes)
15 Apr 2012CPOL3 min read 12.9K   2   4
Whilst Microsoft wants a unified platform, and as I said I understand why, would it not be better to wait and be happy that Win 8 and WinRT is successful with bugs ironed out before rolling it out across all form factors?

As I mentioned in my last post, my free time when coding, is taken up with getting my first Windows Phone application completed and published.

So whilst doing this and getting to grips with WP7 development, I started hearing about how Windows Phone will be changing (Mary Jo-Foley’s blog, Windows Phone dev blog) and that for Apollo, the next Windows phone OS release, Microsoft will make Windows Phone use the Windows 8 kernel.

My first reaction is why? Why change it? Microsoft as a company needs to get as many companies/people developing apps on the platform to make it successful. You may hear the line “it's not about the apps” but it really is, with a lot of bigger companies (like Starbucks) having and promoting apps on iOS & Android but nothing on Windows Phone, the platform looks weak and that is the last thing Microsoft and Nokia need now. It seems that Nokia need Windows Phone to be a success or they may be in trouble so you would think they wouldn’t be happy with any major change that could effect the adoption of the phone.

I read the blogs and can see and understand that Microsoft wants to have a unified environment across phone, tablet and desktop/laptop but why, when you need to get people developing on a platform, do you change how they develop on it after it being out such a short length of time? Developers have invested time and effort into learning about the phone and its foibles only to now need to look to learn new technology if they wish to continue developing on the platform in the future. Microsoft have said that existing apps, legacy apps, will continue to run on the new platform but no details are forthcoming on this at the moment.

Let's be clear that this isn’t a OS tweak, this is a major change. Silverlight gone, you can use XAML but you have to learn WinRT, the apparent good news is you should be able to develop native apps in C++, yeah great so excited about that given I last used it in any anger about 10 years ago and was happy to see the back of it, yes I know for low level performance it rocks, but for most phone apps is it really needed?

Update: I need to point out that Microsoft has said that any Windows Phone 7/7.5 apps will run on Apollo, as devs, I think we have to assume that we won't have to do anything since the need to republish apps would not be a good story for Microsoft.

If anybody knows me, you’ll know I’m not adverse to new technology, but for the life of me I cannot understand why Microsoft would do this, at this time, when they are trying to gain traction in a market dominated by iOS & Android devices.

This now leaves me wondering if I should bother to continue to invest my time in developing apps for Windows Phone 7 or should I now just focus on learning WinRT and preparing for Apollo instead?

My feeling is that a lot of developers who may have thought about doing some Windows Phone development in their spare time will now hold off until Apollo is released and anybody doing development already probably won’t plan on creating lots of new apps either. If this does happen, then you could see the number of applications in the marketplace stall which isn’t a good thing for Microsoft, Nokia or any other handset maker that needs Windows Phone to be successful.

Whilst Microsoft wants a unified platform, and as I said I understand why, would it not be better to wait and be happy that Win 8 and WinRT are successful with bugs ironed out before rolling it out across all form factors?

This article was originally posted at http://designcoderelease.blogspot.com/feeds/posts/default

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Nock Consulting
United Kingdom United Kingdom
Passionate developer, designer, Certified Scrum Professional, wanna-be architect, agile evangelist, and presenter.

Comments and Discussions

 
QuestionWhat's so big issue? Pin
Liero_6-May-12 1:34
Liero_6-May-12 1:34 
AnswerRe: What's so big issue? Pin
Nathan Gloyn7-May-12 9:44
Nathan Gloyn7-May-12 9:44 
GeneralRe: What's so big issue? Pin
Liero_8-May-12 1:24
Liero_8-May-12 1:24 
My point was that the application model will be based on the same idea (lifecycle, isolated, notifications, contracts), xaml will still be xaml (now it is silverlight 3, which is very old, so expect the new xaml to be superset of current SL for WP7), so what you will really lose?. What do you mean by "indepth understanding of a platform"? Give me an example Smile | :)

If you learn xaml now you will use this knowledge in WP8 as well.
If you learn C# you will use it in WP8 as well.
If you are using some API e.g. for making http request or parsing xml, you will google for new WinRT API. This is the lost investment?

If you are using XAML/C#/WP7 api almost nothing will change for you.


For me as a WPF developer was very easy to start with WP7 (I only had to figure out, what xaml features are missing in SL3 and understand the application model) and so it is with windows 8.

every hour you spend developing for WP7 will be advatange when you start developing for Windows 8 based mobile OS.
And when you start developing for WP8 you will be windows 8 metro-style developer as vell.

"lack of communication"
well, do you remember the panic when MS showed html5 based start screen of W8? sl is dead, wpf is dead, c# is dead, xaml is dead and bla bla bla.
I consider your worries to be similar kind of panic. It's based rumors. it's to early even for microsoft to know what they are going to do. There is nothing to communicate at the moment.


"they are risking losing a lot of goodwill from the developers that have been developing on WP7"
on the aother side, there only a few WP7 developer and maybe hundred times more W8 developers.
In the case html5/javascript will be natively supported, there's also much more such developers.

there are another much more important things that makes platform attractive or not. As a customer I would choose platform that is faster, with smooth gps navigation and less battery consumption (faster code is more efficient). As a developer I would choose plattform that I'm developing on desktop and tablet as well, because I can share knowlegde and components. I would choose platform that gives me more possibilities.
GeneralRe: What's so big issue? Pin
Nathan Gloyn8-May-12 11:45
Nathan Gloyn8-May-12 11:45 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.