I'm wondering if it makes sense to have "login/register" buttons displayed on the website header. The client would be redirected anyway to the register/login page whenever it tries to access a protected resource (e.g. my account ). Still almost all the websites provide such buttons.
1
-
Some websites provide navigation links based on the privileges of the current user, so a manager or administrator may have some choices that a lacky lacks. A user who has not been authenticated may not have any choices that they are not allowed to use, hence no way to register or log in by exception. If I were visiting a site, it wouldn't occur to me to try clicking on Delete All Tables to see if I could register.– HABOJul 12, 2014 at 12:40
Add a comment
|
1 Answer
What if the user goes to you main page looking for a login option? They would have to try and access restricted functionality to trigger display of the login screen. This isn't friendly or obvious at all.
You could force all pages on the site to redirect to a login screen, but then where do you put the content aimed at people who have not created an account yet? If it is something simple like signing up for an email account then you can use this approach (and many of them do), but a big e-commerce site like Amazon needs people without accounts to be able to browse the same products as logged in users, albeit with slightly different options displayed.
answered Jul 12, 2014 at 9:24
