Background
In September 2024 the team participated in a Sprinthackular which was designed to create proof of concept for product ideas and get feedback from real users about the feasibility of the concept. The Android team created a proof of concept for a Trivia game. The usability testing insights were positive enough for us to build out the game and offer it in the app permanently in March 2025 and release to German Wikipedia, then all available languages.
After positive reception of the production “Which came first” game on Android (T393055) by both community members, and the press, we feel confident in bringing this game to iOS Users and continuing to improve it.
The Annual Plan has includes an objective to increase retention of logged-out users, and we believe games could be an engaging way to retain readers and knowledge lovers.
Hypothesis
If we test the addition of the “Which came first” daily-play trivia game to the iOS App, we’ll see 15% of engaged logged-out readers return to play the game on multiple days.
How will we know we were successful
Key Results
- KR 1.1 - 8% higher overall app retention among readers who completed the game, compared with those who saw the invitation and did not play
- KR 1.2 - 70% Completion rate (% of those who enter the game, complete the game)
- Baseline: 78% from Android
- KR 1.3 - 15% of engaged users return to play the game on a subsequent day
- Baseline: 23%, but Android had push notifications
- KR 1.4 - Comparable overall app retention for active readers with access to the game compared to active readers who did not have access
Guardrails
- GR 2.1 - At least 50% of active app users click on one of the game entry points (Announcement, Profile, Explore)
- Baseline: 11.7% from just announcement, projected need: 60%
Curiosities
- CR 3.1 - What % of games users interact with articles by sharing, reading or saving directly from the game?
- Baseline: 10%
- CR 3.2: Which Games entry point drove the most users to discover the game? (Profile, Announcement, Explore)
- CR 3.3 - How did average pageviews per user vary for control group, variant group, and those who engaged with the game within the variant group?
- CR 3.4 - What % of uniques shared their results? How many app installs did we see as a result of game
- Baseline: 169 installs
- CR 3.5 - How many total accounts were created through the game? What % of logged-out users who completed the game created an account?
User stories & Requirements
- Which came first gameplay: As a Wikipedia reader, I want to be able to play a daily game about events in history, so that I can pass time and have fun while learning.
- 5 questions based on “On this day” that update every day, for the available languages
- Allow users to exit and pause the game
- User must be able to read entire text within card (scroll or expand)
- Users can pause game and return, with their progress saved
- Show snackbar after game is complete for where games can be accessed
- Results splash screen: As someone who has just finished playing the game, I want to be able to see my results and all of the articles mentioned in the game, so that I can share my results and explore articles mentioned in today’s game.
- Ability to share results with image & Custom URL to download the app
- Game stats (streak, games played, average score)
- Logged-out users: Invitation to log in / create an account for Game stats
- All articles mentioned in the game with ability to Read, Save, or Share
- Archive: As someone who enjoys playing “Which came first”, I want to be able to play previous day's games through the archive, so that I can play days that I’ve missed.
- Games from subsequent days after release can be started, paused, and resumed from Archive
- Entry points to archive: in results screen, splash screen, Games hub
- Show completed games in the calendar view
- Games hub: As a games hub user, I want to have access to everything related to games in one place, including access to my stats, the ability to share feedback, and learn more about games secondary actions about the Games.
- Cards update based on gameplay state (Not started, paused, complete)
- Should support future addition of other games
- Allows playing the game in any supported app languages they have
- Overflow Menu with
- A way to report problems with the game
- Learn more about the game (leads to MediaWiki page)
- Profile access: As a user of the app, I want permanent access to the games hub in Profile, so I can quickly find Games and play them daily
- Explore feed: As a new user of the app, I want to discover that there are Wikipedia games while using the explore feed.
- Explore feed card updates based on gameplay state (Not started, paused, complete)
- Games announcement: As a new user of the app, I want to discover that there are Wikipedia games while reading articles, or using the explore feed.
- New feature announcement on Article view or Explore
- Survey: As a product manager, I want to be able to hear feedback from users about the “Which came first” game so that I can understand their satisfaction level, and incorporate their thoughts into future iterations.
- Games stats in Activity: As a user of the Activity tab, I want to see Games-related activity within the Activity tab so I can see my stats and streaks in one place.
- Clicking on Stats leads to the Games hub
Out of scope
- Daily local push notification
- Sound effects
Target Quant Regions and Languages
Languages where there are consistently 10+ on this day events on the main page, maintained by the community
- DE
- EN
- FR
- PT
- RU
- ES
- AR
- ZH
- TR
Target Qualitative Audience
- Logged-in and Logged-out readers
- Users of assistive technologies like Dynamic Type and VoiceOver
- Users of the app on iPad, and in landscape mode
Quality Assurance
| Testing | Owner | Cadence |
| Exploratory | QS | Per Release Candidate |
| Per Ticket (Feature) | Engineering | During development |
| *Smoke Testing | QS | Per release candidate |
| *Upgrade Testing | QS | Per release candidate |
| Analytics Validation | Data Analytics | When Analytics is completed |
| Internal Testing | QS | When MVP is completed |
| * automation candidate | ||
| Environment | |
| Test | Conditions |
| Performance | Test against devices that are older, smaller, on a poor-performance network, with full memory (w/ simulators) |
| Languages | Device language settings: LTR, RTL, Compounding (long words), Latin, Cyrillic, Brahmic, Logographic, Numbers, Special characters |
| Account required? | Accounts/logins: New account, Regular, 2FA, Hcaptcha, Email Code, Other |
| Accessibility | Accessibility Settings: Voice control, System text size, System contrast, Hearing enhancements, Motion |
| Error states | Network offline, feature offline, crashes |
| Test overview | |
| Onboarding | New and existing installs onboarding and explore feed card |
| Games hub | Game play, questions 1-3 |
| Results | Results, learn more, rankings, streaks, share |
| Game info | Leaderboard, your gameplay, how the game works, scoring description |
| Game settings | Card toggle |
| Unhappy path | Offline, error states, modules off, unexpected user behavior, test while downloading saved articles |
Designs
References
Android Epic: T371504
Timeline
- Release 15-day experiment around May 20
- Scale to all users by June 2