Tasks

High priority

• T363606: [XL] [Tech Debt] Replace custom navigation bar with system bar
• T382031: Track impressions for article views
• T383821: Standardized header: Places
• T383822: Standardized header: Saved
• T383825: Standardized header: Search
• T383826: Standardized header: History
• (Instrumentation subtask) T384972: Instrument new profile buttons (Search, Places, History, Saved)
• (Instrumentation subtask) T384952: Add column `action_data` to current.yaml doc for ios_search schema
• T383828: Create variant for Article search bar A/B Test
• T383829: Assign users for Article search bar A/B test

iPad Design changes required, surfaced from System Nav Bar work

• T383471: System Nav Bar [Design Review] - Fix iPad Explore logo S (Fix iPad Explore logo. Left align)
• T383837: System Nav Bar [Design Review] - Remove Article W logo on iPad M (Fix Article logo, left align. Pop to root on tap)
• T383839: System Nav Bar [Design Review] - Show navigation bar buttons at all times during scroll on iPad S (Show nav bar buttons at all times during scroll on iPad)

Nice to have

• T382032: Add round 1 of sources for article views in iOS App
• T384510: Move History into Search
  • T384512: Move recently searched (required if the above is done)
  • T384516: Tooltip on updated Search (required if the above is done)
• T383831: iPad floating tab bar search icon
• T364755: [Spike] Audit modals, tooltips, and alerts - create visual
• T383759: System Nav Bar [Design Review] - Hide floating tabbar upon scroll for iPad
• T384845: Update remaining X close buttons
• T383468: System Nav Bar [Design Review] - Trigger show animation upon scroll up
• T383464: System Nav Bar [Design Review] - Places search fixes
• T383459: System Nav Bar [Bug] - Code Cleanup
• T383457: System Nav Bar [Bug] - Empty long press back button titles
• T383832: System Nav Bar [Bug] - Center Places Empty State with keyboard
• T383840: System Nav Bar [Design Review] - Adjust animation speed of header hiding
• T383469: System Nav Bar [Design Review] - Disable navigation bar hiding if content is short

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

For the Article Searchbar test:

Validation
These will be measured via an A/B test

• KR 1.1 8% increase in users initiating Search from article view
• [Primary metric] KR 1.2 1% higher app retention rate for logged-out users that had the more prominent article search (using 2-week retention)
• KR 1.3 5% increase in average pageviews/unique user for those who engaged new article search bar

Guardrails

• GR 2.1 No more than 10 negative user complaints about changes to the Article view that can’t be addressed (Measured by user feedback through app store & support email)

Curiosities

• CR 3.1 Do users prefer a different location for the article view search? (Measured by user feedback through app store & support email)
• CR 3.2 What was the feature retention rate for article search for both A & B? (Recalculate 1.2 but using return to engage with article search as definition of retention, not return to overall app)

For Navigation Phase 2

• GR 2.1 No more than 5% increase in app uninstalls (vs baseline)
• GR 2.2 No more than a 10% increase in overall app crashes (for all releases after system nav vs before, measured by engineering)
• GR 2.3 No more than a 10% decrease in pageviews with the source of "history" after its move into Search
• GR 2.4 No more than 10 user complaints about history moving into Search (as measured by support email, and app store reviews)

Curiosities

• CR 3.1 Did overall account creations increase as a result of the Profile menu being accessible from all screens? (Baseline of 15 days before vs Experiment Date Range)

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

Figma

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