@Daniel Rubino
Daniel just posted a really great editorial on what needs to be fixed right now in Windows Phone 8.
I think you got this right on almost all counts. I would disagree only with the 'X' to close apps" feature. This is my reasoning:
1)
One of the main philosophies behind WP, is that having to micromanage the technical aspects of a device (like RAM or CPU resources) is evil. The OS goes to great lengths to ensure it can manage these aspects entirely autonomously. Users should just forget about it. Adding this feature suggests precisely the opposite. It flies in the face of what WP is meant to be. It is also guaranteed to reinforce preconceived notions about how a smartphone should be used, particularly in former Android users who will feel compelled to continue micromanaging app lifespans on WP. It's akin to WP developing a dissociative identity disorder, and none of us want that, right? ;-)
2)
Very few in the WP community actually feel an urge to micromanage app lifespans. As evidenced by the majority of comments on Microsoft's
uservoice site, this feature is really about dealing with a horrid UI design flaw in IE. After having browsed the web, closing IE can require half a gazillion interactions with the physical back button. It's awful. But I ask you this. Is there not something fundamentally fishy about adding features to the OS, in an attempt to correct a design flaw in mobile IE? Even worse, might that not also encourage others to develop apps with the same horrid design flaw (huge backstacks)?
3)
There are better alternatives:
- What about adding an "exit" entry to IE's app menu?
- What about having IE recognize a gesture to instantly exit it?
- Why not separate the concepts of web-page-navigation and WP-task-navigation by adding a "backward navigation" button to the app bar, and let a single tap of the physical back button instantly return us to wherever we were before having entered IE?
I would prefer the last solution, but I think any of those suggestions makes more sense than the "X' to close apps" feature, as it solves the problem at its source, in IE.
Note: I would also move the address bar to the top of the screen (have it drop down just like the status bar on the start screen), to make room for 'backward navigation', 'forward navigation', 'tabs' and 'favourites' buttons on the bottom app bar, but that is an entirely separate issue.
4)
The back button typically returns us to the previous page or app. This navigational technique often breaks down when using mobile IE, due to the need to spam the back button. If our goal is nothing more than to return to previous app, then the "X' to close apps" feature can only be thought of as a very cumbersome workaround (at best). Calling up the task switcher (tap & hold), finding IE in the task list (potentially multiple swipes), closing IE (tap), finding the previous app in the task list (more swipes) and resuming it (tap) is quite a few steps. That is much worse then the solution I suggested in (3) which would require nothing but a single short tap of the back button. IMHO that is a more natural fit and closer to the spirit of WP than the "X' to close app" feature.
I don't know. Maybe you wouldn't mind taking this to Microsoft at MWC instead of the "X' to close app" feature suggestion. What do you think?
Your turn
What do you want in Windows Phone 8 right now?
I would refer you to AngryNil's excellent compilation of WP's greatest omissions, or as he calls it
"[REF] Possible OS Improvements"