=== Background
The reading list sync service created has a concept of a "Default" reading list, which an article can be saved to without being required to be added to a user-created reading list.
Android reading list users currently save articles to a specific user-created list; whilst iOS intends to allow both 'one-tap' quick saving which would save articles to the system 'default' list as well as the option to organize into other reading lists.
Notes:
- The name of the Default list is an ID string in the back-end, with a localized name shown to the user (iOS initially calling it "Bookmarks"
- The default list cannot be renamed
=== Problem
Until such time as Android starts making use of a default reading list, it may be confusing for users to see it appear on their device.
== Proposed solution
====Proposal A. Android users only see the 'default reading list' if it contains at least 1 article, and cannot change the default list name
Presuming only iOS will be making use of default lists initially, the majority of Android users will not see the default list and can continue as normal. It is only a cross-platform user who has synced reading lists where it is possible that the 'Bookmarks' list will be shown if for example, the user adds an article to that default list on their iPad and then opens reading lists on their Android phone.
* **PROS**
- Least disruptive to the majority of reading list users who are only on the Android platform
* **CONS**
- May be confusing down the line when syncing is more widely available on web
====Proposal B. All Android users see the default read-only bookmarks list
* **PROS**
- Introduces the concept of a 'default' list could be beneficial to save the step of requiring users to create an initial list
- Users can take advantage of the (proposed) higher limit of articles for the default list
- Showing the default list on Android is not as jarring for cross-platform users
- Opens the door to potentially switching to the one-tap quick-saving model in future
* **CONS**
- May be slightly confusing for the existing reading list users that a new non-deletable list is shown
- Some work required to update messaging in existing flows (eg. user education message when user first saves an article)
====Proposal C. Android adopts the iOS method of one-tap saving to default list
* **PROS**
- Simplifying the same set of actions across platforms
- Reduces action for the majority of users who value the 'saving' articles aspect over the organizing aspect of reading lists
* **CONS**
- Introduces potential confusion to existing Android reading list users
- **Increases** the action required for significant minority of power users of reading lists (who will need to perform at least one extra tap to move the article from the default list to their own intended list)
- More development and testing time required revise existing workflow
- Changing the existing paradigm for Android to a new untested method without data and feedback is ill advised.
NOTE: RHo: FWIW, I do not recommend Proposal C to start with due to the stated 'cons', but we may consider it after evaluating user feedback from iOS and revising analytics of default list usage from new users on Android (assuming we go with Proposal B).
====Revised workflow for adding to a reading list for proposal C
# User taps on the bookmark icon to add an article (previously unsaved) to a reading list
# A snackbar notification appears advising that the article has been saved to the the default list, giving users the action to "MOVE" it to another list instead
# User taps on the "MOVE" action to move it to another list, and a bottom list appears with the other lists to move the article to:
| Step 1. {F10717984} | Step 2. {F10717939} | Step 3. {F10718051}
=== QA required? {icon check color=green}
==== Scenario: Cross-platform user adds articles to the default reading list on iOS