#### Problem ([Video](https://tome.app/rs/share-reading-lists-usability-test-analysis-clbxhayjv04ckc63beqyamuf9?page=clbxjrptj00a13b6gg25fln75))
- Participants expected to see a preview of the reading list on the web in the usability tests.
- They asked for more information and context before a list was imported.
- Importing something unknown felt weird to the participants.
#### Solution
- Since there's a legal/community constraint not to show previews on the web (yet), we're going to explore previewing a shared reading list in the app before the actual import happens ([Slide](https://tome.app/rs/share-reading-lists-usability-test-analysis-clbxhayjv04ckc63beqyamuf9))
- We should consider renaming "Import" to "View"
#### Design explorations ([[ https://www.figma.com/file/A7j094zru5Zfp2xNqqCuty/Share-reading-lists-T313269?node-id=381%3A20734&t=4EBal89hlfP15asf-4 | Figma ]])
| Old design | **A:** Header image | **B:** Basic list preview | **C:** Article previews
| {F36555705} | {F36555709} | {F36555712} | {F36555723}
- All explorations
- Hide the optional "description" field to reduce cognitive load
- Suggest a default list name, e.g. Shared reading list `%datetime`. The keyboard is disabled; users can choose to rename it.
- Variant A + B likely achieve the goal of previewing the contents of the reading list before importing (low implementation effort)
- Variant C features articles of the list and lets users individually select the ones they'd like to import.
- Does not feature a select/deselect all button to reduce cognitive load and safe screen estate
- Challenge: How is scrolling handled? It needs to be explored by engineers (@cooltey featured this behavior in a prototype a while ago)