The trigger
Tuan and Tri are both full-stack developers. One day meant backend work, the next meant mobile, then a night of docs, RFCs, product teardown posts, design references, GitHub repos, blogs, and links dropped in chat.
The problem was not that we forgot to save. The problem was saving into too many places: Safari Reading List, Notes, Telegram, Zalo, Slack, browser bookmarks, Notion, GitHub stars, and a handful of tabs kept open because closing them felt dangerous.
At the end of one week in Ho Chi Minh City, both of us needed the same link we had once used to debug a sync issue. Both were sure it had been saved. Neither could find it. The first UniSave prototype started that night.
If an important link only exists in memory, it has not really been saved.
What we believe
Saving should be fast enough to keep your reading flow intact. One share action, a useful title, and a short reason when context matters.
Finding things again is the real job. A bookmark app should not only remember URLs; it should help you search by title, domain, tags, body text, or a vague memory like 'that post about offline queues'.
UniSave is built by people who use it every day. When a flow annoys us, it does not become a decorative backlog item; it becomes something to fix.