I've read the advice, "don't break the back button" from multiple sources. For content-based browsing I agree with this 100%. Does the same advice apply to web applications? I feel that it is still ...
I am re-designing a multi-page web form that currently contains 'back' and 'continue' buttons. I am wondering -- is the 'back' button necessary? If the user wants to go back, they will know to use ...
I've been reading and looking at different iOS apps to design the UI for mine, and it feels like sometimes the difference between using a modal view or a non-modal view is not entirely clear... for ...
The back button is a great "get out of a flow's dead end" option that browsers provide. Should a UI rely on the back button as the only method to allow a user to get to the previous page or should the ...
I am developing an android application which has quite a few dialogs that just contain text and an 'OK' button. Pressing the 'OK' button loses the dialog, as does pressing the 'back' button on the ...
On the Android, is the expected action of the back button to navigate backward through menus, or does it just go "back" to the previous screen you came from? I don't have an Android device to sample ...
What's the reason that so many site these days "break" my back button experience? Even stack does this: I read a question expand the comments, scroll to the first answer, follow a link, decide I'm ...
I am building a mobile application that uses a button to launch the navigation menu (much like the Path or Facebook interface). I also want to add a back button. The standard seems to be to place ...