Change Details

**Background** The Android team is setting the strategic direction of the Android app. This will be done in the following steps: Design Q4 Brief **Team OKR ** Objective 2: Objective: Conduct and share a gap analysis of our app’s architecture and our team roadmap to get buy in from Product Leadership and the community - KR: Get community feedback on a visualization map displaying how existing features are projected to be arranged or remain the same to accommodate modes, curation and customized tooling for patrollers, microcontributors and organizers - KR: Share a draft user workflow of primary target audience existing experience and aspirational experience including use of notifications with Product Leadership and Community Members for emerging countries - KR: Develop an audit report of gaps in accessibility and establish baselines for measuring progress on equity **Timeline** The app analysis will take place May 2021 through the end of June 2021. **Project Background** The Android team is setting out to accomplish a 3-5 year long roadmap detailed on the MediaWiki Roadmap. It is described as 3-5 years to align with the product strategy and to provide the team flexibility with timelines. During the Android offsite, the team identified the following primary user groups: - Collaborators - Patrollers - Curators - Invited Users - Organizers - Micro Contributors - Lifelong learners Primary is defined as groups we are deliberately empowering through feature improvements and creation. We also identified the following secondary user groups: - Multilingual Editors - Multilingual Readers - Power Editors - Educators - Structured Learners - Low Bandwidth users - Offline users - Visually Impaired Readers - Tool Developers - Media Consumers Secondary users are users we will actively ensure we are not making their workflows harder as we build new features. **Project Summary** Prior to implementing new features, our team’s designer will provide a visual representation of our existing workflows, with a focus on our primary target users. The visual representation will show the possible pathways a user can use to accomplish a goal, and where they may reach a blocker or inconveniences for achieving their goal. Once this map is complete, the team will discuss high level interventions that we could explore to alleviate blockers and inconveniences while assessing if the interventions would inconvenience our secondary user group. The interventions will be added to the architecture map to show our high level ideas for improving the experience for our target audiences and how it will change components of the flow, as well as possible architectural changes. Once the updated map is complete, the team’s data analyst will partner with the Product Manager to establish baseline metrics for communication related interventions, with those interventions being the first phase of the roadmap. **Goals** Help the Android team think proactively about where we will place new features and how the logic of our workflows will interact with one another. Help the community and Product Leadership visualize our as-is state for our current users and how the as-is state will evolve once our roadmap is completed. **Reference User Maps ** NOTE: The map does not have to look exactly like the ones provided as a reference below, but it does need to be a visual map displaying workflows of the Android app. - An updated version of https://upload.wikimedia.org/wikipedia/commons/f/f3/Wikipedia_Android_app_workflow_-_Feb_2018.pdf with explanations of workflows for our primary audiences - [[ https://docs.google.com/drawings/d/1aiDtZaqSut1LLokktT4J0jFbn21RelcYl_bRWN71qkc/edit | 5.0 Master Flow ]] - Slide 7 of FY21: [[ https://docs.google.com/presentation/d/1Yc9Dv0MA8e7c_9FgcKR9qXEjl-GBLc3FjgrUOEfBor4/edit#slide=id.gd29748ca23_0_329 | Navigation Explorations on iOS ]] - https://www.figma.com/file/kU1p9eny9TCJTlG8ZsnhsV - [[ https://docs.google.com/presentation/d/1VeUAepRzLqUFGlIn7qChlvFweSCWIfeJGA2GrjbF7W0/edit#slide=id.g44dfc8f1c9_0_467 | Understanding First Day - User flows ]]

**Background** The Android team is setting the strategic direction of the Android app. **Team OKR ** Objective 2: Objective: Conduct and share a gap analysis of our app’s architecture and our team roadmap to get buy in from Product Leadership and the community - KR: Get community feedback on a visualization map displaying how existing features are projected to be arranged or remain the same to accommodate modes, curation and customized tooling for patrollers, microcontributors and organizers - KR: Share a draft user workflow of primary target audience existing experience and aspirational experience including use of notifications with Product Leadership and Community Members for emerging countries - KR: Develop an audit report of gaps in accessibility and establish baselines for measuring progress on equity **Timeline** The app analysis will take place May 2021 through the end of June 2021. **Project Background** The Android team is setting out to accomplish a 3-5 year long roadmap detailed on the MediaWiki Roadmap. It is described as 3-5 years to align with the product strategy and to provide the team flexibility with timelines. During the Android offsite, the team identified the following primary user groups: - Collaborators - Patrollers - Curators - Invited Users - Organizers - Micro Contributors - Lifelong learners Primary is defined as groups we are deliberately empowering through feature improvements and creation. We also identified the following secondary user groups: - Multilingual Editors - Multilingual Readers - Power Editors - Educators - Structured Learners - Low Bandwidth users - Offline users - Visually Impaired Readers - Tool Developers - Media Consumers Secondary users are users we will actively ensure we are not making their workflows harder as we build new features. **Project Summary** Prior to implementing new features, our team’s designer will provide a visual representation of our existing workflows, with a focus on our primary target users. The visual representation will show the possible pathways a user can use to accomplish a goal, and where they may reach a blocker or inconveniences for achieving their goal. Once this map is complete, the team will discuss high level interventions that we could explore to alleviate blockers and inconveniences while assessing if the interventions would inconvenience our secondary user group. The interventions will be added to the architecture map to show our high level ideas for improving the experience for our target audiences and how it will change components of the flow, as well as possible architectural changes. Once the updated map is complete, the team’s data analyst will partner with the Product Manager to establish baseline metrics for communication related interventions, with those interventions being the first phase of the roadmap. **Goals** Help the Android team think proactively about where we will place new features and how the logic of our workflows will interact with one another. Help the community and Product Leadership visualize our as-is state for our current users and how the as-is state will evolve once our roadmap is completed. **Reference User Maps ** NOTE: The map does not have to look exactly like the ones provided as a reference below, but it does need to be a visual map displaying workflows of the Android app. - An updated version of https://upload.wikimedia.org/wikipedia/commons/f/f3/Wikipedia_Android_app_workflow_-_Feb_2018.pdf with explanations of workflows for our primary audiences - [[ https://docs.google.com/drawings/d/1aiDtZaqSut1LLokktT4J0jFbn21RelcYl_bRWN71qkc/edit | 5.0 Master Flow ]] - Slide 7 of FY21: [[ https://docs.google.com/presentation/d/1Yc9Dv0MA8e7c_9FgcKR9qXEjl-GBLc3FjgrUOEfBor4/edit#slide=id.gd29748ca23_0_329 | Navigation Explorations on iOS ]] - https://www.figma.com/file/kU1p9eny9TCJTlG8ZsnhsV - [[ https://docs.google.com/presentation/d/1VeUAepRzLqUFGlIn7qChlvFweSCWIfeJGA2GrjbF7W0/edit#slide=id.g44dfc8f1c9_0_467 | Understanding First Day - User flows ]]

**Background** The Android team is setting the strategic direction of the Android app. This will be done in the following steps: Design Q4 Brief **Team OKR ** Objective 2: Objective: Conduct and share a gap analysis of our app’s architecture and our team roadmap to get buy in from Product Leadership and the community - KR: Get community feedback on a visualization map displaying how existing features are projected to be arranged or remain the same to accommodate modes, curation and customized tooling for patrollers, microcontributors and organizers - KR: Share a draft user workflow of primary target audience existing experience and aspirational experience including use of notifications with Product Leadership and Community Members for emerging countries - KR: Develop an audit report of gaps in accessibility and establish baselines for measuring progress on equity **Timeline** The app analysis will take place May 2021 through the end of June 2021. **Project Background** The Android team is setting out to accomplish a 3-5 year long roadmap detailed on the MediaWiki Roadmap. It is described as 3-5 years to align with the product strategy and to provide the team flexibility with timelines. During the Android offsite, the team identified the following primary user groups: - Collaborators - Patrollers - Curators - Invited Users - Organizers - Micro Contributors - Lifelong learners Primary is defined as groups we are deliberately empowering through feature improvements and creation. We also identified the following secondary user groups: - Multilingual Editors - Multilingual Readers - Power Editors - Educators - Structured Learners - Low Bandwidth users - Offline users - Visually Impaired Readers - Tool Developers - Media Consumers Secondary users are users we will actively ensure we are not making their workflows harder as we build new features. **Project Summary** Prior to implementing new features, our team’s designer will provide a visual representation of our existing workflows, with a focus on our primary target users. The visual representation will show the possible pathways a user can use to accomplish a goal, and where they may reach a blocker or inconveniences for achieving their goal. Once this map is complete, the team will discuss high level interventions that we could explore to alleviate blockers and inconveniences while assessing if the interventions would inconvenience our secondary user group. The interventions will be added to the architecture map to show our high level ideas for improving the experience for our target audiences and how it will change components of the flow, as well as possible architectural changes. Once the updated map is complete, the team’s data analyst will partner with the Product Manager to establish baseline metrics for communication related interventions, with those interventions being the first phase of the roadmap. **Goals** Help the Android team think proactively about where we will place new features and how the logic of our workflows will interact with one another. Help the community and Product Leadership visualize our as-is state for our current users and how the as-is state will evolve once our roadmap is completed. **Reference User Maps ** NOTE: The map does not have to look exactly like the ones provided as a reference below, but it does need to be a visual map displaying workflows of the Android app. - An updated version of https://upload.wikimedia.org/wikipedia/commons/f/f3/Wikipedia_Android_app_workflow_-_Feb_2018.pdf with explanations of workflows for our primary audiences - [[ https://docs.google.com/drawings/d/1aiDtZaqSut1LLokktT4J0jFbn21RelcYl_bRWN71qkc/edit | 5.0 Master Flow ]] - Slide 7 of FY21: [[ https://docs.google.com/presentation/d/1Yc9Dv0MA8e7c_9FgcKR9qXEjl-GBLc3FjgrUOEfBor4/edit#slide=id.gd29748ca23_0_329 | Navigation Explorations on iOS ]] - https://www.figma.com/file/kU1p9eny9TCJTlG8ZsnhsV - [[ https://docs.google.com/presentation/d/1VeUAepRzLqUFGlIn7qChlvFweSCWIfeJGA2GrjbF7W0/edit#slide=id.g44dfc8f1c9_0_467 | Understanding First Day - User flows ]]