Designing shareable collections without making users create an account

同思远 — Sat, 14 Nov 2026 05:26:46 +0000

A collection tracker has two different kinds of state: the list someone is editing and the list they want another person to see. Keeping those separate was an important design decision for LootPrism, a Fortnite tool I work on.

The editable collection is saved in the current browser. A shared link captures the selected collection at the time of sharing. Opening that link shows the snapshot instead of silently overwriting the receiving device’s saved progress. To continue on another device, the user explicitly imports it; when progress already exists there, the interface offers a merge.

This makes a shared link stable. A friend can open yesterday’s link and see what was shared yesterday. It also gives the interface an obligation: explain that editing a collection does not update an old link. After making changes, the user creates a new snapshot.

The same distinction matters for image exports. An image can be a full collection, a missing list or the current filtered view. A QR code should lead to the represented snapshot, while the destination should also offer a clear way to create a separate personal checklist.

This approach removes account setup from a small tracking task, but it does not provide automatic synchronization. Clearing browser data still removes locally saved progress. The product needs a visible sharing and import flow rather than calling the feature cloud sync.

You can try these interactions at https://lootprism.com/sprites/. I am interested in feedback on when an explicit import is clearer than automatic synchronization.

Disclosure: I work on LootPrism. This draft was prepared with AI writing assistance and reviewed against the product’s actual behavior.

DEV Community: 同思远

Designing shareable collections without making users create an account