Background
The apps team plans to learn from the Web team's year in review implementation, and create an App-specific version on iOS during Q2. Because our goal is to release in early Q3 (January 2025), we need to think early-on about what kinds of data will be available to use, and if we need to request anything in advance, or prompt users to opt-in to anything in advance. It would be useful to have a "data inventory" of sorts that the Designer and PM can start from during the exploration phase.
Tasks
- TS: Meet with Web team to understand under-the-hood of Year in Review & https://wikipediayir.netlify.app/, and find out if it would be available to for use through an API
- HN: Create starting point list data currently being used in prototypes, and brainstorm what may be useful to use for a year in review
- Reading data
- Editing data
- Donation data
- HN, TS, SN Review list and identify what is possible without an API, what is possible with clientside changes
- Identify any additional instrumentation that could be added locally into the app to unlock more possibilities
References
- Notes from Hackathon: https://etherpad.wikimedia.org/p/wmh2024-Wikimedia_Hackathon_2024_Closing
- Phabricator task for improvements: T362898: Improve the year in review tool for next year
- Old Link: https://wikipediayir.netlify.app/
- New Tool: https://yearinreview.toolforge.org/
- Repo Link: https://gitlab.wikimedia.org/toolforge-repos/yearinreview.git
- Phabricator task for improvements: T362898: Improve the year in review tool for next year