Designing login and sign up screens
Practical guidance for login and sign up screens, including fewer fields, password help, social login, guest options and clear error handling.
Nobody wants to create an account. They want to book the appointment, buy the thing or see their invoice, and the sign up form is standing in the way. Treat every field and every rule on that screen as a cost your customer pays before they get any value.
The aim is to get people through quickly and safely, and to make coming back even easier.
Do you need an account at all?
Ask this first, because the best sign up screen is often no sign up screen.
Say you run a florist with online ordering. A customer sending flowers once a year for a birthday gains nothing from an account. Forcing one will lose some of those sales at the last step. A guest checkout that asks only for what the order needs is the kinder option.
Accounts earn their place when the person will return and benefits from being remembered: saved addresses, order history, upcoming bookings, private documents.
A good compromise is to let people finish as a guest, then offer an account afterwards: "Want to save your details for next time? Just add a password." By then most of the form is already filled in, and the benefit is clear.
Ask for less
Go through your sign up form and challenge each field. Do you need it right now, or is it something marketing would like to have?
For most small business apps, sign up needs:
- An email address or mobile number
- A password, or no password at all (more on that below)
- A name, if you will use it
That is usually enough. Date of birth, postal address, "how did you hear about us" and company size can wait until there is a reason.
Collecting less is also simpler from a privacy point of view. As a general principle, only collect personal information you actually need, and check the official privacy guidance for what applies to your business.
Some smaller touches that help:
- One column, labels above the fields. Easy to scan and easy to tap.
- Use the right keyboard. The email keyboard for email fields, the number pad for phone numbers.
- Support autofill. Let the phone or browser fill in saved details and suggest passwords.
Make passwords less painful
Passwords are where most frustration lives.
- Show the rules upfront. If you require a minimum length, say so beside the field, not after a failed attempt.
- Keep the rules sensible. Length matters more than forcing a mix of symbols. Fussy rules produce passwords people cannot remember.
- Add a show password option. The little eye icon. Typing blind on a phone keyboard causes endless typos.
- Allow pasting. Blocking paste breaks password managers, which are the safest way for most people to handle passwords.
- Make "Forgot password?" obvious. It is one of the most used links on any login screen. The reset should be a link sent by email or text, with a couple of steps at most.
Skipping the password
Many apps now let people log in without a password at all. You enter your email or mobile number and receive a one time code or a link. There is nothing to remember and nothing to forget. For apps people open only now and then, such as a clinic's booking portal, this is often the best choice.
Should you offer social login?
"Continue with Google" or "Continue with Apple" lets people sign in with an account they already have. One tap, no new password.
The upsides are speed and fewer forgotten passwords. The downsides:
- Some people do not want to link accounts, so always offer email as well.
- People forget which method they used last time. They signed up with Google in March and try email in June, and now they seem to have two accounts or none.
- Each provider has its own rules. Check the current requirements for the app stores you are publishing to, as they can dictate which options you must include.
Our advice: offer one or two well known options at most, alongside email. A wall of six logos creates confusion.
Handle errors without blame
Login errors are frequent, so design them carefully.
- Say what is wrong, next to the field. "That does not look like an email address" under the email box.
- Keep what they typed. Never clear the form on error.
- Offer the next step. After a failed login, show "Reset your password" right there.
- Be careful with detail on login. Messages such as "No account with that email" can reveal who is a customer. A general "Email or password is incorrect" is the safer wording, paired with an easy reset.
A checklist before launch
- Can someone complete the main task without an account, or is the reason for requiring one clear?
- Are there four fields or fewer on sign up?
- Are password rules visible before typing?
- Is there a show password option, and does pasting work?
- Is "Forgot password?" easy to see, and does the reset work on a phone?
- Does autofill work on both iPhone and Android?
- Have you tested every error by causing it yourself?
Run through it on a real phone, with one thumb, standing up. If you can sign up in under a minute and log back in within seconds, your customers will be able to as well.