Flocci Notes: The Sticky Note That Plugs Into Your Whole Workspace

You have it in the shower. The clean, whole, obviously-correct idea — the fix to the thing that’s nagged you for a week, phrased so simply you can’t believe you missed it. You’ll remember this one. It’s too good to forget. Then the water shuts off, the towel, the kettle, the first Slack ping, and by the time you’re at your desk the idea has the texture of a dream: you know you had it, you know it mattered, and you cannot get it back. The best thought of your morning died in the ninety seconds it took to find a pen. This is the oldest problem in knowledge work, and it is entirely a problem of speed.

Capture has to be faster than forgetting

The whole genre of quick-capture apps exists to win that ninety-second race. Google Keep, Apple Notes, the back of your hand — all promise the same thing: a box so fast to reach the thought lands before it evaporates. For that one job they mostly work. You jot it; the idea is safe.

Then the second problem starts, and nobody warns you about it. The idea is safe, but it is also stranded — sitting in a note app that knows nothing about the rest of your working life. That shower-thought was a feature you now have to build, so you retype it into the ticket tracker. It was a decision the team needs, so you paste it into the wiki. It was three tasks in a trench coat, so you rewrite it as a checklist somewhere that isn’t the note. The capture was frictionless; the graduation is all friction. Every note app is an island, and the swim to where the idea actually needs to live is the part that quietly eats your afternoon.

First, it earns its keep as a note app

Strip away the platform tricks and Flocci Notes still has to be a good place to put a thought — and it is. A note is a title and a body you paint with a color, pin to the top, archive once it’s cooled, or send to the trash; you file it under labels defined once per organization, so your team’s taxonomy is shared rather than reinvented in every private head, and you can hang an image on it by URL. The checklist is where the humble card shows real spine: turn a note into one and every item becomes a row in a dedicated table with its own sort position and its own checked state — drag to reorder and it persists, tick a box and it’s still ticked tomorrow, on another device, on a teammate’s screen. Every edit rides out live over a ‘notes:changed’ broadcast, so a note in motion updates in front of you rather than on a poll interval.

And the card does one thing no ordinary note app does: a space picker promotes an outgrown jotting straight into the Flocci Library wiki as a real hierarchical page, minting a cross-link back that’s logged on the platform as an integration link of type ‘note’ — the first clue this isn’t really just a note app.

The trick: it was never just a note app

You’ve met the board, and it looks humble on purpose — a Google-Keep-style wall of color-coded cards. What’s underneath is the interesting part: this isn’t a standalone product at all. It’s one of five apps — Notes, the Library wiki, Projects kanban, Calendar, and the Infinity whiteboard — all served by a single Hono and Drizzle backend, sharing one login, one realtime core, and one AI layer.

That shared spine is what a four-table note app has no business affording on its own. Identity, the realtime core, the AI layer, and the platform’s Graph event bus were each built exactly once in the Hono core, so Notes — the smallest surface in the suite by a wide margin — stands on the same infrastructure as the video-calling Calendar and the infinite-canvas whiteboard. It hand-rolls no authentication, no websocket layer, no model integration; it inherits the versions four heavier apps depend on. The quick-capture box is the on-ramp; the platform holding it up is the destination.

From a jotting to a wiki page, without retyping

Here is the move that gives away what Flocci Notes really is. You’ve got a note that has outgrown itself — a spec, a decision record, a real document. In a normal note app this is where the copy-paste starts. Here, you promote it instead.

1. Jot it in the capture box

   Title and body, a color to code it, a label or two so it’s findable later. The idea is safe within seconds — the race against forgetting is won first.

2. Grow it in place

   Turn it into a checklist and drag the items into order, attach an image by URL, and let AI compose help you flesh out the prose.

3. Promote it to the Library

   When the note has earned it, a space picker sends it into the Flocci Library wiki as a structured, hierarchical page — and mints a bidirectional cross-link back, using the platform’s integration-link type ‘note’.

4. Keep the thread intact

   The note and the page stay connected — two ends of one live link, not two copies drifting out of sync.

That cross-link is the anti-island: capture flows into documentation without a single retype, and the two artifacts remember each other.

Alive, not local: what the shared core buys a humble app

Riding the same spine as its four siblings, Notes punches well above the weight of its interface. Three capabilities in particular would be genuinely hard to build into a standalone note app; here they come with the address.

None of it shows up as clutter; the board still looks like a board. But the note you type isn’t sitting in a local store waiting to be forgotten — it’s a live, org-scoped, AI-reachable, promotable object on a platform that knows what to do with it.

Who it’s for

Flocci Notes is for the person who already lives across several tools and is tired of their notes being the one thing that connects to none of them. If your day spans a task board, a wiki, a calendar, and a whiteboard, a separate note app with a separate login is a tax on every idea that needs to move. Here the note already lives in the same account, the same backend, and the same realtime spine as the rest of your work.

The on-ramp is the strategy

It would be easy to dismiss Flocci Notes as a Keep clone, and easy is exactly the disguise. The humblest surface in the Flocci Work Apps suite is also its cleverest positioning: the lowest-friction way onto a five-app platform is to hand someone a box they already know how to use, then quietly let a note they scribble become a wiki page, sync to a teammate, and get co-authored by a model — all because the hard infrastructure was built once and shared.

Per-note sharing is still on the roadmap and the platform is still maturing around Notes — honest gaps, named rather than hidden. But watch what a single capture can become here. A shower-thought lands in a color-coded card before the water’s even off; as the plan firms up it grows a checklist; when it outgrows the card it graduates into a shared Library page the whole team can edit; and somewhere down that thread it becomes the spec behind a shipped thing. The same idea the whole way — one unbroken link, no retype and no island in between. Capture that graduates is a better bargain than capture that merely survives.