New answers tagged signup-signon
Just to clarify, this is a web-based application, from the sounds of it. So let me ask, is there an implicit assumption that users either deliberately log out of your application before they navigate away or close the browser window, or are they perhaps automatically logged out after a certain amount of time? In my current (mobile) app case I've left the ...
Try this: Show only one button. Take email address they enter and determine if you need to register them with a new account or log them in with that email. This way it's impossible for the user to select the wrong choice.
IMHO : this question is logically equivalent to another question : is the avarage user a returning user or a first comer ? Controversary , a human being is a returning user, because he registers once and use many. So , I recommend promoting the login button ,while keeping the register button well-noticed and easy to access . Best regards.
I propose that for the best UX, user login and new user registration both use the same initial form. How many times have you typed info into one of these forms only to find out that you are reregistering on the site rather than logging in or vice versa? The best solution in my opinion is to have the two important fields at the front: username and password. ...
When considering UX, consider the total user experience. That is, a user has memory and an action like logging in may occur multiple times. Thus, it doesn't need to be very prominent. There is a learning curve and the user will learn. Registration on the other hand is catered to someone that has not accessed your site before. It is a one-time action and ...
Most companies try to use their websites in the best possible manner to attract new customers. It is thus arguable to make register button more prominent. One way of doing this can be to have both the register and login buttons in the same row and use a raised button for register and a flat button for login. See android material design guidelines for buttons ...
The products these days are intelligent enough to predict their visitor intent of coming on the website based on past their past behavior. For example, If I have logged out of a website, then the next time I open it - it will know that I am a returning user (through various technical means, e.g. browser cookies) and can present a message, "Returning user? ...
The fact that some sites feature a Register button more prominent than the Login button might be attributed to the fact that these sites try to encourage visitors to register and use their services. From a normal UX point of view, an user log ins many times on a site but registers only once, so it makes sense to have the Login button more prominent.
First thoughts are it depends on if your service is established or not. The longer the company has been around I would guess the login feature would be displayed more but for a brand new start up I assume the register button would be more visible.
If your login modal fills most of the user mobile screen, users might be tempted to cancel with the Back button on mobile. If you do not handle this explicitly, your app is going to close the dialog AND also go back the browsing history. Imagine this: Google.com -> Your Landing page -> user click to login, login modal appear then user change his mind, ...
Username (that's publicly facing) should always be user customisable. That's self evident in the fact that it's called the "USERname". So whilst it's perfectly ok to use an email address as the login name, the publicly facing username must be entirely and absolutely editable at signup, and the user must be clearly informed as to what will be shown as their ...
Top 50 recent answers are included