Skip to content
Interface language: English
Design / Signal

A passkey instead of a password: design for the day after the phone is lost too

Design passkey enrolment, management and account recovery around real supported methods.

Article language: English

Aeneia world concept: a designer tests movable wall modules and benches on open terraces overlooking the water.
In this article

On Monday, signing in took a moment. On Wednesday, the phone was left on a train. The portal still offers “Sign in with a passkey”, as though it had not noticed a small change in the passenger's equipment. The promise of convenience is now being tested under much harder conditions than a demonstration of a new button.

A passkey is a sign-in method that uses cryptographic mechanisms instead of entering a password into a service. For a user, practical questions can matter more than the protocol's name: where is the method available, how can it be recognised and what happens if it stops working? The design should cover its whole period of use.

Imagine a fictional printing company's partner portal. Marta returns to orders, downloads approved designs and adds comments for a new print run. The company wants to make sign-in easier, but cannot let a stranger take over an account after a brief conversation with support. A convenient screen and rules for confirming access must be designed together, although different parts of the team are responsible for them.

A passkey need not mean one phone

The FIDO Alliance distinguishes synced passkeys from those bound to a particular device. A passkey provider may make them available on other compatible devices; not every key has the same method of transfer.

This distinction affects labels visible in the portal. “Marta's phone” may mislead if the method is available through a manager that also syncs passkeys to her computer. Conversely, a generic “Passkey” will not distinguish several methods. A name should help the user recognise what they actually possess, without guessing from one piece of device information.

Do not promise “you can sign in from any phone”. State the supported option and what it requires from the user. Marta may use a different passkey provider from her teammate. Changing phones may mean restoring access through the same provider or needing another method prepared earlier. There is no single universal instruction for replacing a device.

Show the benefit beside the action it fits: “Add a passkey to sign in without entering a password”. Further explanation must match the solution in use. If the system cannot reliably identify a provider or synchronisation, the screen should not invent that certainty. A designer can prepare a clear variant for unknown information.

Adding a method must end in a recognisable result

Marta is already signed in to the printing portal and opens access settings. Before the device window appears, she should know which account will receive the method. The company name and address used in the portal help prevent confusion, especially when she handles several brands. A generic “Secure your account” heading displayed identically in every workspace is not enough.

She then starts creating a passkey. The page should prepare her for the system flow without recreating it as a misleading imitation of its own. After she returns, confirmation must correspond to the method actually being registered. Closing the window alone does not establish whether Marta cancelled, succeeded or encountered a problem.

If she cancels, she need not lose her previous portal access. Briefly say the new method was not added and leave settings in their previous state. An error should let her retry the appropriate action or use another supported route. Do not immediately ask her to create a second account for the same orders.

After addition, show the method somewhere she can return to later. Marta should not have to remember whether management was hidden on a welcome page, in a promotion window or in a post-login message. Access settings need a stable, recognisable path from the account. First use of a tool (in Polish) may explain the feature, but does not replace later management.

Adding a passkey should not accidentally change the purchase model either. If a shop offers checkout without an account (in Polish), a new sign-in method is not a reason to suddenly require registration at checkout. First establish which account and task the proposed convenience concerns. In our portal, the partner already has an account with a history of designs.

In messages, distinguish the printer's account from the passkey provider's account. The address used in the manager need not be the name under which Marta works in the portal. When creating the method and later signing in, show the appropriate printing-portal account identifier. If the system selects another available identity, she should see that choice before entering orders. A familiar provider alone does not explain which company profile a method opens.

The method list should help with the decision to remove one

Prepare a list where methods can be distinguished. A recognisable name, available provider information and dates may help Marta select the right entry. Do not show a guessed sign-in location as the person's certain address. The information set should follow system data and the decision's needs, not a desire to fill a table row.

The web.dev guide to passkey management describes a method list, adding more methods and warning before removal of the last useful sign-in route. It also distinguishes deletion of a server record from a copy held by the provider.

At the printing company Marta sees two methods and wants to remove an old one. Confirmation should identify the particular entry and effect on her next sign-in. “Are you sure?” without a name forces her to remember which button she selected. If renaming is possible, ensure later messages use the same current label.

When it is the last method, the message must say how Marta will sign in next time. “Last” alone is too vague: the last passkey need not be the last access method if another working route exists. Conversely, a visible email field does not prove the portal offers email sign-in. The design must refer to that account's actual configuration.

Aeneia conceptual photography

You can propose adding another method before removal if the product supports it. Do not treat every existing entry as sufficient continuity protection. Marta may no longer have the second device or access to the provider account. Recognising an entry on a list and actually being able to use the method are different pieces of information.

Web.dev also describes a record removed from the server but still offered by the provider. Signing in with that key will fail. Reconciliation between the lists depends on supported mechanisms; disappearance of a portal row does not confirm every copy was deleted.

Marta then needs instructions for that particular method. She should not have to recover the whole account merely because she sees a stale suggestion in a sign-in window. During acceptance, also record what happens to existing sessions after removal. If the product is supposed to end access on other devices, that needs its own decision and test. Removing a method and ending previously opened work should not share one unclear label.

The phone is gone. What else is available?

On Wednesday Marta opens the portal on her computer. If she has a working method there, losing the phone need not mean losing the whole account. She should recognise an available route and then organise her settings. Before directing her to recovery, distinguish loss of one method from loss of all available sign-in methods.

If a passkey can return through its provider, instructions must refer to that provider and the right account. The printing portal should not pretend to manage the account of the service storing keys. Its own help can explain the boundary and lead to the relevant official instructions. It must not collect data in a company form that the printer does not need for its procedure.

The harder case begins when Marta has no working method. A real account-recovery process is then needed, under conditions set by those responsible for security. The design should not invent that a new email address or last order number suffices. A simple instruction does not prove that the procedure recognises the owner with sufficient confidence.

NIST's section on authenticator events distinguishes account recovery from ordinary sign-in and describes how a procedure can be less convenient and involve waiting. It is a technical reference, not an automatic obligation on every portal.

In our design the customer should learn which supported route they are starting, its present stage and where to receive further information. If the company does not confirm a completion time, do not promise “access in five minutes”. When support must act, show the right contact and the material to prepare. Do not encourage people to send an arbitrary collection of documents to a general inbox.

If a recovery request has already been accepted, show how to find its status. Returning to help should not look as though the user must start again. In the fictional portal a case number and agreed contact channel can be shown. Include reopening the instructions before support replies in the trial. Marta should recognise whether she is waiting on the same case and whether the company needs another action from her.

Recovery must also connect its result to the correct account. Marta wants to return to her order history, not receive a new empty profile with a similar name. When the procedure ends, the interface should let her recognise where she has arrived. Details of granting access and invalidating previous methods require separate technical acceptance; the word “Recovered” does not confirm them.

A signed-in tab does not prove the new method works

This problem is easy to miss during acceptance. A designer adds a passkey, still sees the portal and considers the trial complete. The open tab, however, uses an earlier session. Test the new method by entering again in a flow that actually requires sign-in. Use a prepared test account with an agreed route back.

Do not begin experiments by removing the only method on an account with real orders. Test material allows safe comparison of states: cancelling addition, saving, returning to sign-in and removing a chosen entry. For each case record the expected result before the trial. Do not treat a row in the list as a test of the whole access path.

Separately test session expiry while working (in Polish). Marta may have a comment on a design open when the portal requests access confirmation. Successful sign-in should restore the right destination without creating a second comment. Passkey management and preservation of work in progress meet at this point.

Settings do not end on this device

A shared terminal (in Polish) presents another boundary. A user should not accidentally configure long-term access to their own account on a device belonging to a service location. If the product supports this context, the design must account for it in prompts and at the end of the visit. A phone icon drawn beside the button does not solve the problem.

Likewise, installing a web application (in Polish) does not automatically register a new sign-in method. After opening from an icon, the account and available flow still need to be recognised. Do not combine installation confirmation with a message that the passkey is ready unless the system confirmed both events separately.

Before handover, gather support's questions. What will it tell someone with a new phone? How will it direct a person who has another working method? How will it distinguish a request to remove an old entry from a report of losing every access method? Answers should agree with the screens rather than being invented during the first difficult conversation.

At Aeneia Design, the design of this path, its messages and acceptance cases can be discussed within an agreed scope. The authentication team defines supported mechanisms and recovery rules and is responsible for their technical implementation. The design aims to help Marta understand the instructions while her phone is still travelling by train and the portal needs to recognise her right to work with orders.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear