Tasks

• T363606: [XL] [Tech Debt] Replace custom navigation bar with system bar
• T364755: Audit modals, tooltips, and alerts - identify those affected by Nav round 2

Background

This is the 2nd phase of the larger Navigation Refresh (T373712) planned for the iOS App. This work is part of the Annual Plan WE3, 3.1 KR to Release two curated, accessible, and community-driven browsing and learning experiences to representative wikis, with the goal of increasing the logged-out reader retention of experience users by 5%.

Our draft hypothesis is: If we make the article search bar more prominent, we will increase the number of users who initiate searches by 8%, possibly leading to a 1% increase in search retention rate for logged out users.

How will we know we were successful

• Validation
  • KR 1.1 8% increase in users initiating Search from article view
  • KR 1.2 1% higher repeated engagement with new article search bar
  • KR 1.3 5% increase in average pageviews/unique user for those who engaged new article search bar

• Guardrails
  • GR 1.4 No more than 10 negative user complaints about changes to the Navigation that can’t be addressed
  • GR 1.5 No more than 5% increase in app uninstalls

• Curiosities
  • CR 1.6 Do we see a difference in the KRs for logged in users vs logged out users
  • CR 1.7 Did usage of Places or History change due to their move into Search?
  • CR 1.8 Do users prefer a different location for the article view search?

Requirements

• Navigation bar
  • Make navigation bar elements system, instead of custom
  • Create standardized header for permanent views (Explore, Search, Saved)
  • Reserve space for Tabs in the standardized header
  • Search bar is more prominent within article view
• From the article, users can
  • Search
  • Go Back to previous article
  • Access Profile
  • Navigate back to main view
• Search Tab
  • Move Places or History into Search, and adjust recently searched
  • Move recently searched so it displays after clicking into search
  • Show tooltip letting users know that Search has been updated
• Design only:
  • Created updated views for Temporary accounts where needed

User Stories

Primary

• As a reader checking out the Pluto article from a browser link, I want to have quick access to Search, so I can quickly pull up the NASA article without having to navigate back to the main view.
• As a student who uses iOS devices, I want to have navigational elements that make sense to me without thinking, so that I can just start using the app for researching with no learning curve.

Secondary

• As a tourist in a new city, I want to see recommendations about Places nearby me while I search for a monument, so that I can continue to learn more about the city.
• As a student researching Geology, I want to have access to my Tabs from the main views of the app, so that I can jump between different Wikipedia articles I am using for sources.
• As an experienced editor, I would like there to be an explicit "Contribute" section within the app, so that I can find contribution tools, and so newcomers can find new ways to contribute.

Target Quant Regions and Languages

Release will be available to all users, but we will measure success using these audiences:

• Arabic users in Egypt, Sudan, Algeria, and Morocco
• French users in Sub Saharan Africa

Target Qualitative Audience

• Readers who use iOS and the Wikipedia app
• Guardrail Groups
  • Low Bandwidth Readers
  • Blind and Low Vision Users

Designs

TBA

Reference

• Overall iOS Navigation Update (Alex) Figma, https://docs.google.com/presentation/d/1p7Efp4ENZJ_w7BS5bLUDMtFkVHgIbYZt2oTNxRsJUM0/edit#slide=id.g2eda053f939_0_86
• First Navigation Update - T373714: [Sub-Epic] Navigation Refresh Part 1 - Sept 2024