Linked by Thom Holwerda on Wed 9th Oct 2013 21:47 UTC

Paul Thurrot has a number of rumours up about Windows Phone 8.1. Two stand out to me.

Where GDR3 is widely expected to support 5- to 6-inch screens, 8.1 will supposedly support 7- to 10-inch screens as well. This obviously infringes on Windows RT/8.x tablets, so it's not clear what the thinking is there.

So, Windows RT will become even more pointless than it already is.

Aping the iPhone navigation model, Microsoft will apparently remove the Back button from the Windows Phone hardware specification with 8.1. The Back button just doesn't make sense, I was told: Users navigate away from an app by pressing the Start button and then open a new app, just like they do on iPhone. And the "back stack" is ill-understood by users: Most don't realize what they're doing when they repeatedly hit the Back button.

This I am not happy with. The back button is my main navigational input in both Android and Windows Phone, and I miss it dearly in iOS.

I'm just hoping on performance improvements, still my biggest issue with Windows Phone. I used my HTC 8X for a few hours today, and I was stunned by just how slow everything is compared to Android 4.3. Of course, application quality is another huge issue, but there's little Microsoft can do to convince developers that their Windows Phone applications are more than just side projects done between serious work on Android and iOS.

Thread beginning with comment 574419
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Comment by stabbyjones
by lucas_maximus on Thu 10th Oct 2013 18:32 UTC in reply to "RE: Comment by stabbyjones"
Member since:

Nobody would have used it.

I seen devs regularly ignore compiler warning like "THIS IS OBSOLETE AND WILL BE REMOVED NEXT VERSION" or the clocks on the production servers aren't even in right timezone.

You are assuming that people are proactive. Unless they are forced in one direction most devs won't do it.

Reply Parent Score: 2

ze_jerkface Member since:

Especially when they don't have a strong case which is what happened with WPF.

When you have existing code bases built against stable APIs there has to be numerous motivating factors for migration that have clear economic benefits, a shiny new API with a few trinkets isn't going to cut it.

Reply Parent Score: 2