Background
Over the years it seems that other teams/community have chipped away at the feature and enabled AMC features for all logged in users.
Doing a quick audit enabling AMC mode in 2026 does three things:
- Disables a simplified view for watchlist, contributions and history page exposing power editor features
- Adds recent changes, special pages and community portal to the left (main/hamburger) menu
- Adds user talk, sandbox and watchlist to the user personal menu
In addition to this, next fiscal year we are looking to improve performance for logged in users by adding additional caching. Non-default preferences are likely to continue to be uncached so it will be important to consider this as part of that initiative.
Given the above I think we should remove the AMC in some form mode (see proposals)
User story
As a user I should not need to enable an advanced mobile mode to access features.
Requirements
- Add task requirements. Requirements should be user-centric, well-defined, unambiguous, implementable, testable, consistent, and comprehensive
BDD
- For QA engineer to fill out
Test Steps
- For QA engineer to fill out
Design
- Add mockups and design requirements
Options to consider
(Note no decision has been made about which to pursue. Other options welcome in the comments)
Option 1) Unlock features based on user activity
Instead of the existing AMC mode I suggest we enable features based on user behaviour. The logic for these decisions would also apply to desktop editors.
- We expose the recent changes page once a user gets the rollback permission
- We expose the user talk page if a user has a non-empty talk page.
- We expose the sandbox page once a user has an edit count greater than 10 (TBC)
- We expose community portal based on edit count
- We expose special pages based on user rights (TBC)
- We expose the watchlist page once an editor has a certain edit count, user right OR has used features in the watchlist (eg. created labels or watched articles)
- We disable simplified view of watchlist, contributions and history page when a user gets the rollbacker or new page reviewer user right
Once the above is done, we drop AMC and associated code.
Note: would hurt discoverability and learnability as different users would have different experiences.
Option 2) Remove simplified features and show links to all
- We remove the simplified view for watchlist, contributions and history page exposing power editor features to all logged in users
- We add recent changes, special pages and community portal to the left (main/hamburger) menu for all logged in users
- We adds user talk, sandbox and watchlist to the user personal menu for all logged in users
Note: this may confuse readers who do not understand these features.
Option 3) Replace with individual preferences
Replace AMC with individual preferences: currently it's not clear what clicking AMC does.
- We add an explicit preference for the simplified views for watchlist, contributions and history page. These could be exposed on the page themselves e.g. "Enable advanced view" so it's clearer what they do.
- We add a preference "Enable advanced menus" for expanding menus
Note: this would mean users who use these preferences would not benefit from future caching benefits for logged in users (which is likely to favor whatever defaults we land on)
Option 4)
- We drop the simplified views and links to watchlist, recent changes and contributions and point to PersonalDashboard
- We move user talk, community portal, sandbox are moved to an extra menu
Acceptance criteria
- Add acceptance criteria
Communication criteria - does this need an announcement or discussion?
- Add communication criteria
Rollback plan
- What is the rollback plan in production for this task if something goes wrong?
This task was created by Version 1.2.0 of the Web team task template using phabulous