The last method used
Lovable shows a badge that tells you which sign-in method you used last.
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.
Try it with any email. facu@email.com already has an account. It’s a replica: it doesn’t store or send anything.
We set out to improve our users’ experience when signing in or creating an account.
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.
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.
Lovable shows a badge that tells you which sign-in method you used last.
A national news outlet uses a stepper to show which step of the sign-up the user is on.
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.
With the problem, the goals and the analysis clear, we redesigned the user flow. That let us see every possible scenario clearly.
With the flows defined, we moved on to the visual design of each screen: sign in, create account and change password.
The real interface, rebuilt from the design file. Mobile, at 360 px.
The stepper and the input, built as reusable components with all their states. They’re live: you can try them.
Shows sign-up progress. The active step is blue, and each completed step turns green along with its line.
Validates the four requirements as you type and warns you if Caps Lock is on. Type a password to see it.
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.
Explicit, accessible error states, with no generic messages. Every input has its label, iconography and a text that explains exactly what is going on.
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.
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 heroWe tested the prototype with users before developing a single screen.
5users, in person
92%of our users are on mobile
From the Excel data we generated an automatic report with AI, deployed as an app.
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.
The flow launched with these five iterations built in. The design you see in this project is the one in production.
The full sign-up on mobile, from the email to the confirmed account.