What is the general UX rule followed wrt to navigation that a browser provides. I am developing a web based tool.I would be definately be enabling navigation to different screens within the tool, I want to understand should the same be allowed through the browser or not?

  • 2
    Leave them alone. Trying to switch them off or mess with their behaviour just annoys people who have come to rely on them working in a specific way. Mar 11 '16 at 13:43

The browser has back and forward buttons whether we like it or not. I would work with that.

If the buttons are present but made non-functional by the developer, the end-user is likely to find the experience frustrating.

  • The application should also ideally accept that the buttons exist and that pressing them should behave in the normal manner. For example, SPA (single page applications) use hash-tag navigation to produce browser history entries that can then move forward and backwards between application state.
    – phyrfox
    Mar 11 '16 at 23:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.