(Well, that's nice, it is functional and not a concern for failing toīe deterministic, but should probably be represented elsewhere) Listings? if I come here from a bookmark, do I have any clue what I The web app, and people don't know what your app will do until they
Back (Back to where? also applies to the browser's back button,īecause we all know it doesn't always do what we expect, depending on. To expand slightly on this, providing back-navigation options within your UI gives you control over their presentation: this means you can assuage anxiety over what an action result will be by clearly delineating what using the control will do.įor example, consider whether someone would have any uncertainty over what the following might do: When they load that bookmark, what navigation options do you want available to them? What navigation options do you think they will want at hand? It's a good idea to make these a consistent component of your UI, hence not worth solely relying on the back button in other instances. What if the person browsing the site bookmarks an individual product, then closes that session. Using your example, say the list was a static sale page (instead of a dynamic search). While the person using the app should ideally still have the original tab open, if you want them to be able to access the page they came from, make sure to give them a way to do so from the context of the page they are currently on. Secondly, if the page was spawned from a new tab (or a bookmark!), there may not be a back button. Sadly, one of the top reasons for this is that some people are afraid of hitting their back button within certain web applications due to broken or inconsistent browser control/state related behavior found in many AJAX heavy web apps, where using the back button may not result in the effect the person using it anticipated. Option? However, a web application should generally not rely solely on the browser's back button for all navigation that might be considered related. Your Results", leaving the browser back button as an alternative 
The web site provide a link or button that allows users to "Go back to Should the UI assume a user will use the browser back button or should
To go back to the list to click another product and view its details. Then after viewing the details, they would like That is, using the back button should have deterministic results within that application that match expected behavior (global consistency).Ī common scenario that comes to mind with this is an eCommerce site A web application should always strive to be compatible with the browser's back button.
0 kommentar(er)
