Tasks

Build off prototype from offsite

• Localization (put strings into Translate Wiki for volunteers to translate ASAP) - T392010
• Adjust components to match new wireframes - T392011
• Connect Logged-out screen - T392027
• Get editing count working - T392028
• Add navigation to saved articles tab - T392033
• Add editing empty state - T392035
• Add suggested edits component - T392036
• Add survey (using YiR Component): Are you satisfied with your "Activity" screen? What else would you like to see here in the future? - T392297
• Design touch ups (iPhone portrait only, do not need to optimize for landscape or iPad) -
• Wrap up in 30-day A/B/C test: see details below
• Instrumentation T392248
• Add link to edit history T392164 (nice to have)

Background

In a recent study on Editing and Reading on the iOS App, we saw that notifications about edit counts and activity related to their contributions were motivating for some new editors. One experienced editor also mentioned feeling encouraged by seeing their edit count on the desktop version. But, unstructured editing on the iOS app requires using Wikitext, which is intimidating to most newcomers.

We know from our recent experiences with Year in Review that viewing insights is motivating for both readers and editors, and that folks are willing to create an account to have access to them.

We want to learn if immediately providing a structured way to edit (via “Add an image”), and immediately providing edit activity statistics helps newcomers on the iOS App activate at a higher rate.

Hypothesis
If we temporarily present a population of new account holders with an invitation to add an image via Suggested Edits within an Activity tab, we'll learn if this explicit call to action, and corresponding structured workflow, is ≥25% more effective at increasing constructive activation than a generic invitation to "Edit" Wikipedia presented in the same place.

How will we know we were successful

• Validation
  • KR 1.1 Users in the experiment group C with access to Add an image in their activity tab have a 25% higher constructive activation rate compared to those in group B who did not have access
    • Fallback: KR 1.1 Users in the experiment group C with access to Add an image in their activity tab have a 25% higher activation rate compared to group B
  • KR 1.2 15% of logged-out users users who open the Activity tab click on the prompt for unlocking insights
• Guardrails
  • Revert rate in the variant groups B or C does not exceed 18%
• Curiosities
  • What other features are users looking for in the activity tab? What did they expect to see there? (Survey)
  • By how much did the constructive activation rate vary across groups A, B, and C?
  • How many accounts were created from the activity tab?

Test plan

Wrap up in 30-day A/B/C test
Everyone on zh, fr, tr, es is in the test. All other wikis see current History tab.

• • A Group - 1/3 see no activity tab, keep current history tab
  • B Group - 1/3 see new A activity tab with generic edit CTA.
  • C Group - 1/3 see new A activity tab with Add an Image edit CTA.
• Show to iPhone users only

Must Haves

• Reading history should still be accessible for users who opt not to log-in or engage with the Activity tab (Ensure VoiceOver users especially can still access History)
• All users in target audiences see the new Activity tab
• Logged-out users
  • See prompt to log-in/create an account for insights
• Logged-in users
  • Control: Prompt them to edit to make their editing stats increase
  • Variant: Prompt them to add an image to make their editing stats increase. Show entry point to Add an image
  • Both: Display at least one reading insight
• “Add an image” is available to users under 50 edits for the target audiences in the experiment group
• Editing stats increase after someone makes an edit
• After engaging with the Activity tab, users are asked for their feedback through an in-app survey or Google Form survey

Target Quant Regions and Languages

15-day experiment with all app users in the following languages would see the experimental Activity Tab

• Chinese
• French
• Turkish
• Spanish

Target Qualitative Audience

• Newcomers
• Engaged readers

Concepts

https://whimsical.com/ios-activity-tab-TaLYNNWgMfhn6VM1Lb1Xja

Final designs: https://www.figma.com/design/G80XioWE4CdjKdcOQ14dJv/iOS---Activity-tab?node-id=113-3701&m=dev

QA Notes

This experiment will be ready starting in TestFlight 7.7.5 (5209).

• Note that upon first launch of the new app version, the app will randomly assign a user to the experiment if you have a target wiki as a primary app language (33% in group A control, 33% in group B generic edit CTA, 33% in group C Add an image CTA).
• If you need to force a particular variant for testing, you can subsequently go into Developer settings and choose a particular toggle. Note that after selecting a toggle, you must terminate the app and relaunch for the override to take effect.