Does your app really need the Signup flow?

Harsh Vitra
2 min readSep 27, 2022

Do you really need a signup page? or create an account page in your authentication flow

I analyzed 100+ Authentication flow designs on Dribbble

Each of them had these common elements on their Login pages —

  • “Don’t have an account — Signup”
  • “Create a new account”
  • “New to XYZ brand, Sign up here”

Most apps have the Login page as their initial page.

And when a User enters their email/phone number and tries to log in — they end up in an existential crisis (pun intended)

So what happens behind the screen in this flow?

Several app designers follow this design architecture at the start and many never change it.

Not only we are opening places for making errors by the user but we are also adding additional logic to our system to handle these errors.

Now let's try to make this SIMPLE

Since we have the contact info (email/phone) of the user, why do we need to ask that again? We can use the same info and process it ourselves.

This saves time for your users as well as your developers.

If you need more details from the user, it can always be part of your onboarding process, which can be kept separate from your authentication flow. Also, the T&C statement can be part of your login page as well.

So think again about whether you really need a Signup page. And let me know in the comments if you have interesting counterpoints.

Make things simple.

--

--

Harsh Vitra

Problem Solver ★ Love to make things simple ★ Designer ★ Developer