Page MenuHomePhabricator

As a language variant reader, I want to know that improved variant settings are available
Closed, ResolvedPublic

Description

Why are we doing this?

We are working on improving functionality around language variants and we would like for these updates to be announced to readers who may be interested in using them.

Reader story

As someone who reads Wikipedia in a language variant, I would like to know that it is now possible for me to read in any language variant we support.

Proposed design

👉 Figma: https://www.figma.com/file/Jcc9DMzO29Gk1nOndjm4jj/Chinese-Variant-User-education?node-id=0%3A1
DefaultSepiaDark / Black
Default.png (667×375 px, 47 KB)
Sepia.png (667×375 px, 92 KB)
Dark.png (667×375 px, 87 KB)

Design details

  • Utilize the card style from the Fundraising alert to communicate the update to readers who currently have one or more language variants as one of their app languages on their next log in to the app
  • This alert should be shown to any reader who currently has one or more language variants as one of their app languages on their next log in to the app
  • Text (except for variants as presented) should be translated into the reader's primary language
  • Tapping on the CTA should open the Settings > Languages screen
  • Tapping on 'No thanks' should dismiss the alert
  • This alert should not be shown during a first time user experience (aka first app load)

Proposed copy

Text should appear in the reader's primary language, except for the variant names which should appear as they are below, regardless of their primary language / variant.

Chinese

Title
Updates to Chinese variant support

Body text
The Wikipedia app now supports the following Chinese variants as primary or secondary languages within the app, making it easier to read, search and edit in your preferred variants:

简体 Chinese, Simplified (zh-hans)
繁體 Chinese, Traditional (zh-hant)
大陆简体 Mainland Simplified (zh-cn)
香港繁體 Hong Kong Traditional (zh-hk)
澳門繁體 Macau Traditional (zh-mo)
大马简体 Malaysia Simplified (zh-my)
新加坡简体 Singapore Simplified (zh-sg)
臺灣正體 Taiwanese Traditional (zh-tw)

Other language variants
LanguageTitleBody Text (EACH VARIANT SHOULD APPEAR ON ITS OWN LINE, NOT SHOWN HERE BECAUSE OF LIMITED TABLE SUPPORT)
Crimean TatarUpdates to Crimean Tatar variant supportThe Wikipedia app now supports the following Crimean Tatar variants as primary or secondary languages within the app, making it easier to read, search and edit in your preferred variants: Qırımtatarca, Latin Crimean Tatar Latin (chr-latn); къырымтатарджа, Кирил Crimean Tatar Cyrillic (crh-cyrl)
GanUpdates to Gan variant supportThe Wikipedia app now supports the following Gan variants as primary or secondary languages within the app, making it easier to read, search and edit in your preferred variants: 贛語 原文 Gan (gan); 赣语 简体 Gan, Simplified (gan-hans); 贛語 繁體 Gan, Traditional (gan-hant)
InuktitutUpdates to Inuktitut variant supportThe Wikipedia app now supports the following Inuktitut variants as primary or secondary languages within the app, making it easier to read, search and edit in your preferred variants: ᐃᓄᒃᑎᑐᑦ ᑎᑎᕋᐅᓯᖅ ᓄᑖᖅ Inuktitut, Syllabics (ike-cans); Inuktitut ilisautik, Inuktitut, Latin (ike-latn)
KazakhUpdates to Kazakh variant supportThe Wikipedia app now supports the following Kazakh variants as primary or secondary languages within the app, making it easier to read, search and edit in your preferred variants:Қазақша Kazakh (kk); Қазақша Кирил Kazakh, Cyrillic (kk-cyrl); qazaqşa latin Kazakh, Latin (kk-latn); توتە قازاقشا Kazakh, Arabic (kk-arab)
KurdishUpdates to Kurdish variant supportThe Wikipedia app now supports the following Kurdish variants as primary or secondary languages within the app, making it easier to read, search and edit in your preferred variants: Kurdî Latînî Kurdish, Latin (ku-latn); كوردی Kurdish, Arabic (kk-arab)
SerbianUpdates to Serbian variant supportThe Wikipedia app now supports the following Serbian variants as primary or secondary languages within the app, making it easier to read, search and edit in your preferred variants: српски ћирилица Serbian, Cyrillic (sr-ec); srpski latinica Serbian, Latin (sr-el)
TajikUpdates to Tajik variant supportThe Wikipedia app now supports the following Tajik variants as primary or secondary languages within the app, making it easier to read, search and edit in your preferred variants: тоҷикӣ кирилликӣ Tajik, Cyrillic (tg-cyrl); tojikī lotinī Tajik, Latin (tg-latn)
UzbekUpdates to Uzbek variant supportThe Wikipedia app now supports the following Uzbek variants as primary or secondary languages within the app, making it easier to read, search and edit in your preferred variants: oʻzbekcha lotin Uzbek, Latin (uz-latin); ўзбекча кирилл Uzbek, Cyrillic (uz-cyrl)
TachelhitUpdates to Tachelhit variant supportThe Wikipedia app now supports the following Tachelhit variants as primary or secondary languages within the app, making it easier to read, search and edit in your preferred variants: ⵜⴰⵛⵍⵃⵉⵜ Tachelhit, Tifinagh (shi-tfng); Taclḥit Tachelhit, Latin (shi-latn)

