Timeline for Should the Back button do anything from the Launcher?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 13, 2015 at 5:32 | vote | accept | Phrogz | ||
| Sep 12, 2015 at 4:55 | comment | added | Swapnil Borkar | You can take my word for it. | |
| Sep 11, 2015 at 20:37 | comment | added | Phrogz | Thanks for your answer and opinion. You have not cited any authoritative references in your answer, but based on your profile I take it that you're sufficiently in the know at google that I should perhaps take your word for it. | |
| Sep 11, 2015 at 19:09 | comment | added | nightning | +1 on @SwapnilBorkar comment. It works on the same principle as showing/not disabling the Save button on a form. Disabling it can cause confusion as the user wonder why it's disabled. ux.stackexchange.com/questions/78663/… | |
| Sep 11, 2015 at 15:50 | comment | added | Swapnil Borkar | It's for being consistent throughout the OS. If the user is accustomed to having the Back button in say 90% of the screens, removing it from one screen will need the user to adapt. Keeping it doesn't cause a harm, but can be mapped to do a different action. Also, Screen Pinning requires Back + Recents button to Unlock. | |
| Sep 11, 2015 at 15:45 | comment | added | Phrogz | Do you have a personal opinion about why the back button is not disabled, then, or whether it ought to be? | |
| Sep 11, 2015 at 15:24 | history | answered | Swapnil Borkar | CC BY-SA 3.0 |