Building Nave
Threads began as automatic grouping. Too shallow — they are the line from an idea to what got built.
-
Threads are just automatic grouping
-
Grouping by topic is too shallow
-
A thread must understand context, not words
-
A thread has a direction, not just a name
-
A thread runs from idea to what got built
Notes
2 thoughts today, woven into Building Nave.
Spaces
Threads
Building Nave
Landing page for the app
Pricing the encoder by the hour
Moving the docs off Notion
A second iOS engineer
Cutting onboarding to one screen
Widget for the lock screen
Actions
Drop the v3 config once the classes are ported
Move the landing styles to Tailwind v4
Make the hero fit a 900pt window
The hero has to fit one screen
Close a thread on the note that ships
A thread runs from idea to what got built
Show the trajectory, dated, before the notes
A thread has a direction, not just a name
See how your
thinking changed.
A local-first notes app for iPhone. Capture a thought and Nave writes the title and the summary, files it into the right thread on its own, and lifts out what you said you would do.
Say it once.
Get it back readable.
One tap, by voice or by keyboard. Your words are on the device before anything else runs — saving never waits for a network. Then Nave writes a title, a one-line summary and the key points, and keeps it all as a plain Markdown file in your own iCloud Drive folder: readable without Nave, and yours to move or delete.
Work and home
never mix.
A space is a separate vault: its own notes, its own threads, its own colour, and its own model if you want one. Switch space and the whole app switches with it, so a note about the release never lands beside a note about your weekend.
You never file a note.
The thread forms itself.
When two notes turn out to answer the same question, Nave opens a thread and names it. Nothing to tag and nothing to sort — and because the thread keeps the order and the dates, you can watch a position change.
Nothing you promised
stays buried in a note.
Every commitment inside a note becomes an action, without you marking anything up. Say a time out loud and Nave reads it out of the sentence, then offers to put it in Reminders — or writes it there itself, if you set it to.
What you said
I need to get the landing off Tailwind v3. In v4 the config lives in CSS, so tailwind.config.js goes away entirely, and a good half of the class names changed on top of that — it is a port, not a version bump. Do it before I write any more of the page.
What came back
Voice · 1:42 · 12 Aug
Move the landing styles to Tailwind v4
The config moves into CSS and tailwind.config.js goes away — and the class names changed, so this is a port.
Key points
- In v4 the config is CSS; the config file disappears.
- Half the class names changed — budget a port, not a bump.
Calendar
The month you actually had.
Every day you captured on is marked, so a fortnight you cannot account for has a shape. Tap a day and what you thought on it comes back — in order, with the threads it went into.
August
Threads
Building Nave
-
Threads are just automatic grouping
-
Grouping by topic is too shallow
-
A thread must understand context, not words
-
A thread has a direction, not just a name
-
A thread runs from idea to what got built
Five notes about one feature, three weeks apart. Nave put them on one line, and read in order they show the exact moment the idea turned over.
Nave is almost here.
A local-first notes app for iPhone, built for one thing: keeping the line of your thinking, without asking you to keep it.
Your notes stay in your own iCloud folder, and Apple Intelligence reads them on the device. Bring your own model and key if you would rather. Either way, there is no Nave server in between.