Wikimedia Apps/Team/iOS/Watchlist/ja

背景
ウィキペディアのコミュニティが成長し進化し続ける中で、利用者のニーズや要望に耳を傾け、それに応えることは非常に重要です. その中で、多くの利用者に共感していただいたのが、ウィキペディア アプリにウォッチリスト機能を搭載することです. The Android app added the Watchlist feature in 2021 and improved it in 2022. This year we will bring Watchlist to iOS. この機能により、利用者は気になる記事をリストとして管理でき、その変更や編集を容易に把握できます.



目的
私たちの主な目的は、ウィキペディアの iOS アプリで、利用者がウォッチリストに保存することで記事の変更を追跡できるようにすることです. They will also have access to undo, thank, and rollback actions.

仮説
北欧や西欧の経験豊富なアプリ編集者による編集数を増やしていくことになると考えています. また、米国やカナダではアプリでの編集頻度が低い経験豊富な編集者による編集が増加し、この地域からの編集のシェアはページビューやインストールと同等になると考えています. 利用者がモバイル機器でウォッチリスト機能にアクセスできるようにすることで、ウィキペディアでの荒らし行為をより早く軽減できるようになると考えています.



仮説の検証
以下の成長ターゲット地域における iOS アプリのオプトイン データの流入をモニタリングすることで、仮説を検証していきます:


 * 北・西ヨーロッパ
 * 北アメリカ

北・西ヨーロッパは、インストールに比べて、編集回数が多いという理由で選ばれました. この地域の編集者は、ウォッチリストの体験を強化し、興味のある記事の追跡や監視を容易にすることで、より多くの編集を行えるようになると考えています. 米国とカナダは、ページビューやアクティブ インストール数が多いのに比べて編集数が不釣り合い、というデータに基づいて選ばれました. 編集者数を増やすことで、アクティブなインストール数にもっと比例させることができると考えています.

Key performance indicators

 * Increase in edits from experienced editors in Northern and Western Europe
 * 10% increase in edit activity from US and Canada
 * 10% higher completion rate with undo and revert than web
 * 60% of users that engage with watchlist feature report it helping them mitigate vandalism faster and overall satisfaction with feature

Additionally, when we will conduct usability testing, we will look for a diverse group of users to ensure the functionality is used by people from a wide variety of groups. In addition to primary languages spoken in this region, we will be hoping to include testers that speak Spanish, Chinese & Punjabi.

We are also hoping to diversify the age groups, visual abilities, handedness and genders.

Why native implementation matters
The Watchlist feature being native is important for several reasons:


 * 1) Mobile-first experience - Native integration allows users to remain in the app for contributions and access their watchlist offline, ensuring a seamless experience.
 * 2)  Accessibility - A native implementation ensures that the feature adheres to the user's font/theme settings, supports offline access, and is compatible with screen readers.
 * 3)  Personalization and customization - Users can personalize their watchlist experience through theming and other customization options.
 * 4) Innovation -  A native watchlist feature supports multilingual feeds, allowing users to follow articles in multiple languages.
 * 5)  Safety -  Native implementation helps mitigate vandalism by providing tools to monitor and report suspicious activity.
 * 6) Continuity - Users can benefit from features like filters, watchlist expiry, and a count of articles being watched, ensuring consistency across platforms

iOS watchlist page created on MediaWiki.

We are currently iterating on early stage designs. We are discussing and describing tasks.

Early Stage Designs!
We have some early stage designs for the iOS Watchlist feature as well as some interesting updates relating to work around navigation.

Main Page

So how will the main page of watchlist look like? We have two variations.

Design 1: Top Navigation


 * The first variation of the watchlist page has the filter at the top right of the app.
 * This design has pro of being quite similar to the Android version hence a very similar experience for cross platform users on mobile.
 * Please note that in the first iteration of the iOS watchlist we will not have the search and filter functionalities and they are slated for the next version.



Design 2: Bottom navigation
 * The second design of the watchlist page has the filter icon at the bottom of the screen along with an icon to see other Wikipedia projects such as Wikidata.
 * This design also has the pro of bringing the filter icon closer to users.



Empty States

 * An "empty state" is a user interface (UI) design concept that occurs when there is no data or content to display in a particular section or screen of the app. This can happen for several reasons, such as when a user first launches the app, clears all data, or encounters an error that prevents data from loading.
 * We have designed the empty states for the Watchlist. There are two scenarios for the Watchlist. The first entails a scenario where the user has not logged in to the app while the second entails a scenario where users do not already have a Watchlist.

Design 1: User is not logged in


 * When the user is not logged in, they get a call to action button to log in or to sign up.

Design 2: User is logged in but does not have a Watchlist


 * When the user does not have any articles, we provide a call to action to explore articles that they would be interested in watching.



Diff View
A "diff view" in Wikipedia refers to a specific comparison view that shows the differences between two versions of a Wikipedia article. When editors make changes to an article, Wikipedia keeps a record of each version in its edit history. The diff view allows users to see the specific additions, deletions, or modifications made between any two versions.

We have two variants of the diff view with the main difference being how comparison looks like:

Design 1: Side by Side Comparison

Here the comparison is side by side. the pro is that comparison is very easy.

The con is that there is only so much text that you can add before the view gets crowded.

Design 2: Stacked Comparison

Here the comparison is stacked. The major pro is that more text can be added without looking too crowded.

Various Actions within the Watchlist

We have also designed other actions such as sharing, clicking the username on the diff view, what selecting the overflow button does, rolling back edits, undoing edits and sending thanks.