**Must Haves**
[x] Basic entry point into the Year in review from user menu
[x] Two non-personalised card that can the user can interact with.
[x] One personalised card using data from the users device.
[x] One personalised card using data from an API call.
[] Basic instrumentation on at least one interaction.
**Nice to haves**
[] Share flow
[] Year in Review entry modal
[] Survey
[x] Donation entry point
[] More personalised cards
[] Make available in developer settings.
**Mid point task checkin before making available in dev settings**
Tasks to complete before
[] Move the modal to trigger on app load/first article read. Check in with iOS.
[] Update the more menu entry point to open YiR onboarding.
[] Where does the learn more button point to
[] Where does the information icon point to.
[] Finalise share functionality
[x] Hook up donation flow.
[] Have the survey trigger on last slide
**Designs**
- https://www.figma.com/design/9lqLxtOqqcQxSSg73ScUrH/Android-YiR?node-id=0-1&p=f&t=BCiw4lqzTLhX6FVd-0
**User Stories**
Primarily
- As a Wikipedia reader, I want to be visually struck and leave the experience remembering how cool and useful Wikipedia is —inspired and in awe at the breadth and depth of human knowledge that can happen over the course of a year, and ready to give back with a donation.
- As a Wikipedia reader, I want to see a breakdown of my reading habits in the App, so I share with my quirky Wikipedia reading habits with friends on social media.
Secondarily
- As an editor on Wikipedia, I want to see insights about my editing contributions to Wikipedia, so I can understand my overall impact this year and share with friends.
**Phase 1 Engineering work**
1. Add Year in Review text and icon to the More menu of the Explore Feed
2. Build compose NavHost and screen 1 displaying "Hello World"
3. Create clickable navigation from Year in Review icon to screen 1
4. Build screen 1 template (following Figma design yir #53), add hardcoded data (e.g. image, headline, textbox)
5. Duplicate screen 1 template for 2 personalized screens, add navigation and hardcode data.
6. Add page indicator to the BottomAppBarr.
7. Add functionality to navigate back to MainActivity/MainFragment.
**Phase 2 Engineering work**
1. Build BottomSheet for the explore screen and integrate it into the navigation path.
2. Create a viewModel and transfer all state variables to the viewModel.
3. Build an API call for editCount screen integrate it into the execution path.
4. Leverage HistoryEntry DB call(s) to gather readCount screen data and integrate it into the execution path.
5. Add a tracking interaction.
**Phase 3 Engineering work**
1. Implement right to left testing.
2. Add more screens (personalized and non-personalized)
3. Create a survey and integrate it into the YiR flow.
4. Add share flow