AC
- Language switcher link is available in sticky footer at the bottom of the viewport
- The sticky footer is shown to 50% of mobile web beta users
- We have metrics in place for measuring
- No tracking changes from now to the B version
- Before pushing to stable we should have a estimate of impact on clicks and thus impact on API traffic and whether this would lead us to needing to ship languages via JavaScript config variables rather than API requests.
TBD
- Design (by @Nirzar) moves also the watchstar. Should it be done as part of the beta test?
- If so, we should track (without changes to the metrics) the watchstar and its impact.
Implementation plan (proposal)
From T123342#1928084
First, in parallel
T123382: Spike: How do people currently use the language switcher?
T119658: [Design] Language button on footer
T122521: Update MobileWebUIClickTracking to include talk, edit, watch, etc.
Next, implementation in parallel, rollout may not be
T123384: Changes to language overlay design
T97377: Create a sticky footer with access to language switcher