To be fair, when you tap into individual emails on current 8.1 devices, they have a back and forward button despite a capacitive/hardware/on-screen back button.This! Why does it have a back button at the top left when WP already has a back (capacitive/on-screen) button. This looks tailored for iOS tbh.
View attachment 94440
To be fair, when you tap into individual emails on current 8.1 devices, they have a back and forward button despite a capacitive/hardware/on-screen back button.
Might as well have the options at the top. It's hardly a crazy thing and not a great deal to complain about.
Are we now living in an age where complainers just complain? (Obviously)
My reasoning for disliking what was shown (copied from here):
The bottom and right (for right handed people) or left (for left handed people) edges are the best places for commands and navigational chrome. Controls at the top of the screen only work well for things that are used briefly and only occasionally (like volume controls).
- The occasional" back arrow" showing up seems confusing and unnecessary, given that WP has a hardware back button.
- There is already a lot of edge UI originating from the top, and all of it can cover up those navigation controls. Consider Joe's demonstration. What if he had started writing his response to the text message he received, and then realised he needs to check something in a word document? He can't, because the navigational controls are occluded by the interactive toast message. Even the small version of the audio panel that extends from the top edge would cover up half of that navigational strip. How many people will accidentally tap a navigational button, rather than expand the audio panel as they might have intended?
- A result of placing a lot of controls at the top of the screen, is that our hands will spend a lot more time blocking our view. Half the time we'll not even see the effect tapping a control at the top of the screen had, so we'll move our hand out of the way, just to move back again to invoke the next action. We're used to this on iPhones, but not on WP. It was the sum of these little things (good UI is always about little things), that made WP better. To put it more extremely, why don't we place the keyboard at the top of the screen instead of the bottom. Same reason. If Metro was all about "content over chrome", this is now about "hands over content".
a) the image posted here has two back arrows in the top bar. I doubt both are reply commands.Is there another capture that shows a back arrow?, because I think in the one posted here, that back arrow is the reply command.
Blocking the underlying UI while an interactive toast message is on screen, or while the audio panel is being shown, is a pretty bad idea. Blocking just part of the UI that is close to the overlay is even worse. Instead of just fiddling around the corners and fixing symptoms, why not go after the actual problem. That would make a lot more sense IMHO, particularly as there is no reason for these problems to exist in the first place. It's an artificial problem that is easily solved by finding a better way to host navigational chrome.Popups should block the underlying UI, or at least block the UI close to the popup. They could also make the volume popup bigger.
And they don't have to. A static row of commands and an ellipsis are, amongst other reasons, at the bottom precisely because they are not supposed to draw your attention. You're supposed to be focusing on the content. I don't think the mental overhead involved in looking for commands at the bottom of the screen is too much to ask.The bottom location has problems too, most people don't pay attention to the bottom of the screen. <snipped> So, there is a little bit of mental overhead to go for the commands at the bottom
a) the image posted here has two back arrows in the top bar. I doubt both are reply commands.
And they don't have to. A static row of commands and an ellipsis are, amongst other reasons, at the bottom precisely because they are not supposed to draw your attention. You're supposed to be focusing on the content. I don't think the mental overhead involved in looking for commands at the bottom of the screen is too much to ask.
The other arrows are to navigate to the next and previous email, those commands are in the email app in 8.1.
Besides, if that is not the reply button, where is the reply button?!.
But when people try WP, just after a couple of minutes they're asking for their iOS/Android phone back. The UI is weird, they can't find the commands, they aren't immediately visible and intuitively positioned as in the other devices, including Windows PCs.