Per our post stand-up discussion, lets do a bit of user outreach/research before we commit to requirements for variants in the APIs
Three reader personas we want to understand:
- Exclusive simplified readers users whose primary or only form of literacy is simplified characters
- Exclusive traditional readers users whose primary or only form of literacy is traditional characters, or who have strong identity associations with traditional characters
- Mixed or fluid readers users who can read comfortably in either character set
For now, we won't try to cover other variants or user types (such as editors) to keep things tractable.
Initial research questions:
- Do users ever want to have multiple simultaneous variants for mixed language views (such as in the Search or Explore views) or do they expect one "Chinese" entry with a single variant preference?
- Do these users, during app install/set up, expect to manually select a variant, or more than one variant?
- Do they expect to bookmark or save articles from two variants as "different" articles (ie. two entries in their reading list) even though they are actually the same article "under the hood"?
- Do these users find and understand the variant options on the web site?
- Do these users find and understand their reading options, if they are presented as languages in the app interface(s)?
- Do these users find and understand the options, if they are presented as a secondary setting like "Variant" in the app interface(s)?
Last but not least, it would also be good to reach out to communities (either on wiki or off) to get their sense of how this should be presented. Again, this is a reader focused set of questions, but asking the long time readers who are also editors seems like a good step.