Page MenuHomePhabricator

As a multilingual reader, I would like to know why an article might not be available in any other languages or specific languages
Closed, ResolvedPublic

Description

Why are we doing this

During usability testing a participant landed on an article that was only available in German. This lead to some confusion when they tapped on the Languages panel in the article view, which appeared empty. How might we create an empty state for this panel that helps people understand how languages work on Wikipedia? Additionally, how might we make this panel more friendly to use for multilingual readers?

Feature job story

As a multilingual reader, I would like to know why an article might not be available in any other languages or specific languages

Scenarios

  • Article is only available in 1 language
  • Article is not available in a person's selected app languages
  • Generally, it might be good to know how many languages the article is available in and why

Proposed design

Design details

Only show this empty state when no other languages are available for a given article (eg. https://en.wikipedia.org/wiki/Myriam_Gurba)

🔗Figma link: https://www.figma.com/file/Jcc9DMzO29Gk1nOndjm4jj/Language-Variant-work?node-id=239%3A622

No other languages available.png (667×375 px, 20 KB)

Event Timeline

@JMinor just double checking that this should be on Bonefish and not Manta Ray ;)

It depends on the scope of the solution. If we just add an "Article not available in other languages." string for now, I'd like do that in Bonefish. If we're doing a broader fix for all the stories, then yeah, I'd likely move it forward.

cmadeo updated the task description. (Show Details)
cmadeo updated the task description. (Show Details)
cmadeo updated the task description. (Show Details)

Engineering note - WMFEmptyView.h and UIViewController+WMFEmptyView.h already have some empty view setups that we should be able to hook into.

Notes from engineering sync - looks like the modal style has changed a bit to the iOS-13 style and search looks a little different - to make this a speedier and since it's given us trouble in the past, I propose we keep the full screen look and only add the empty state view for now. Also @cmadeo, I can't remember where we landed on this, but should the search bar be visible at all here, if there are no languages available to search?

Thanks @Tsevener! No worries about keeping it fullscreen for now! Also, I'm cool with removing the search bar if it's not adding too much complexity for you all!

Will be in TestFlight build 6.8.1 (1812). Note we added a loading state as well as a part of this.

JMinor claimed this task.