User
authentication

A redesign of TN’s login, sign-up and password change. A flow built to grow the registered user base and to be simple and accessible for people over 50.

Iniciá sesión o registrate

Try it with any email. facu@email.com already has an account. It’s a replica: it doesn’t store or send anything.

Client
TN, Artear
Year
2025
Role
Product Designer
Focus
Research, usability testing, accessibility, UI

Context

We set out to improve our users’ experience when signing in or creating an account.

Business problems

  • Get more registered, logged-in active users on TN.
  • Get more active users in the games section.

Usability problems

  • Friction when completing sign-ups, mainly at the blocking “wall” in front of the games.
  • Frustration at login when trying to sign in successfully.
  • No way of knowing which login method had been used last.
  • An outdated design with poor accessibility.
TN’s previous login with the most-clicked areas marked, based on the Clarity heatmap

We analysed how the flow was built to decide whether it could be adjusted or had to be rethought from scratch. We decided to redesign it: better organised, more accessible and, above all, simple for people over 50.

Benchmark

We looked at competitors and at the feature in general, to understand how they solved this flow, what we could use and where we could stand out.

The last method used

Lovable shows a badge that tells you which sign-in method you used last.

Sign-up in steps

A national news outlet uses a stepper to show which step of the sign-up the user is on.

An input that decides

An international news outlet uses an input that detects whether the email already has an account and, based on that, sends you to sign in or to create an account.

Userflow

With the problem, the goals and the analysis clear, we redesigned the user flow. That let us see every possible scenario clearly.

Flow diagram: the user enters their email and, depending on whether it has an account, continues to sign-in, to the three-step sign-up or to the password change
FrontstageLogin and sign-up screens, error screens and success screens.
BackstageEmail validation against the database, email delivery, error handling and password requirements.

Visual definition

With the flows defined, we moved on to the visual design of each screen: sign in, create account and change password.

Start
Start screen on mobile: an email field, and Google and Apple sign-in with the “Último usado” (last used) badge
Create account, step 1
Create account screen, step 1, on mobile: a three-step stepper, email and password with its four requirements validated as you type
Change password
Change password screen on mobile: an email field to receive the link

The real interface, rebuilt from the design file. Mobile, at 360 px.

The components

The stepper and the input, built as reusable components with all their states. They’re live: you can try them.

Stepper
Step

Shows sign-up progress. The active step is blue, and each completed step turns green along with its line.

Input
  • Mínimo 8 caracteres
  • 1 minúscula
  • 1 mayúscula
  • 1 caracter especial
State

Validates the four requirements as you type and warns you if Caps Lock is on. Type a password to see it.

Errors and accessibility

Input states: wrong email format, email without an account, empty field and Caps Lock warning

Accessibility

The modal works as role="dialog" with aria-labelledby and starts with focus on the first input. Messages are marked with aria-invalid and role="alert", and there are descriptive tooltips, for example for the special characters.

Errors

Explicit, accessible error states, with no generic messages. Every input has its label, iconography and a text that explains exactly what is going on.

Error prevention

Caps Lock detection while typing the password. Some devices have it built in and others don’t, so we added it to make sure it always shows up.

Prototype in Figma Make

We built a high-fidelity prototype that replicates the real logic of login and sign-up: validations, password requirements, error states and step-by-step progress.

That let us test the flow on mobile almost as if it were already built, measure task times and catch real friction before going into development.

Because every screen was built with reusable components, auto layouts and clear instructions, the result in Figma Make came out practically identical to the design.

Try the replica in the hero

Usability testing

We tested the prototype with users before developing a single screen.

5users, in person

92%of our users are on mobile

GoalValidate the wall that requires users without an account to complete a full sign-up before they can play.
What we measuredTask conversion, time and perceived usability.
How we did itOn mobile, with a fictional scenario and a task script. We recorded audio and screen, logged the results in an Excel sheet and added questions to gather qualitative insights.
TaskWho completed itTime, on a scale from 0 to 80 sObservation
1. Open the jigsaw puzzle5 of 5 users100%4 s average, 4 s medianEveryone figured out how to move forward.
2. Sign up, without Google or Apple3 of 5 users60%63 s average, 71 s median4 out of 5 filled in the login fields thinking they were the sign-up ones; 2 couldn’t move forward without help.
3. Finish signing up5 of 5 users100%78 s average, 73 s medianEveryone figured out how to move forward.
4. Play4 of 5 users80%6 s average, 6 s median1 user went back to the start expecting to confirm the email. It couldn’t be fully validated because email delivery wasn’t built yet.

AI report

From the Excel data we generated an automatic report with AI, deployed as an app.

Iterations

We ranked the problems by frequency, how many of the 5 users ran into it, and by severity, whether it blocked the task or was a minor issue. Each one ended in a change.

The main screen now has a single email input. If the email already has an account, we welcome the user back and ask for the password; if not, it moves on to the sign-up flow.

Priority1
SeverityBlocks the task: 2 couldn’t move forward without help

Launch

The flow launched with these five iterations built in. The design you see in this project is the one in production.

Start
Start screen on mobile: an email field, and Google and Apple sign-in with the “Último usado” (last used) badge
Create account, step 1
Create account screen, step 1, on mobile: a three-step stepper, email and password with its four requirements validated as you type
Step 2
Create account screen, step 2, on mobile: first and last name, with the first step completed in the stepper
Confirm account
Confirm account screen on mobile: asks you to check the email that was sent to confirm the account
Sign-up complete
Sign-up complete screen on mobile

The full sign-up on mobile, from the email to the confirmed account.

End of the projectBack to top
Next project

Weather
service

TN’s weather redesigned from the data and a card sorting, built for people arriving from Google and on their phones.

View project
Open project: Weather service

Let’s talk

If you have a product to think through, design or build, write to me.