Related
Hello everyone,
I just bought my desire and the first "annoying" thing is that I can't go back without using the hardware button. It would be nice to go back using a gesture like a slide from left to right (similar to the home pages navigation).
Since the display is quite big, you need to do some 'trips' between the upper part of the display and the bottom where the button is located.
Is there any utility tool which can accomplish that?
I assume because it would be rather confusing. What happens in apps that use the swipe gesture? If "back" is hard coded into the swipe gesture for the entire OS then apps can't use it. In the photo gallery swipe is for moving from one photo to the next...but if I accidentally try to share a photo and want to get out of that dialogue then I don't want swipe to move to share the previous photo instead...I want it to get out altogether.
I agree..in some applications makes no sense. Anyway, I need to have at least a soft button to go back on the upper or bottom of the display. Another solution is to have the back behavior only on some portions the display.
There is another problem which bothers me . The fonts are not so smooth..it looks like no clear type is available. Every letter have some very small pink pixels on the left side.In fact this applies for every vertical line. Is this normal?
has anyone else this pink pixels?
giony said:
I agree..in some applications makes no sense. Anyway, I need to have at least a soft button to go back on the upper or bottom of the display. Another solution is to have the back behavior only on some portions the display.
There is another problem which bothers me . The fonts are not so smooth..it looks like no clear type is available. Every letter have some very small pink pixels on the left side.In fact this applies for every vertical line. Is this normal?
Click to expand...
Click to collapse
Er...no...never seen this. You need to get that checked.
RE pink pixels.
See this article and this XDA thread.
Regards,
Dave
Where would you rather have the "search" bar/icon?
Honestly, the search bar at the top of the home-screen is pretty ridiculous. Yes, I know, I know, they wanted to put the search bar on every homescreen, so you can search easily, and from a business standpoint, it would result in a lot more mobile searches. this way people don't have to go hunting for a search box.... But, is that really the best they can do? It intrudes the screen real-estate, and you still have to exit an app, and go to the homescreen to search for something. since searching is googles #1 priority, it should be easier than that.
what they should have done is put a search icon at the bottom, next to the 'back', 'multitask', and 'home' keys. the US carriers did this the right way. With it being down there, we would free some screen real-estate, and we would be able to search something with just one tap. Another benefit would be the "voice" search. I know a lot of people don't use this feature (as i have to tell and remind all of my friends about voice actions), but this is a huge feature, whether people realize it or not. we would be able to use 'voice actions' simply by holding down the search key. ANYWHERE we are in the OS. if we're playing a game, and we want to send a quick text message, just use voice actions and send a text message without even leaving the game! Also, with the button at the bottom, we can search within apps without having to hunt for the "search" key within the app.... some apps don't even have a "search" key visible! For example, if i want to search for a previous text message about a party in Austin, i can simply tap the "search" key at the bottom and search.... The button would be in a universal spot throughout the whole OS, and we wouldn't have to go hunting around finding it.
tl;dr version:
Search key should be on the bottom, next to the home, menu, multitasking buttons.
Pros
search anywhere in the OS
Search within apps (songs, files, text messages, etc)
saves homescreen real-estate
easier to search on the web
can conveniently do voice searches anywhere in the OS, even when in a game.
Cons
adds a fourth button at the bottom?
???
there is really no reason to disagree. I really hope someone figures out a way to add that button at the bottom. It's extremely useful.
bump.
&10char
I think you need a 3rd option, neither. If I want to search the web, I can click on the icon for it. Should be a users choice, what goes on their screens.
i voted at the bottom, as i use the "press and hold the search button" a lot in the car for navigating. what i'm sure i'll end up doing is dragging the voice search shortcut from the app drawer to the launch dock to mimic the way i'm used to using it on my nexus s and nexus one.
eric b
I never really used the actual button that often. I know it's there but I always find myself going to the search widget. The only times I really hit the button was when I was in an app like the music app and searching for a song or artist. I assume that's just going to be done with the press of the app menu button and the hitting search (making it now two button presses) but I don't really mind that. They are software buttons after all so they can totally be patched in with an update if the demand for them is large enough.
I wouldn't have minded the google search bar, if it were a "true widget", i.e. when you tap on it, the cursor would appear whilst you are still in the homescreen. But, correct me if I'm wrong, but the search bar simply takes you to a google search page, so it's not even a widget!! I felt the same way when using it in Gingerbread.
What they should have done, is to create a proper active widget and given us the choice to install it on the homescreen. I probably would install the widget on each homescreen.
Alas, we have to wait to a developer to release a ROM that takes the bugger off.
The fun thing about this is that it's all software; a custom lanucher can be used, and an adventurous (Depends on the way it was written; it could be very easy or very hard) dev could add a search button. Hell, El Goog themselves could even change this if they see it fit and there's enough community support for such a change.
Bmerz said:
I think you need a 3rd option, neither. If I want to search the web, I can click on the icon for it. Should be a users choice, what goes on their screens.
Click to expand...
Click to collapse
that's the thing. the "search" button isn't just for searching. the same button doubles as a "voice actions" button. it's like an extremely convenient way to text, set reminders, notes, call "walmart" or "pizza hut", or even search where the nearest olive garden is, and navigate to it. all these options from the touch of one button. I personally use voice actions A LOT. they're extremely useful if you remember the feature is there.
Lieu10ant said:
that's the thing. the "search" button isn't just for searching. the same button doubles as a "voice actions" button. it's like an extremely convenient way to text, set reminders, notes, call "walmart" or "pizza hut", or even search where the nearest olive garden is, and navigate to it. all these options from the touch of one button. I personally use voice actions A LOT. they're extremely useful if you remember the feature is there.
Click to expand...
Click to collapse
True, I wasn't thinking about that. I was more thinking it would be nice to have a choice if it's at the top - as it's my understanding that it's at the top of all 5 screens fixed.
No biggie, and certainly not a deal breaker for me - just thought it would be nice to remove it of one wanted to.
Bmerz said:
True, I wasn't thinking about that. I was more thinking it would be nice to have a choice if it's at the top - as it's my understanding that it's at the top of all 5 screens fixed.
No biggie, and certainly not a deal breaker for me - just thought it would be nice to remove it of one wanted to.
Click to expand...
Click to collapse
agreed. i would have thought the main reason of having "virtual" buttons was so we could be able to modify them. it only makes sense.
MoDaco moved the location of the menu bottons and forced them always on so I don't see why it would be impossible to put a search button down there and a long-press couldn't simulate what we have now with capacitive buttons.
This is the best part of Android -- everything can and will be fixed by a Dev to make it work.
http://android.modaco.com/topic/348762-21-nov-legacy-menu-patches-lhs-rhs-both-normal-always-on/
I might be a minority but I abuse the search feature on android so having it on the top is actually much better for me, i use it for even find apps that are already on my phone, I can't remember when was the last time i've seen my app drawer.
Didn't have a search button for almost two years (Galaxy S), never missed it. But the positioning on every homescreen is not ideal either.
Voted option one since I'm not a fan of the search button and don't need it as a software button.
Stigy said:
MoDaco moved the location of the menu bottons and forced them always on so I don't see why it would be impossible to put a search button down there and a long-press couldn't simulate what we have now with capacitive buttons.
This is the best part of Android -- everything can and will be fixed by a Dev to make it work.
http://android.modaco.com/topic/348762-21-nov-legacy-menu-patches-lhs-rhs-both-normal-always-on/
Click to expand...
Click to collapse
wow! that's amazing. that shows a 'search/voice' key is definitely plausible.
Does anyone think that there could be great potential in the Galaxy Nexus' soft key area at the bottom of the screen? As soon as they announced that the GN would have on-screen buttons, customization came to mind right away.
We've already seen Paul O'Brien's begin with his UI patches here, but I feel like we are only scratching the surface of what can be done.
For example, with my limited pondering, I was hoping that a dev or maybe CM could soon allow us to put shortcuts on that bottom bar for quick access to the certain apps that you always use. For me, I would love for Google Talk to have a permanent shortcut on that bar that I can access from anywhere as I use it almost religiously. Also, a shortcut that emulates the power button would be highly convenient as well so that I don't have to reach up to the side button as often. I can also foresee some themeing or button rearrangement and so forth.
Do you guys have any other ideas? As I'm not a dev of any sort, maybe I'm out of line in thinking that the bottom bar is flexible enough to customize. However, if it could be done (and Paul O'Brien already has demonstrated that maybe it could), the possibilities could be endless.
As a webOS user, I'd love some swipe gestures implemented for 'back' and a swipe up to open the app drawer
a swipe up for the drawer would really nice
Damn, I didn't even think of swipe gestures at all. Now my mind is really running wild.
bump for more ideas!
swype gestures are already available on go launcher
subxero123 said:
swype gestures are already available on go launcher
Click to expand...
Click to collapse
But we're not talking about the launcher. Didn't read the post huh?
I wish we could swipe down to make the thing disappear, which allows us to take advantage of the full 4.65 inch screen.
Swipe down - disappear
Swipe up - appear again
I think would be awesome if we could swipe the regular buttons to the side, showing new options (like we do with dock bar in almost every popular launcher). There, we could use app shortcuts, power widgets and other stuff, like the search and the option buttons.
I agree, I hope this is just a tip of the iceberg, it seems pointless to have all this potential and not utilize it.
how about instead of the soft keys have it scroll:
"wwwwwaaaaaasssssssssssuuuuuuuuuuuuppppppppppppp!!!!!!!!" w/ flashing text.
seriously though, being able to make them appear/disappear anytime would be a big plus in my book.
or say if you're playing a game/watching a movie, and someone calls you... rather then having the call notification pop up & take over, have the notification just appear in the soft key area.(i guess same for texts)
I think instead of putting toggles with the notification bar, a scrolling dock with these would be even better.
Like you guys said, swipe on the dock to the left or right to reveal Wifi/BT/GPS/etc. This seems easier than swiping down on the notification bar to bring it down.
On honeycomb we could hide them and theme them. Change animations and icons.
They didn't figure out how to add more or change up the order or add functionality because honeycomb wasn't open source like gingerbread and ICS.
So yea. Expect lots of cool stuff.
-Galaxy Nexus
-Asus Transformer
Since Android came out, I was hoping we would switch to soft-keys. Now we can fully customize the buttons, select preferred positions, preferred icon style, and which icons you actually have...
I'd be pretty content to just Swap the Menu and task manager buttons... I dont need a permanent task manager button that takes as much time to operate as it does to just navigate to the apps icon itself.. the menu button on the other hand I use in just about every app I launch.
sodequis said:
I'd be pretty content to just Swap the Menu and task manager buttons... I dont need a permanent task manager button that takes as much time to operate as it does to just navigate to the apps icon itself.. the menu button on the other hand I use in just about every app I launch.
Click to expand...
Click to collapse
I thought this too until I actually got down to using it on the GN.
I never used the task switcher on my other Android devices as it seemed too difficult and took too long for it to be worth it. However, having been using the GN for a couple of days now, I find its implementation (just a single tap) to be much more friendly and useful. I find myself using it all the time now to switch between what I am doing and can't imagine not having it.
player911 said:
On honeycomb we could hide them and theme them. Change animations and icons.
They didn't figure out how to add more or change up the order or add functionality because honeycomb wasn't open source like gingerbread and ICS.
So yea. Expect lots of cool stuff.
-Galaxy Nexus
-Asus Transformer
Click to expand...
Click to collapse
I'd just like to know what devs to talk to in order to make it happen
I was hoping for some app specific keys. For instance in the browser have a Forward, Back, Stop/Reload, Home, etc.
id love to see the buttons replaced with like gif animations. so cool
Enhanced said:
I thought this too until I actually got down to using it on the GN.
I never used the task switcher on my other Android devices as it seemed too difficult and took too long for it to be worth it. However, having been using the GN for a couple of days now, I find its implementation (just a single tap) to be much more friendly and useful. I find myself using it all the time now to switch between what I am doing and can't imagine not having it.
Click to expand...
Click to collapse
But, why not just allow the "Home" button to be the task-switching button via long-press like before? Is that extra pause for the long-press what you're referring to when you say it took too long?
Anyway, I, too, would like the Menu button back, but more importantly I want the Search button back. I can't wait for the ability to get rid of the G Search widget, put a dedicated Search button back in the soft touch area, and have the Home button as the task-switcher.
Brandon
I've been realizing lately how amazing android really is and customizable it is with this phone. Off topic but I kinda hated the fact. Of a recent app button and the fact that I lost the menu button (honestly the most used button on all my other phones). The devs here realized it and gave me the ability to have my menu button, get my search button back, and make recent apps come up by holding the home button. Got to love them. Shout out to our fantastic devs.
Now the point of this thread was just I wanted to know how you guys thought about a gesture bar instead of having buttons. So swipe on the bar to go back, maybe swipe up to go home etc? Just trying to think of creative ideas on how to use this huge screen and since everything is virtual, why can't this be possible. What you guys think?
Sent from my Galaxy Nexus using Tapatalk
nice idea, kind of like the microsoft touch mouse. I would like to see someone make that possible and see how it works out.
Shaquiel Harris said:
Now the point of this thread was just I wanted to know how you guys thought about a gesture bar instead of having buttons. So swipe on the bar to go back, maybe swipe up to go home etc? Just trying to think of creative ideas on how to use this huge screen and since everything is virtual, why can't this be possible. What you guys think?
Click to expand...
Click to collapse
As a technical exercise it sounds like a very good idea, but I know for one I wouldn't use it. Dolphin HD has had gesture support for such a long time and I used it as my main web browser on my Desire but I didn't ever use the gesture support.
Even my HD2 running WM 6.5.x had an app that allowed you to launch any app/program by configuring a gesture, but again I didn't use it.
I guess it's just easier to place my thumb than to move about when holding the phone in one hand. Is this an idea you were thinking of implementing yourself, or are you looking for someone to pick the idea up and run with it?
Kalavere said:
As a technical exercise it sounds like a very good idea, but I know for one I wouldn't use it. Dolphin HD has had gesture support for such a long time and I used it as my main web browser on my Desire but I didn't ever use the gesture support.
Even my HD2 running WM 6.5.x had an app that allowed you to launch any app/program by configuring a gesture, but again I didn't use it.
I guess it's just easier to place my thumb than to move about when holding the phone in one hand. Is this an idea you were thinking of implementing yourself, or are you looking for someone to pick the idea up and run with it?
Click to expand...
Click to collapse
Are you talking about lmt? Fyi: it's now also available for android/gsn...
http://forum.xda-developers.com/showthread.php?t=1330150
Sent from my Galaxy Nexus
Shaquiel Harris said:
I lost the menu button (honestly the most used button on all my other phones).
Click to expand...
Click to collapse
You never lost the menu button, it's just not on screen 100% of the time anymore, where it would just waste space otherwise.
I think its great idea!
Another few things that would be cool to see would be, resizing the Navigation Bar to be maybe a little thinner, and being able to slide the nav bar left or right, to reveal a icons to launch other apps, and maybe swiping down to hide the navbar all together.
Like you said being able to customize android and change every aspect of it is what makes this OS so awesome.
You guys ever use gesture area on webOS phones? Much better than using back key, would be a great idea. It also used visual feedback so a white line would go in the swipe direction. Currently the only phone using something similar to this is the N9 probably, which has swiping through the sides of screen to control apps.
I was just thinking about WebOS when reading this as well. Would be nice.
Just having the soft keys area as a gesture area? cool!
Maybe you could customize your gestures?
A big thing to me would be the ability to have a fully loaded package and be able to switch between stock softkeys, added search/menu softkeys, and gestures. Everything customizeable by user rather than through flashing?
menu bar like in windows 8
I think gesture is pretty good, but i`d like to see menu bar(home, recent, etc) like in win8: it is hidden until you swype from bottom-outside up, than it become unhidden. see any wideo with windows 8 tablert, you`ll see what i mean.
MrBIMC said:
I think gesture is pretty good, but i`d like to see menu bar(home, recent, etc) like in win8: it is hidden until you swype from bottom-outside up, than it become unhidden. see any wideo with windows 8 tablert, you`ll see what i mean.
Click to expand...
Click to collapse
That would get annoying pretty quickly. I don't want to have to add extra steps to navigate my phone. Back, home and recent app are buttons you use all the time, why add a barrier to get to em? More screen real estate isn't worth the extra hassle.
Enhanced said:
That would get annoying pretty quickly. I don't want to have to add extra steps to navigate my phone. Back, home and recent app are buttons you use all the time, why add a barrier to get to em? More screen real estate isn't worth the extra hassle.
Click to expand...
Click to collapse
How about navigational controls similar to the quick controls in the stock browser? Touch the bottom edge of the screen and out pops a semi-radial menu that can contain: back, home, recent apps, menu, search and can be used to add quick shortcuts to your most used apps like messaging, contacts, browser, etc., or app specific commands, like say refresh for browser, check mail for, well, email, and so on. Touching the edge requires less effort and movement as compared to swiping up or down.
I came to Android from webOS after HP shot themselves in the foot several times and one of the things I miss most is the gesture bar you had at the bottom of the screen. With the advent of the soft button area in ICS I see a real option to enable the area to work in a similar fashion. Hell yes!
The webOS gestures were:
A single swipe up would show you your running apps.
Swiping 2 fingers up would show you the launcher (app drawer).
A leftward swipe would go back.
A full swipe across the entire area going either right or left would take you to the next or previous running app.
Besides the wireless charging, the gesture area was one of the webOS killer features you very quickly learned to take for-granted. So long as gesture detection was implemented well I don't see why you couldn't have the soft buttons as they are now and gestures all working at the same time.
Call me old fashioned, but I also don't like the gestures idea.
Dolphin is just about the only program on android that I have tried to use gestures with, and it's not the sort of feature i'd personally like integrated into my phone.
That said, customizing how different people can use their phones, within the same operating system, so two people can use the exact same phone in two totally different ways, is the way to go
j.go said:
How about navigational controls similar to the quick controls in the stock browser? Touch the bottom edge of the screen and out pops a semi-radial menu that can contain: back, home, recent apps, menu, search and can be used to add quick shortcuts to your most used apps like messaging, contacts, browser, etc., or app specific commands, like say refresh for browser, check mail for, well, email, and so on. Touching the edge requires less effort and movement as compared to swiping up or down.
Click to expand...
Click to collapse
I like your idea of having the pie control from the stock browser available all over android. I had the idea a while back but was just too lazy to implement it. Today I did a small working prototype and I think I will add the pie control feature to my gesture app "LMT"...
good idea but put ot optionaly! maybe it is not practical ! iwould rather hidden button ! like Video player amaing full screen with hidden buttons !!
Huntlaar said:
good idea but put ot optionaly! maybe it is not practical ! iwould rather hidden button ! like Video player amaing full screen with hidden buttons !!
Click to expand...
Click to collapse
If implemented properly, you might be able to do away with the bottom bar and take advantage of the full screen. You can't see it with the nexus browser, but if you have a tablet running ICS and enable browser quick controls, the app hides the tabs and address bar, instantly adding an inch of usable screen real estate at the top.
Sent from my Galaxy Nexus using XDA App
The big nasty problem with having hidden buttons or, for that matter, any trigger point area(s) on the devices main screen is you'll always end up triggering something when you didn't want to or it interferes with a ui element in one or more apps e.g. game scroll bars / buttons. I've tried plenty and they all interfered with one app or another to the point I stopped using them.
The quick controls idea is fine but you're still having to watch what you're doing. The beauty of gestures in webOS was that you wouldn't have to take your eyes of what you were doing to find a button - your finger just flicked below the screen content while your eyes looked towards what you were going to do next.
I realise it's hard to imagine if you've never done it before but (weak analogy approaching...) think of it like walking up a thin and narrow set of steps as opposed to thick wide ones while trying to read a book. On the narrow steps you have to look down to hit the next step thus breaking the flow of your reading. While on the bigger wider ones you can carry on reading as the step is big enough your foot can find it without taking your eyes of your book.
Anyroad, IMHO, gestures need to be out of the way of app content so as not to interfere with app usage patterns and shouldn't require the user to take their eyes off what they're doing.
I'm hoping the discussion in this thread can inspire devs to really tweak Android.
An article I read a while back through Daring Fireball really got me thinking on how to fix the back button. This quote in particular:
They’ve replaced dumb hardware buttons with equally dumb software buttons.
Click to expand...
Click to collapse
http://daringfireball.net/linked/2012/01/16/android-buttons
This is also a good discussion on the topic:
http://www.theverge.com/2012/4/10/2...uidelines-update-settings-navigation#98209921
This is what I've come up with:
The back button should be dimmed or not visible at all when looking at the home screen.
This should also be the case for looking at the home/main scene of an app, for this reason:
The back button should never take you out of an app to the home screen, that is what the home button is for.
Instead of using the back button to close apps, use the task switcher to swipe away and actually close unwanted apps.
I know all this is possible, I just don't know how feasible it would be. I would love to see these changes in Android, what do you think?
I actually use the back button to exit out of applications, this way the app get's a chance to save any information to files. if it's forced closed, these writes can sometimes get missed and cause inconsistencies in the app (or lost time if game progress is not saved).
Having it on the home screen maintains a consistent look that many people appreciate. What i find is fantastic now is how the button rotate to the right place regardless of orientation, I KNOW that if I'm in landscape, the buttons will always be on the right hand side.
The buttons also dim down to dots in some applications (not sure if it's a new API) look at the camera app to see this in action. This removes the aesthetics of the bright buttons while leaving the functionality.
I guess you can argue about anything these days. The software keys will work better as apps are updated to 4.0 API, but to get full use out of them use AOKP, or just remove them altogether and use LMT's Pie menu. Problem fixed.
If the user accidentally opens an app, it wants to go back to where he was before. If the user opens Maps from the Gmail app, and the user wants to go back, the only way to do so is by pressing the back key.
If the user is in the App Drawer, accidentally opens an app, it wants to go back to the app drawer, and not back to the home screens.
The home button doesn't close the app, but tells the app that it's moved to the background.
The back button closes the app, tells the app it is being destroyed and lots of memory will be given back to the system.
With Android, it's possible to open app X within app Y(if the developer of app Y wants the user to do so). It wouldn't make any sense if the user had no way to undo that operation.
In my opinion, the navigation buttons are used properly.
EDIT:
Matridom said:
I actually use the back button to exit out of applications, this way the app get's a chance to save any information to files. if it's forced closed, these writes can sometimes get missed and cause inconsistencies in the app (or lost time if game progress is not saved).
Click to expand...
Click to collapse
The Android Documentation states that developers should save their data when onStop is called. onStop will be called both when user presses the home button, and when users presses the back button. So in theory, both buttons should work fine.
The buttons also dim down to dots in some applications (not sure if it's a new API) look at the camera app to see this in action. This removes the aesthetics of the bright buttons while leaving the functionality.
Click to expand...
Click to collapse
Yes, that's an API. It's possible to dim those buttons in some apps(like gallery/camera), and it's also possible to hide those buttons. The buttons will re-appear as soon as the user touches the screen. Look at the YouTube app if you want to see the buttons disappear and re-appear.
fifarunnerr said:
If the user accidentally opens an app, it wants to go back to where he was before. If the user opens Maps from the Gmail app, and the user wants to go back, the only way to do so is by pressing the back key.
If the user is in the App Drawer, accidentally opens an app, it wants to go back to the app drawer, and not back to the home screens.
The home button doesn't close the app, but tells the app that it's moved to the background.
The back button closes the app, tells the app it is being destroyed and lots of memory will be given back to the system.
With Android, it's possible to open app X within app Y(if the developer of app Y wants the user to do so). It wouldn't make any sense if the user had no way to undo that operation.
In my opinion, the navigation buttons are used properly.
Click to expand...
Click to collapse
I agree. I dont think it is "broken". It works well for me and I hate using my friend iPhone because it doesnt have a back button and I have to find it on screen.
Matridom said:
I actually use the back button to exit out of applications, this way the app get's a chance to save any information to files. if it's forced closed, these writes can sometimes get missed and cause inconsistencies in the app (or lost time if game progress is not saved).
Click to expand...
Click to collapse
I'm not talking about force closing apps, just regularly exiting apps only when they are swiped away from the multitask menu. I agree with everything else.
miketoasty said:
I guess you can argue about anything these days. The software keys will work better as apps are updated to 4.0 API, but to get full use out of them use AOKP, or just remove them altogether and use LMT's Pie menu. Problem fixed.
Click to expand...
Click to collapse
I'm not talking about removing the icons altogether, just make them contextually aware.
fifarunnerr said:
If the user accidentally opens an app, it wants to go back to where he was before. If the user opens Maps from the Gmail app, and the user wants to go back, the only way to do so is by pressing the back key.
Click to expand...
Click to collapse
This isn't the case anymore with ICS. I think the multitask button should be utilized instead. Granted, it's one extra tap, but I think it's more consistent.
fifarunnerr said:
If the user is in the App Drawer, accidentally opens an app, it wants to go back to the app drawer, and not back to the home screens.
Click to expand...
Click to collapse
I don't think that should happen. I realize that I'm arguing against actions Android has done since it's inception, but I believe that they are wrong now.
fifarunnerr said:
The home button doesn't close the app, but tells the app that it's moved to the background.
Click to expand...
Click to collapse
The home button shouldn't close an app, they should never have to unless the system decide when it needs to close an app, or the user does by swiping it away.
juliano_q said:
I hate using my friend iPhone because it doesnt have a back button and I have to find it on screen.
Click to expand...
Click to collapse
The same is for me as well, muscle memory is much faster. I just think the potential of the virtual back button is not even being scratched at yet.
thereddog said:
This isn't the case anymore with ICS. I think the multitask button should be utilized instead. Granted, it's one extra tap, but I think it's more consistent.
Click to expand...
Click to collapse
In Android, there are 2 ways of launching an app:
- As a new Task, this will add the app to the multitask interface
- As the same task, the new app won't be added to the multitask interface.
If you would like to see the second one, go to the Play Store, and click on the Email button. The Gmail apps opens. Now press the home button and open the multitask interface. You won't see the Gmail app, only the Play Store. If you open the Play Store, it'll open the gmail app, since it's the same task.
Press the home button again, and open the Gmail app(from the app drawer). The draft of the Play Store email won't show up, but it'll open the Gmail task that you opened before(for example, your latest received mail).
So, the multitask button won't work properly when the second way of launching an app is used.
The home button shouldn't close an app, they should never have to unless the system decide when it needs to close an app, or the user does by swiping it away.
Click to expand...
Click to collapse
In some cases, the back button would fit better. When you're in the Paypal app and want to close it, it's much easier to press the back button(then the user logs out), instead of pressing home, multitask button, and swipe away(thats 3 times as much time/energy).
In Android, there are 2 ways of launching an app:
- As a new Task, this will add the app to the multitask interface
- As the same task, the new app won't be added to the multitask interface.
If you would like to see the second one, go to the Play Store, and click on the Email button. The Gmail apps opens. Now press the home button and open the multitask interface. You won't see the Gmail app, only the Play Store. If you open the Play Store, it'll open the gmail app, since it's the same task.
Press the home button again, and open the Gmail app(from the app drawer). The draft of the Play Store email won't show up, but it'll open the Gmail task that you opened before(for example, your latest received mail).
So, the multitask button won't work properly when the second way of launching an app is used.
Click to expand...
Click to collapse
I actually agree with this. The back button would be used to to back into the store. GMail was never really opened though so it wouldn't have to be closed.
When you're in the Paypal app and want to close it, it's much easier to press the back button(then the user logs out), instead of pressing home, multitask button, and swipe away(thats 3 times as much time/energy).
Click to expand...
Click to collapse
In this case, I believe it is up to PayPal to have a Log Off button on the main scene of their app, and possibly in a context menu in other scenes.
although I get your main premise, I think it might be extra confusing when you have buttons just "randomly" disappearing and reappearing.
martonikaj said:
although I get your main premise, I think it might be extra confusing when you have buttons just "randomly" disappearing and reappearing.
Click to expand...
Click to collapse
Maybe not disappear, dim would work
thereddog said:
Maybe not disappear, dim would work
Click to expand...
Click to collapse
Possibly. But I think what you're looking for is a fundamental reworking of the OS here. The "Back" button is meant to work a certain way (completely at the OS level), and changing that changes everything.
What you're really looking for is the iPhone setup, where all you have is a "Home" and "Multitasking" (just double tap home, could be a separate button). All "Back" functions are handled at the app level, not the OS level. Back buttons are placed at the discretion of the developer.
The consistency provided by the Android way of handling "Back" at the OS level has many advantages I think.
The software keys actually work great. I've never had a problem with them. The menu key always comes up when its needed and I'm not finding myself missing the search key either.
Sent from my Galaxy Nexus using XDA
the whole back button talk has got me thinking. do you guys think the back virtual button will go away any time soon since the new style guides want a back button in the top left corner.?
The way the android back button works is simply brilliant and I hope it never changes. The application stack is very thoroughly thought out and designed for a specific reason. As already mentioned there are many examples/situations that wouldn't be possible if there was no activity stack history with the back button function. You just have to learn how the activity stack works.
And yes you should ALWAYS use the back button to leave an app, never home. It clears that activity stack. Only time to use home is when you want to background said app to come back to later, ie multitasking.
I pray to god they don't change the way the back button functions. I like having all my keys lit up whenever I'm not using a full screen application. I like that the back button goes through different apps/pages when you close out of it. This just integrates multi-tasking soooo much better. I don't want to have to wade through different clicks and apps just to get to a place I was before (i.e. backing into a different application). I'm not sure I understand the premise of this... please elaborate?
It is entirely possible to implement this in the OS, it's just a question if Google wants to do this. I personally am well adapted to Android's back button, and find it much better for multitasking than Apple's iOS design. Example:
1. Open Twitter, click on link from Tweet
2. Android opens the browser, I read whatever was posted, then hit back
3. I return to my Twitter feed, ready to move onto the next Tweet
This works in a multitude of apps, from Reader to Google Music to anything that wants to keep the previous app alive in the background. Can you imagine having a back button in the Browser that could both take you back a page and also take you back to the app you used to launch it? Apple's iOS solves this by eliminating any form of efficient multitasking in my opinion, as you have to double press home and select the previous app. The iPad does it better with gestures, but a soft back-key would easily suffice.
Additionally, Apple's iOS also has a varying design for the back-key, it's in different places for different apps. I personally love the static back-key on Android, and I've used both on a daily basis. You could dim the back button when on the home screen, but that would leave a gaping hole in the Navigation bar, in addition of wasting RAM/Processing power continuously disappearing and reappearing the key when you move from home-screen to app.