Flow records what your desktop was doing and puts the day you planned next to the day you had — including the parts you would not have written down.
No account. No server. Your data stays on your devices.
The waitlist opens shortly. Until then the build runs in public on X, and questions go through the contact form.
Tuesday · a real working day
Planned
Actual
091011121314151617
Focused 4h 45m
Off plan 1h 15m
Unaccounted 1h 15m
Context switches 27
Deep work 4h 45m
Meetings & mail 1h 15m
Off plan 1h 15m
Unknown 1h 15m
Largest single block 1h 50m
Off plan, in 6 pieces 1h 15m
Context switches per hour
2
3
7
2
1
2
6
3
1
091011121314151617
Switches 27
Both peaks while waiting on a build 11:00 · 15:00
Local-first
The recording never leaves the machine.
There is no account to create and no server to trust, because there is no server. Flow writes to a local database you can open, copy, or delete.
Sync between your own devices runs directly between them — encrypted, opt-in, and off by default.
StorageSQLite, on disk
AccountNone
TelemetryNone
ExportYours, any time
Planned vs actual
The gap is the product.
Most trackers hand you a pie chart of categories and let you feel productive. Flow leads with the distance between what you meant to do and what happened — and with the hours it cannot account for at all.
When it ships
Price TBD
Desktop and phone in one price. Pricing is not settled yet — the waitlist decides who gets the first build.
Design principle
No score. No streak. Nothing turns red because you had a bad day.
A tool that grades you gets closed after a week. Flow never rates the person — it makes the structure of the day impossible to argue with, and leaves the conclusion to you. Time it cannot identify stays labelled unknown rather than being guessed into a category.
Away
Knows when you left.
Idle time is not counted as work, and not silently dropped either.
Off screen
Life that has no window.
Calls, errands, a nap. Add them after the fact in two clicks.
Second screen
Your phone counts too.
The scrolling that happens while a build runs is part of the day.
Footprint
Rust, not a browser.
A tool that runs all day has no business eating 250 MB.
The studio
RiD builds tools that hand time back.
Three worlds, one idea: games that enrich the small gaps in a day instead of mining them, organisation that actually saves time, and health that leaves you comfortable in your own body. Every RiD tool is built for its own maker first — what annoys, goes.
rid of the clutter — less weight between you and the better version of yourself.
OrderFlow · in development
OrderTask manager · built, renaming
PlayBrowser game · in concept
Build log
Built in the open, week by week.
Intention layer: focus blocks, planned against actual