On "stock" iOS5, you only see the state of the app while navigating on the fast-switching dock. This has minimal function - if at all - simply because the app is not only paused, but you have just seen it.
Also, on the iPhone the notification center totally cover up the app. As such, even the current method notification does not satisfy this requirement of yours.
I believe its important for the user to see whats going on at all times. With the iPhone as it is now, you can drag down as much as you like of the notification bar, at least I think so you can on the iPad. You can also lift it up in an increment of your choice to reveal the app behind. With your method it's either all covered or all visible. The point being here users have the choice to show both or to see the app if they want too as well as looking at notifications.
My mock up was made on MS Paint, because my Photoshop skills are non-existant. The way I could mark the running app was, as such, limited. I believe there is a myriad of visual effects and eye-candy that would allow this design to look as appealing as anything Apple has gotten us used to. And indeed, this is not something Apple hasn't ever done: on Mac OS X, running apps have a small dot and/or a highlight below then, do they not?
Of course I understand what your saying. But it would have to be something noticeable and even if it looked awesome and smooth and beautiful, its still different and still out of place on the symmetries and size of each icon.
If you closed the running app, obviously the icon and respective the highlight would disappear. I also cannot see how having an icon totally to the left of the bar + highlight could be confusing as to which app is opened at the time. I didn't get your point on the Homescreen.
Well it was simple as, true the highlight would not be there, people could be confused as to why. After all if theres a highlight for all running apps then why not on the home screen. Some people would get consumed about this. Granted, I wouldn't and neither would you but from apples point of view they could.
If you close the running app from the bar, the app would be closed, and the highlight would go away. That's it. The "multification" (as you call it) screen would be left were it was, just like it should. Also, if a user is closing an app, I expect them to know they are closing an app (and as such, realize that in the background, the app is being closed.)
Realising and seeing/knowing are two different things. Can you close your eyes and drive a car? What if your in the dark, and you press a button and you expect it to turn on the headlights, but instead it does something else because it happens to be dark outside? This might be hard to understand but its like driving a car with your eyes closed, people need to see where they are going, they can't expect something to happen and then not know if it actually happened or not.
Then again, if that is an issue, one could always have the possibility of not allowing the user to close the app from the multitasking dock. All icons could wiggle and show the "forbidden" sign, except for the running app. One could even have an warning saying "You will close the running ________ App" pop-up." appear.
A popup? Having a popup on the screen is introducing too much UI elements to the user, They will have the notification centre with all notifications. Then the multitasking bar on the bottom, and now a pop up box which warns them about the app being closed. And again. What do you mean about the forbidden sign? Or are you talking about the x, not the - sign?
If the screen is accessed from the Homescreen, the left app will not have a highlight, because it isn't running. And seriously, thinking that a user would consider the homescreen an app is pretty unnapreciative of others. xD The only reason why Apple didn't put that icon by themselves is because they had another way of returning to that app. This method compromises that way, so it finds another, which I actually find very clear.
Granted it's clear and most people would understand that. But it isn't consistent. Having things inconsistent ups the learning curve. People have to remember that this happens here, but not here. Sounds harder for new users than it is and having it consistent is easier for users and easier for apple.
And, i've seen some pretty uneducated users which have no idea about computers, but my gran picked up my iPhone, and was able to use the Maps application to scroll around. Some things are understandable others not. Although i agree its not a major drawback, but it still has some impact and could cause potential confusion and loss of data from force closing an app.
I do not think it leaves the design unclean. I do agree though that taking the app would leave a flaw on the design. Perhaps a "Back" button near the top of the Notification Centre thingy would be another idea for returning to the running app.
Personally a back button is even worse and takes up valuable space on the iPhone screen. You would already have cut the space there is for reading notifications because the multitasking bar is there. Adding a back button, where would it go I can't see a place where it could freely go without impacting on the space and user experience of the notifications. Of course you can -put- one anywhere, but there would be space on each side which is valuable and needs to be used by notifications, widgets and other things.
I suggested both double-clicking the home button or long-clicking the home button. Double-clicking is already existing on the current iOS, and does not take that long.
Well a long click would take and 'feel' longer than two clicks and is certainly longer than a single tap above the multitasking bar.
A user would know they closed the app on my method just as much as a user would know that they closed an app on the current Apple method. Same goes for returning to the app. A user knows what app he is running, and by recognizing the icon, it is also logical that clicking it will return to it. Just like clicking an app on the current method returns to it, clicking on the respective icon on this method returns to it. It really isn't that complicated.
What if i just handed my granddad the iPhone and he, somehow manages to play Cut The Rope (or rather i gave it too him with the app running.) He would never of seen the icon before, hence would have no idea what it looked like. Having no app icon on the bar at all means no need to worry about the running app and what the icon looks like.
Also, about closing an app. Theres a difference between closing and force closing. Force closing won't save data but closing it using the home button will call the multitasking functions of the app which will save its state. This would be confusing to be allowed to force close an app while its running.
Really? You think extending all your thumb up, trying to hit the spot, and swiping it down is easier than just clicking a button where your finger naturally lays down?
It depends real but overall it could have an impact over long term use. what if the iPad/iPhone is laying flat then i would still have to press the button, rather than lift up my arm, i would just need to move and place my arm instead.
It's not about the swipe down gesture. It's about the UI. The way Apple implemented the notifications has been used by Google since 2009. I bet Apple wouldn't mind saving themselves a couple thousand bucks and the public ridicule of copying the "baby OS", at the expense of no feature loss and a simpler OS architecture.
The UI, your mockup can be seen to look exactly like the current iOS 5 notification centre, which looks like the android notification bar as well. The only difference is adding the multitasking bar to the equation and changing how its initiated. That leaves one thing left which is the gesture to activate it, seems to be the only thing that matters overall.
Not really a fan of it. You have some nice points, but it looks really sloppy. I much prefer to clean sleek style of iOS.
All you're doing is taking features from the Android OS and adding it to iOS. Which will never happen. At least not the way presented above.
Care to elaborate on what 'features' are have been taken and added, which are not currently in iOS 5?
Last edited by a moderator: