Introduce a feature in the account creation flow that suggests and allows users to select from auto-generated, available usernames. This aims to reduce friction during username entry, particularly on mobile, and improve account creation completion rates.
User story
As a mobile web user creating a Wikipedia account, I want the username field to be pre-filled with a generated username and to receive a clickable suggestion if my chosen username is taken, so that I can complete account creation with less friction.
Background & research:
This task is part of an ongoing effort to reduce friction in the account creation funnel on mobile web. More details in T424451.
Experiment plan:
We should test this in a simple way on enwiki as a first step.
If this is successful, then we can decide if and how we localize and scale a feature like this.
Design:
Scope: this task is scoped to mobile web only.
→ Figma specs
→ Prototype
→ usernameData.js
| Prefilled username | Username taken state |
|---|---|
Acceptance Criteria:
Prefill on page load
AC1
- Given I am on the account creation form on mobile web
- When the page loads
- Then the username field is pre-filled with an auto-generated available username
AC2
- Given the username field is pre-filled with a generated username
- When I view the field
- Then I see a cdxIconReload icon displayed as an endIcon inside the username field
AC3
- Given the username field is pre-filled with a generated username
- When I tap the reload icon
- Then the field is replaced with a newly generated available username
Username taken state
AC4
- Given I have typed or edited a username in the field
- When the field is validated and the username is already taken
- Then a warning message appears below the field using the Codex warning state
- AND the warning reads: "Username taken. Try: [suggested username]"
- AND the suggested username is displayed in color-success and text-decoration-underline
AC5
- Given the username taken warning is displayed
- When I tap the suggested username
- Then the username field is populated with the suggested username
Instrumentation is in place to measure
- Whether the user submits the form with the originally generated username unchanged (eg. accepted without editing)
- Refresh icon clicks (how often users request a new generated username)
Open questions:
- How should we calculate the alternative username suggestion shown in the taken state? In the current prototype, 4 random digits are appended to the username the person originally typed. Is this the right approach, or is there a better method we should use?
- Do we need a legal review of usernameData.js?

