Change Details

Can pick up after {T375566} is complete ####Background The Apps team plans to explore if a personalized Wikipedia in Review feature that displays insights about a user's reading history, editing history, and donation history is engaging for App users, and inspires them to make a donation to the Wikimedia Foundation. ###Requirements - Flow should launch from Profile item "Year in Review" - Only users who are eligible for more than 1 personalized slide should see the entry point - Ensure Next goes to the next component. - Dismiss flow when Done is tapped - Present all slides from collective flow in [[ https://www.figma.com/design/JRTyGA3rZ0qlQ9eqh0FMhE/Wikipedia-YiR?node-id=147-12038&t=o1VMtqNHkSIpgzk8-4 | Figma ]] - Use **variables** for source text of translations, so that statistics can be updated shortly before launch ###Engineering Notes - Present paging components when tapping Profile item using a WikiwrappedCoordinator / WiRCoordinator - Before presentation, create a paging component view model item for each slide that should be displayed, in the proper order: - Reference personalized slide "report" model created in T376041, and create associated view model if evaluated = yes and display = yes - If any "fallback" collective slides are needed (i.e. no valid personalized slide exists with evaluated = yes and display = yes), create collective slide view models here. There will be no underlying model data to reference here like with personalized slides - we will just create the copy as literal strings here. Note copy for collective slides may be in-flux until we get final numbers from Comms. - At this point the correct sorting of slides will be determined, depending on our ordering of the slide view models. - Note in the future, if we need further flexibility on slide presentation (A/B testing against different sets of slides, different collective slide copy for EN Wiki), this logic will live here when we create the final slide view models.

Can pick up after {T375566} is complete ####Background The Apps team plans to explore if a personalized Wikipedia in Review feature that displays insights about a user's reading history, editing history, and donation history is engaging for App users, and inspires them to make a donation to the Wikimedia Foundation. ###Requirements - Flow should launch from Profile item "Year in Review" - Only users who are eligible for more than 1 personalized slide should see the entry point (Note: this logic will be handled in T376042) - Ensure Next goes to the next component. - Dismiss flow when Done is tapped - Present all slides from collective flow in [[ https://www.figma.com/design/JRTyGA3rZ0qlQ9eqh0FMhE/Wikipedia-YiR?node-id=147-12038&t=o1VMtqNHkSIpgzk8-4 | Figma ]] - Use **variables** for source text of translations, so that statistics can be updated shortly before launch ###Engineering Notes - Present paging components when tapping Profile item using a WikiwrappedCoordinator / WiRCoordinator - Before presentation, create a paging component view model item for each slide that should be displayed, in the proper order: - Reference personalized slide "report" model created in T376041, and create associated view model if evaluated = yes and display = yes - If any "fallback" collective slides are needed (i.e. no valid personalized slide exists with evaluated = yes and display = yes), create collective slide view models here. There will be no underlying model data to reference here like with personalized slides - we will just create the copy as literal localized strings here. Use plural formatting when numbers are in the copy (see "Plural syntax" in our [[ https://github.com/wikimedia/wikipedia-ios/blob/main/docs/localization.md | localization document ]]). Note that copy for collective slides may be in flux until we get final numbers from Comms. - At this point the correct sorting of slides will be determined, depending on our ordering of the slide view models. - Note in the future, if we need further flexibility on slide presentation (A/B testing against different sets of slides, different collective slide copy for EN Wiki), this logic will live here when we create the final slide view models.

Can pick up after {T375566} is complete ####Background The Apps team plans to explore if a personalized Wikipedia in Review feature that displays insights about a user's reading history, editing history, and donation history is engaging for App users, and inspires them to make a donation to the Wikimedia Foundation. ###Requirements - Flow should launch from Profile item "Year in Review" - Only users who are eligible for more than 1 personalized slide should see the entry point (Note: this logic will be handled in T376042) - Ensure Next goes to the next component. - Dismiss flow when Done is tapped - Present all slides from collective flow in [[ https://www.figma.com/design/JRTyGA3rZ0qlQ9eqh0FMhE/Wikipedia-YiR?node-id=147-12038&t=o1VMtqNHkSIpgzk8-4 | Figma ]] - Use **variables** for source text of translations, so that statistics can be updated shortly before launch ###Engineering Notes - Present paging components when tapping Profile item using a WikiwrappedCoordinator / WiRCoordinator - Before presentation, create a paging component view model item for each slide that should be displayed, in the proper order: - Reference personalized slide "report" model created in T376041, and create associated view model if evaluated = yes and display = yes - If any "fallback" collective slides are needed (i.e. no valid personalized slide exists with evaluated = yes and display = yes), create collective slide view models here. There will be no underlying model data to reference here like with personalized slides - we will just create the copy as literal strings herelocalized strings here. Use plural formatting when numbers are in the copy (see "Plural syntax" in our [[ https://github.com/wikimedia/wikipedia-ios/blob/main/docs/localization.md | localization document ]]). Note that copy for collective slides may be in-in flux until we get final numbers from Comms. - At this point the correct sorting of slides will be determined, depending on our ordering of the slide view models. - Note in the future, if we need further flexibility on slide presentation (A/B testing against different sets of slides, different collective slide copy for EN Wiki), this logic will live here when we create the final slide view models.