For all languages
Primary button CTA
Review your preferences

Close link
No thanks

Event Timeline

cmadeo updated the task description. (Show Details)

@cmadeo @JMinor Thanks for mocking this up! Here are a few of notes we have from engineering sync:

  1. Note that we will be choosing a variant for them (educated by their iOS device settings) whether they visit Settings or not. Should we indicate what we are defaulting to in some way on this screen?
  2. Should we indicate that they can choose more than one variant if they want?
  3. This is a bit of an edge case but what if they currently have multiple languages chosen that offer variants (like Chinese and Serbian)? Do we show these modals back-to-back with each of the variant choices?
  4. Just an FYI, we made a reminder ticket not to release 6.8 until we have translations in the build. Normally we don't block on translations but this for sure is a case where we'll need them.

Hi @Tsevener!

  1. I think because we give folks the option to review their settings in this message there isn't too much need to reiterate for them what their selected variant is (and hopefully whatever we default to won't be too surprising as it's related to their iOS device settings).
  2. Good point! I updated the text to 'variants' vs. 'variant'
  3. Yeah, unfortunately I think it'd probably be best to show multiple modals back to back.

@cmadeo

I know that alerting the user to variants for other languages is another ticket, but I am considering this the "Show alert for new language variants" ticket.

If the user happens to be using more than one language that now supports variants, we will show one alert per language, right after one another.

This works well if the user taps the "No thanks" button, since we just show an additional alert once the current one is dismissed.

But, if the user taps the "Review your preferences" button, we currently navigate to the language preferences, but then do not show any subsequent alerts.

I think this is quite an edge case since I don't believe there are many users that simultaneously use multiple different languages that support variants.

I can think of three approaches to take:

  1. What is currently implemented. As soon as the user navigates to the language preferences from the alert, the remaining language variant alerts are not shown.
  1. If there are multiple language variant info alerts to be shown, only the last alert has the Review Preferences / No thanks buttons. The earlier alerts have a single "Got it" button that dismisses and brings up the next language variant alert.
  1. After the user returns from language preferences, we show the remaining alerts.

I think #2 is the best choice. #3 will take a fair amount of engineering to do correctly, and do so for what I think is a very rare edge case.

With #2, in the case of a single language (what we think is the overwhelmingly most common case) the behavior is exactly as you have designed.
In the case of multiple languages, we ensure the user knows about each language but is only allowed to navigate away after we give them all the information.

Hi James, Thanks for checking in! I agree that #2 is the best choice.

Tsevener renamed this task from As a Chinese reader, I want to know that improved variant settings are available to As a language variant reader, I want to know that improved variant settings are available .Mar 23 2021, 5:57 PM
Tsevener updated the task description. (Show Details)
Tsevener updated the task description. (Show Details)

FYI, I updated the description to be more general to all language variants, not just Chinese, to make it easier on QA.

Note we are not allowing variants to interrupt the user's flow if they are deep linking to a particular modal presentation (like app settings) or a particular navigation push (like an article) on launch, in this case it will try to present the next time they launch. The user will only see the variant modal the first time they launch on 6.8.0 and aren't drilling into a particular screen.

IMG_0141.PNG (1×750 px, 377 KB)
image.png (667×375 px, 53 KB)

This is working well for me @Tsevener + @James_Dempsey!

Feel free to tell me now is not the time, but would it be possible to make some tweaks to the design of this modal?

If tweaks are okay:

  • It'd be great to remove the outline for this button/button style
  • Would it be possible to use the 'paper' background color at 75% opacity as the overlay?
  • Update the Title font to SF UI Display - Bold - 17pt
  • Increase modal width to 325 pt
  • Increase line spacing/leading to 20 pt

Thanks @cmadeo! These tweaks do look much better - the only trickiness is that this modal is integrated into the same system as all of our other modals so we'll need to either add some tiptoeing around to be sure it only affects this one or apply the changes across all the other modals and test them. Can we split these tweaks off into a separate task and we can tackle it next week if there is time?

@Tsevener sounds good! Yes I'd love to see these changes applied universally to all of our modals so the task seems pretty large! Let me make a sub task off of this one for that work.

ABorbaWMF subscribed.

Looks good on 6.8.0 (1804) with the exception of Tachelhit, which is a known exception

JMinor claimed this task.