Background
Following the success of our desktop test, it's now time for us to do the same on mobile! Since the desktop proof of concept was celebrated as something that made subsequent work easier, and as there are a couple of differences between the mobile version of this experiment and the desktop one, let's make another proof of concept to ensure that we understand the engineering work entailed in this experiment!
User story
As an engineer on the Reader Experience team, I want to feel as prepared as possible to begin development on the mobile version of the donate A/B test
Requirements
As much of the infrastructure of doing an experiment like this has been proven out, I'd like us to focus our efforts on making sure to answer the open questions:
- How can we localize the currency to the user's geographic region? Fundraising tech pointed us to this banner code which we should be able to copy the approach of: https://wikimedia.slack.com/archives/C045WH0QYS2/p1753980480035079?thread_ts=1753976695.104009&cid=C045WH0QYS2
- Is the clickthrough rate instrument correctly measuring impressions for the mini banner, which is hidden behind a tap of the menu icon?
all other features should be regarded as optional and dealer's choice
BDD
- For QA engineer to fill out
Test Steps
- For QA engineer to fill out
Design
Acceptance criteria
- a proof of concept patch has been created in gerrit, which answers the above questions
- code need not be perfect or finalized (don't worry about variable/function names for now), but it should work end-to-end to demonstrate how an engineer could set up this mobile experiment without additional unforeseen challenges
Communication criteria - does this need an announcement or discussion?
None required beyond sprint updates
Rollback plan
The proof of concept should not be merged nor mergeable, so no worries about rollback plan here