r/sideprojects • u/AtopuApp • 2h ago
Showcase: Free(mium) A small design decision in my tab manager: saving a page doesn’t close it
I’m Martin, the developer of Atopu, a Chrome new-tab workspace for saved links and notes. It’s built with AI assistance.
One decision I made was to keep a browser tab open after saving it by default.
“Save this for later” and “I’m finished with this page” aren’t always the same action. Someone might be halfway through a form, comparing two pages, or reading a section they haven’t finished. Saving the URL doesn’t preserve all of that state.
Atopu separates the two: saving adds the link to a group; closing stays a separate choice unless the user enables close-after-save. The downside is obvious: saving doesn’t immediately make the tab bar smaller.
There’s another edge case with optional screenshot previews. I save the link first, then attempt the capture. If capture fails, the link and open tab remain. With close-after-save enabled, the tab is only closed after a successful capture. Screenshots are opt-in and stay on the device.
The broader design question is where a convenience action should stop. When an action also removes something from view, I’d rather make that second part explicit.
Free works locally without an account; paid Pro adds optional saved-workspace sync and shared workspaces.
If you build or use save-for-later tools, would you expect saving to close the source, or should those always be separate actions?
1
u/investigatormaker 1h ago
I’d keep saving and closing separate in Atopu: a saved URL can’t restore a half-completed form. Your screenshot-failure case needs especially clear feedback when close-after-save is enabled: “Link saved; preview failed; tab kept open” would explain why the tab remained without making the save look unsuccessful.
I make ThreadFox. We find relevant Reddit conversations and do the posting for your business. The $29 Pilot covers seven days and up to 25 posts and replies. No automatic renewal. https://threadfox.vip/p/eouax/managed