4 ms·
It's a nightmare for usability when done wrong, though it's amazing for usability when done right. For instance, a wrong way to do it is when I use the task swi
by darrenkopp 14y ago
It's a nightmare for usability when done wrong, though it's amazing for usability when done right. For instance, a wrong way to do it is when I use the task switcher to go back to Google Voice which opens up the last conversation and when I hit the back button it dumps me to the home screen, when what I really wanted was to be dumped back into the inbox. This could be solved by pushing an explicit intent or whatever onto the stack for the inbox above the conversation so that the back button works as expected.
Where the back button works awesome is where I open a link from Tweetdeck and when I hit the back button it puts me back into Tweetdeck.
- batiudrami 14y agoBut, what the button is supposed to (as given in the article), is to take you back to your previous screen - the home screen. The button on the top left is supposed to take you back to your inbox.
- darrenkopp 14y agoPerhaps, but if you are taken to a conversation regardless of how you launch the app (ie, the previous state, which is standard behavior), then I would say, no. Which is what is happening in the Google Voice application. I should state that what actually happens in this scenario is this. 1. View conversation, leave Google Voice. 2. Re-enter Google Voice somehow, currently viewing conversation. 3. Hit back button, taken to wherever you came from (previous app, home screen, etc) 4. Re-launch Google Voice, now the starting screen is the inbox.