Page MenuHomePhabricator

Surface page issues on articles more prominently to Android app users
Closed, ResolvedPublic

Description

Paused until related ticket on mobile web improvements to page issues is done: T159262
Why are we doing this?
  • Make content issues more transparently to readers (currently, users can only access "Page issues" which appears as a bottom sheet by tapping on a menu item called "Content issues" in the article overflow
Current overflow on an example article with a page issue:
image.png (1×1 px, 364 KB)
Example page issues bottom sheet:
image.png (1×1 px, 875 KB)
Another example article with page issues:
image.png (1×1 px, 909 KB)
  • It may encourage users to edit since some issues may be solvable by small contributions (e.g., adding a citation)
Proposed solution
  • Add a "Page issues" alert in the article content under the article title following the same logic as web proposed in task T159262
  • Remove the hidden "Content issues" menu item from the article overflow menu
  • Add a "Page issues" menu item as a section in the "About this article" footer menu (per iOS). Tapping on the "Page issues" menu item should bring up the full screen overlay from the web on T159262
NOTE: This task is closely related to surfacing page disambiguation better as captured on T187204

Event Timeline

RHo renamed this task from [UX-debt] Surface page issues on articles more prominently to users to [UX-debt] Surface page issues on articles more prominently to Android app users .Feb 13 2018, 6:43 PM
RHo updated the task description. (Show Details)
RHo renamed this task from [UX-debt] Surface page issues on articles more prominently to Android app users to [HIGH] Surface page issues on articles more prominently to Android app users .Mar 2 2018, 3:31 PM
RHo claimed this task.
RHo renamed this task from [HIGH] Surface page issues on articles more prominently to Android app users to Surface page issues on articles more prominently to Android app users .Mar 5 2018, 2:59 PM
RHo triaged this task as High priority.

@RHo I think the image for Example page issues bottom sheet is incorrect.

@RHo I think the image for Example page issues bottom sheet is incorrect.

Thanks - just updated!

@RHo From what we discussed today, am I correct in the following interpretation:

  • Regarding disambiguations, since we're already letting them be shown within the article itself, we don't need to re-expose them natively, so we can remove that portion outright.
  • Regarding page issues, for the time being, we're going to let them be shown within the article (as seen below) until further improvements are made in the Web presentation itself.

device-2018-09-27-130830.png (2×1 px, 1 MB)

Hi @Dbrant - yes, correct on both counts!

@RHo From what we discussed today, am I correct in the following interpretation:

  • Regarding disambiguations, since we're already letting them be shown within the article itself, we don't need to re-expose them natively, so we can remove that portion outright.
  • Regarding page issues, for the time being, we're going to let them be shown within the article (as seen below) until further improvements are made in the Web presentation itself.

device-2018-09-27-130830.png (2×1 px, 1 MB)

Change 463334 had a related patch set uploaded (by Dbrant; owner: Dbrant):
[apps/android/wikipedia@master] Utterly remove old Disambiguation and Page Issues code.

https://gerrit.wikimedia.org/r/463334

Change 463334 merged by jenkins-bot:
[apps/android/wikipedia@master] Utterly remove old Disambiguation and Page Issues code.

https://gerrit.wikimedia.org/r/463334

RHo removed RHo as the assignee of this task.Oct 30 2018, 6:45 PM
Dbrant claimed this task.