Save-for-later must be reachable while browsing
Aliases: read later · in-context bookmark · star while reading
What it is
Save for later pins what is on screen into a private list, so someone can leave when attention runs out and come back. The entry has to exist during browsing—reading the body, skimming a list, opening detail—not after hunting a place named Saved and searching the item back in. This is “pin it now.” Where the list lives afterward, how a large list is organized, finding the original by search, and archiving old items are later steps.
Why it happens
Save-for-later happens in the moment attention is already insufficient: a meeting, a deep trail, a title-only skim. The only usable controls are in the current viewport. If the star, flag, or reading-list entry vanishes on scroll, sits in a third-level overflow, or appears only after a login wall, people pay more: copy the link into notes, screenshot, message themselves. Those bypasses never enter the product’s return structure, so the content operation fails. The entry also has to be low-commitment: one light tap, not a forced folder, note, or public post—that upgrades pinning into organizing, and people skip the pin. Equal-size save controls on every row will fight Open and Share; reachable does not mean largest, it means still findable in the frame where leaving begins.
Studying it
On a slightly long item, insert a reason to leave mid-way (next task, time up). See whether people can pin it without leaving the page.
Independent variables: whether the entry stays during scroll, whether login is required first, whether pinning demands a folder. Dependent variables: pin success, copy/screenshot bypass rate, time from decide-to-leave to pinned.
A script that says “please bookmark this article” measures button-finding, not save-for-later. Make saving optional inside another job. Test list streams and long-form detail separately; the entry sits in different places. Impression counts are not success—seen but untappable (keyboard covering it, login wall) is still unreachable.
Where it stops holding
If a paywall forbids saving the full text while logged out, at least allow pinning title and link, or there is no hook to return. When law or license forbids a local copy, save is a pointer, not a download, and the label must not say “save to device.” Live feeds expire; the entry can succeed and the target can still vanish—that is a return-path problem, not a reason to refuse the pin. A tool dashboard has no “read later” object; a star there mis-saves configuration.
Applying it
- Put the same save control on the row and in the reading surface. On long pieces it stays tappable and does not roll away with the title.
- The first click only pins. Folder, tag, and note are skippable next steps, not gates.
- While logged out, store the pointer on-device and merge after login; do not open registration first.
- Verify: stop people mid-read with a reason to leave; they should finish the pin on the current page. Copying the link or failing to find the star means unreachable. Check whether a login wall blocked this pin.