Page MenuHomePhabricator

[V2 experiment release] Mobile web account creation form improvements + username TL;DR
Closed, ResolvedPublic3 Estimated Story Points

Description

User story & summary:

As a mobile web user, I want a cleaner and less verbose account creation form so that I can view all required fields at a glance without scrolling, and complete registration with reduced information overload.

  • As a mobile web user, I want simple and clear guidance when creating a username, because then I am more likely to respect the username policy.
Summary

We are making further improvements and simplifications to the mobile web account creation form, and will A/B test the impact before releasing further.

Included changes:

Not included:

Design:

Arc 2026-04-03 15.32.44 (1).png (2,206×1,450 px, 477 KB)

image (26).png (1,410×1,806 px, 390 KB)

Prototype: https://monorepo-account-creation.vercel.app/
Figma Designs: Account Creation designs

Experiment Details:
  • WE1.8.3 Measurement Plan
  • Existing baselines:
  • Exposure prediction:
  • Duration of experiment
    • start date: Turn On: TBD May 19th , effective: May 20th at 14:30 UTC
    • end date: July 30, 2026
  • Machine readable name: we-1-8-account-creation-form-v2
  • stream/schema: event.mediawiki_product_metrics_contributors_experiments
  • Link to test-kitchen dashboard experiment config:
  • Wikis / groups: auth.wikimedia.org/enwiki
  • Automated analysis metrics, including link to metric catalog, instrumentation source:
  • Manual analysis metrics: none
  • Link to the aftermath task:
Metrics tracked for this experiment:
MetricInstrument source
Experiment exposuresexperiment_exposure
Account Creation attempts (= all Special:CreateAccount submissions)'creation_attempt'
Fraction of Special:CreateAccount submissions with email'creation_attempt_with_email'
Unsuccessful account creation attempts (= Page visits with error present)'page_visit_with_error'
Special:CreateAccount Create-Account-button clickthrough'create account button'
Special:CreateAccount user policy link clickthrough'username policy link'
CTRs for the links in the username policy TL:DR;CTR instruments in UsernamePolicyPopover.vue
Account creation rategeneric account creation instrument
Acceptance Criteria:
  • Implement additional instruments in WikimediaEvents as needed
  • adjust Statslib / Prometheus based metrics as need (see respective V1 change)
  • Set up A/B test on Test Kitchen
  • Release experiment on start date listed above (or communicate if a shift in release is necessary)
  • Adjust Growthbook analysis setup as needed

Related Objects

Event Timeline

KStoller-WMF triaged this task as High priority.
KStoller-WMF added a project: Growth-Team.
KStoller-WMF moved this task from Inbox to Needs Estimation on the Growth-Team board.
Urbanecm_WMF subscribed.

This task is blocked on completing the improvements linked. The metrics section is also out of date (from a different task); we should update it (@Michael is working on that). It is also unclear whether the metrics would be implemented in a different (to-be-created) task, or here (this would affect estimation as well).

KStoller-WMF set the point value for this task to 3.Apr 20 2026, 3:40 PM

Change #1286930 had a related patch set uploaded (by Michael Große; author: Michael Große):

[mediawiki/extensions/WikimediaEvents@master] Support NCS-experiments for Account Creation

https://gerrit.wikimedia.org/r/1286930

Change #1289344 had a related patch set uploaded (by Michael Große; author: Michael Große):

[mediawiki/extensions/GrowthExperiments@master] feat(V2): support both url-param based and cookie based enrollment

https://gerrit.wikimedia.org/r/1289344

Change #1289344 abandoned by Michael Große:

[mediawiki/extensions/GrowthExperiments@master] feat(V2): support both url-param based and cookie based enrollment

Reason:

The changes from this patch should be squashed into the parent Id1c5f16bbe8b43f6cd2bc6ba275cad9dbe9cc599 as needed.

https://gerrit.wikimedia.org/r/1289344

Change #1300210 had a related patch set uploaded (by Michael Große; author: Michael Große):

[mediawiki/extensions/WikimediaEvents@master] fix: correct intake-url and payload type for NCS experiment events

https://gerrit.wikimedia.org/r/1300210

Change #1300210 merged by jenkins-bot:

[mediawiki/extensions/WikimediaEvents@master] fix: correct intake-url and payload type for NCS experiment events

https://gerrit.wikimedia.org/r/1300210

Change #1300736 had a related patch set uploaded (by Michael Große; author: Michael Große):

[mediawiki/extensions/WikimediaEvents@wmf/1.47.0-wmf.6] fix: correct intake-url and payload type for NCS experiment events

https://gerrit.wikimedia.org/r/1300736

Change #1300736 merged by jenkins-bot:

[mediawiki/extensions/WikimediaEvents@wmf/1.47.0-wmf.6] fix: correct intake-url and payload type for NCS experiment events

https://gerrit.wikimedia.org/r/1300736

Mentioned in SAL (#wikimedia-operations) [2026-06-11T13:16:03Z] <lucaswerkmeister-wmde@deploy1003> Started scap sync-world: Backport for [[gerrit:1300736|fix: correct intake-url and payload type for NCS experiment events (T422295)]]

Mentioned in SAL (#wikimedia-operations) [2026-06-11T13:18:09Z] <lucaswerkmeister-wmde@deploy1003> lucaswerkmeister-wmde, migr: Backport for [[gerrit:1300736|fix: correct intake-url and payload type for NCS experiment events (T422295)]] synced to the testservers (see https://wikitech.wikimedia.org/wiki/Mwdebug). Changes can now be verified there.

Mentioned in SAL (#wikimedia-operations) [2026-06-11T13:22:55Z] <lucaswerkmeister-wmde@deploy1003> Finished scap sync-world: Backport for [[gerrit:1300736|fix: correct intake-url and payload type for NCS experiment events (T422295)]] (duration: 06m 51s)

The experiment has now started! This is the link to investigate the treatment experience without affecting the data: https://en.wikipedia.org/w/index.php?title=Main_Page&mpo=we-1-8-account-creation-form-v2:treatment&mobileaction=toggle_view_mobile

DMburugu added a subscriber: Etonkovidova.

Had a chat with @Etonkovidova around QS support on this and she suggested that this is good to close. Any issues will be filled as separate tickets.