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 574344
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

So you confirm every point including having to go back to the start screen to view status icons? That obviously isn't the case, its up to the app to show the system tray and many of them do.

Or the background tasks not updating actual data in the app? Also provably false, a push notification runs a background trigger which has a time slice of CPU execution time with which to update a cache of data. Its up to the app and many apps including Twitter do this.

The state saving goes hand in hand with app quality and can vary, bit you two wildly exaggerate the problems. I have similar problems with Android widgets which randomly stop updating, but I don't blame Android. I blame the individual app.

Reply Parent Score: 3

cdude Member since:

Its up to the app

A user unlikely knows or like to know whos responsible for a problem. There is a problem. Point. And while that blame game goes on I see very little progress too. In the future that may indeed change with Nokia assimilated and a stronger role of WP within Microsoft. Right now priority seems to be with Windows on desktop, Server, Services like Azure and Bing, xbox, Devices like Surface and RT. WP comes last. That needs to change.

Edited 2013-10-10 09:28 UTC

Reply Parent Score: 1

Nelson Member since:

The Windows Phone head runs Windows now, with all of his subordinates filling key roles in that powerful division. He brings with him the influence of the .NET stack (ensuring they aren't shunned out of the WinRT platform) and the original designers of Metro (not the copycat the Windows team did). So you're going to see a major conversion. According to Thurrot, the API unity for WP8.1 is rumored to be over 70%.

What's important is that Windows (and Windows Phone once their dust settles) will be on a yearly release schedule which should allow them ample time to move -- and Microsoft will have moved the WP code base to the more mature Windows RT stack which has support for many more ARM chipsets (including Tegra that's in the Surface) as well as Intel chips.

The inmates are no longer running the asylum in WinDiv, there's new leadership there and many things will be changing. There is a very, very real possibility that Stephen Elop will be running the whole of Microsoft soon.

Even if he doesn't -- the power struggle is over. Windows Phone won over the Windows division's objections.

Reply Parent Score: 2

JAlexoid Member since:

That needs to change only if WP is to be more than a replacement for the featurephones.

Reply Parent Score: 2