Flocci Recall: The Bookmark Graveyard Finally Has an Exit
Recall inverts the bookmarking bargain — save anything in one tap, then find it by describing what you half-remember instead of where you filed it.
On this page
You saved it. You are certain you saved it. The thread about database indexing strategies, or the YouTube explainer with the perfect diagram, or the offhand note you typed to yourself at a red light — it exists, somewhere, in one of the six apps you use to save things. And it is gone. Not deleted: unfindable, which is worse, because the failure is now yours. You didn’t remember the exact title, you don’t recall which folder, the tag you’d have used doesn’t match the tag you actually used eight months ago. This is the bookmark graveyard, and almost everyone who works with information lives on top of one.
The bargain every bookmarking app makes with you
Every read-later and bookmarking tool ever built asks the same two favors, and it asks them at the two worst possible moments.
The first favor is at save time: file this correctly, now. Pick a folder. Add tags. Decide, in the half-second before the tab closes, which future version of you will come looking and what words that person will use. The second favor is at retrieval time: remember exactly what you saved, and where. Reconstruct the title. Recall the tag. Navigate the folder tree you built when you were a different person with different priorities.
Both favors are asked when you have the least capacity to grant them — mid-task on the way in, and mid-panic on the way out. So the honest outcome is the one everyone actually lives: most saved content is never seen again. The library becomes a landfill you keep paying rent on.
Flocci Recall’s entire thesis is that this bargain is backwards. You should be allowed to save carelessly and search vaguely — because careless saving and vague searching are the only kinds of saving and searching humans reliably do.
Recall doesn’t ask you to file neatly now and remember exactly later. It lets you describe what you half-remember, reconstructs the meaning, and hands back a plain-English account of what it found — with every item already boiled down to its point. It’s less a save-list, more a memory you can talk to.
Capture that never makes you think
The way you kill the filing chore is to make saving cost nothing — not one tap of thought, not one moment of hesitation. Recall funnels everything through a single endpoint shaped like a native share ({url?, text?, title?}), and that endpoint is deliberately promiscuous about what it swallows.
Paste a bare thought and it becomes a note. Share a messy block of text with a link buried inside and it extracts the URL. Hand it a direct image link and it files an image. You never declare a type; the system classifies. On Android it registers as a proper share target, so Recall appears right in the native share sheet next to the apps you already use. There’s a /save deep link for everything else.
And here is the detail that separates a real capture tool from a demo: saving never waits on the AI. If the intelligence service is slow, off, or down, a heuristic fallback catches the save instantly, and the smart enrichment catches up afterward. The one thing a memory app can never do is drop your memory on the floor because a model was busy. Recall is built so that the save always lands.
Retrieval that meets you where your memory actually is
If capture is where filing dies, search is where the whole idea earns its name. Type what you remember — not keywords, a description. “That piece about why remote teams over-communicate.” Recall’s AI interprets that into underlying concepts and uses them as soft boosts on your library, never as hard filters.
That distinction is the entire game. A keyword filter that finds nothing returns nothing, and you’re back in the graveyard, now blaming your own phrasing. A soft boost can’t strand you: the closest-in-meaning item floats up even when not one of your words matches the save. The explicit chips you tap only ever narrow — and the type chips use union semantics, so multi-select adds options rather than colliding them. The fuzzy-first behavior stays honest all the way down.
Then Recall does the thing that turns a search box into a collaborator. Above every result set sits a one-sentence narration — what it found and why it thinks it fits. And on a miss, instead of a blank page and a shrug, it proposes a concrete better angle to try. The tool takes responsibility for the empty result instead of handing it back to you as a personal failing.
Your fuzzy query becomes concepts that lift the most relevant saves to the top — never a rigid filter that returns nothing. A half-remembered description is enough to surface the right item.
A one-sentence account rides above every result set explaining what surfaced and why. Miss on a query and it hands you a sharper angle to try, not an empty page.
Every item carries a 3–5 point digest, shown on the card and as a numbered “Key takeaways” block in detail — so you read the library without reopening the source.
One endpoint swallows links, shared text, and pure notes, classifies them on the way in, and never blocks on AI — a heuristic fallback means the save always lands instantly.
Notice what the takeaways digest quietly eliminates: the second chore. Even people with a tidy library still have to reopen each result to remember why it mattered. Recall reads every item when you save it and keeps the gist attached, so scanning results is often the whole job. You rarely reopen the source, because Recall already did.
The iPhone problem, solved the hard-but-honest way
Here’s a real-world wall most “save from anywhere” pitches quietly walk into: iOS does not admit progressive web apps to its native share sheet. No amount of clever web code fixes that — it’s a platform door that simply doesn’t open.
So Recall doesn’t pretend. It ships a signed “Save to Recall” Apple Shortcut that posts your content to the same capture endpoint using a per-user capture key (an rcl_… token). The key is honored only when there’s no session cookie, and an unknown key fails loudly with a 401 rather than silently swallowing your save into nowhere. It’s not the prettiest path — it’s the honest one, and it’s the difference between “works on iPhone” as a slide and as a fact.
- Grab it from anywhere
Hit the OS share sheet — Android’s native share target, the iOS Apple Shortcut, or the /save deep link. Link, highlighted text, or a bare note: all the same one endpoint.
- It files itself, instantly
The save lands immediately on a heuristic classification, then AI enrichment fills in the digest and understanding in the background. Nothing waits on a model.
- Later, describe it back
Search in plain language. Concepts boost the closest matches, a narration tells you what surfaced and why, and if you missed, Recall proposes a better angle.
- Read without reopening
Scan the key-takeaways digests on the cards. More often than not, the point you saved it for is right there — no round-trip to the original tab.
More than a private pile
A memory worth keeping is a memory worth sharing and protecting, and Recall treats both as first-class rather than afterthoughts. Collections aren’t static folders — they carry link invites, roles, comments, and an activity feed, so saved content becomes a collaborative surface a team can actually work on together. On the other end of the spectrum, a Vault puts a PIN screen-lock, privacy rules, and purge-or-regenerate-understanding controls around sensitive items. Resurface pulls saves back into view before they fossilize. And exports for items, links, and context mean the library is portable, not a hostage.
Portability isn’t a marketing checkbox here; it falls out of an unusually simple architecture. The whole library lives in memory and persists as a single JSONB row, debounced and flippable between a local database and a hosted one. When your entire second brain is one clean structure, getting it back out is trivial by construction.
The mobile experience is engineered with the same seriousness. On phones the layout structurally re-branches rather than merely shrinking: a compact appbar replaces the desktop hero, the Library shows a one-row search plus real items in the very first screenful, and saving lives in a floating button and a bottom sheet. It reads as a mobile-first shell, not a desktop page squeezed through a phone.
Do
- Save carelessly — a bare note, a messy paste, a link with no context. Recall sorts it out.
- Search the way you actually remember: describe the vibe of the thing, not its exact title.
- Trust the takeaways digest to answer “why did I save this?” before you reopen anything.
- Lean on the fuzzy-first behavior; let the narration tell you whether it nailed it.
Don't
- Build an elaborate folder tree at save time — the filing chore is the thing Recall deletes.
- Assume a no-match search failed you; read the suggested better angle first.
- Treat it as write-only storage. The whole point is that things come back.
- Worry that an AI outage ate your save — capture always lands on heuristics.
Recall rides shared Flocci rails, not its own silo
Recall doesn’t reinvent the plumbing every SaaS product reinvents. It signs users in through the shared Flocci identity service — Google SSO mediated centrally, with no per-app OAuth client of its own — and links accounts by email so one person maps to one user. It runs all of its AI through the shared Flocci intelligence gateway on DeepSeek, holding no model SDK or keys itself, under three named feature keys: capture.enrich, search.interpret, and search.narrate. When AI is off or the service is down, every one of them degrades to heuristics.
And it publishes activity to the platform-wide Graph event mesh so capture, opens, and searches can feed cross-app intelligence — but with a privacy line drawn in indelible ink. Search events carry counts only; the text of your queries never enters the Graph. Envelopes are marked as containing no personal information, benchmarks are disallowed, and user references are hashed rather than sent raw. Here, respect for the user lives in the wire format itself, not in the marketing copy.
This is early in the most honest sense. Today the AI calls run without per-user billing or metering wired in, and notifications and payments aren’t used yet — the stated next step is to thread the identity user through intelligence and the Graph to unlock per-user attribution and pricing. That’s a foundation being laid deliberately, not a gap being papered over.
The pitch, though, is already complete where it counts. Recall doesn’t promise to make you more organized. It promises the opposite — that you can stay as disorganized as you actually are, save on impulse, search on a hunch, and still get the thing back, already read, already reduced to its point. And once that works, the old habit quietly flips for good: describing what you half-remember stops being the fallback and becomes the natural way you find things — the day recalling meaning finally beats remembering where you filed it.
Frequently asked questions
What is Flocci Recall?
A universal content-memory app. You save any link, shared text, or plain note from anywhere, then find it later by describing what you half-remember rather than recalling exactly where you filed it. Its AI narrates what each search found and digests every saved item into a few key takeaways, so you can read your library without reopening the sources.
How is it different from bookmarks or read-later apps like Pocket?
Bookmarking tools make you file things by folder or tag, then remember precisely what you saved. Recall flips that: capture is one tap with no filing required, and retrieval is meaning-first — the AI turns a fuzzy description into concept boosts, never rigid filters, so you get the right item instead of an empty result. And every result explains itself with a one-sentence narration plus key takeaways, so you often never open the original at all.
Can I save things from my phone, including an iPhone?
Yes. On Android it registers as a share target, so it shows up in the native share sheet, and there is a deep link for saving. iOS never lets PWAs into its share sheet, so Recall ships a signed 'Save to Recall' Apple Shortcut that sends content in using a personal capture key. There are also Android and iOS apps built from the same web app via Capacitor shells.
Is my data private?
Privacy is built into how usage is reported. Analytics events sent to the wider Flocci platform carry counts only — the text of your searches never leaves the app into the event mesh — and those events are hashed and marked as containing no personal information. There is also a Vault with a PIN screen-lock and privacy rules for sensitive items, plus controls to purge or regenerate an item's AI understanding.
What happens if the AI is unavailable?
Saving never breaks. Capture is designed to never block on AI: if the intelligence service is off or down, it falls back to fast heuristics so your save still succeeds instantly, and enrichment can catch up later. Search and narration degrade gracefully to heuristic behavior too, so the app stays usable.
/* Comments */
Comments are offline right now — we reconnect automatically, nothing is lost.