What changed
Every update from every project, merged and sorted by date. The same entries live on each project's own page — this is the view across all of them.
September 20266 entries
1.5: easier to find your way
A smaller round of polish. My Verses has a search once the list grows, and each Library group shows how many you've already added. How it works is six short sections you tap to open, instead of one long page. While you add or edit a verse, Save stays at the bottom of the screen.
1.4: easier to start, calmer to use
Watching a first visit screen by screen showed how much a newcomer had to work out alone. Adding a Library verse meant a long form. The Library hid each verse behind a tap, so you chose from notes. And the grades never said what they did.
Now one tap adds a verse, and its button becomes "Memorize now". Your very first verse gets a guided pass through the four steps, and afterwards Today tells you when it comes back. Each grade button says what happens next: "Back in 2 days", "Back tomorrow", "Start over".
The memorize screen is quieter: a thin progress bar, a larger verse, and one button at the bottom under your thumb. Today is a proper home: what's due and about how long it takes, what you're still learning, and one verse to add next.
It also has a new look, taken from the app icon: cream paper, deep blue and gold, with a book serif for Scripture. It's still all system fonts, and it still makes zero network requests.
1.3: install it, or carry it away
Until now "works offline" came with a catch: you still had to reach one of our websites to open it. On a computer you could save the page as a file, but on an iPhone there was no real way to keep a copy at all.
Now it installs as an app: Add to Home Screen on iPhone, or Install on Android and in Chrome or Edge on a computer. A small service worker keeps the tool's own files on the device, so the app opens with no connection, and it keeps working if this site is ever down or blocked. It only ever fetches its own files from its own site, and it sends nothing about you.
There's also a "Save this tool" button, which writes the whole tool out as one file to keep or pass along. It's the same file, byte for byte, and it opens in any browser.
Along the way, testing caught a bug I'd never have seen from a desk: the site serving the other copy forbids pages from making any request at all, and a service worker obeys the policy on its own script. So it couldn't even cache itself. One file now has a narrower rule of its own.
1.1: backups that happen by themselves
Browser storage is the tool's working copy, and some browsers clear a site's storage after a week or two away. Safari does this to sites you haven't visited in about seven days, and it can take months of review history with it.
So there are now three layers. The backup reminder comes sooner, and only when something has actually changed. On a computer, you can choose a sync folder, ideally inside Google Drive, OneDrive or Dropbox. A backup lands there after every change, and changes from your other devices are picked up whenever the page opens. On a phone, "Send a backup file" opens the share sheet, so a backup can go into that same folder in two taps.
It still makes no network requests. Your cloud drive's own app does the carrying, which is why this works even on a site whose security policy forbids the page from talking to any server at all.
1.0: memorize, review, and say it to Him
The first release. Add verses in any translation, file them under categories that work as tags, and learn them on a four-step ladder: Read, Fade, First letters, Recall. Typing is optional. Recall is self-graded, and an optional typed check marks the words you missed.
Review uses Leitner boxes (1, 2, 4, 7, 14, 30, 60 and 120 days). There are no streaks to break.
The part I care about most is the order of the Library. Most memory systems are built around what God does for us, and this one opens on who He is. When you recall a To the Lord verse, a quiet "Now say it to Him" follows. It never rewrites the verse, and nothing about it is recorded.
The only Scripture it ships is checked twice
The tool includes text only for its recommended verses: public-domain BSB and KJV, extracted by a script from pinned eBible.org files, never typed by hand. Every verse is compared word for word against a second, independent export of the same translation, so a parser bug can't quietly change a word.
July 20265 entries
· Grove
Folder sync, and the limits of browser storage
Maps living in the browser is fine right up until it isn't. Clear the wrong setting, use a different machine, and they're gone — and "back up your data" is advice nobody follows.
Chrome and Edge on desktop can now write each map straight into a folder you choose. Point it at a folder inside a cloud drive you already pay for and two machines share the same maps, with no Grove server in the middle and no account anywhere. Safari and most phones can't do this, and Grove says so plainly rather than pretending it worked.
There's also an auto-backup that drops a dated copy in Downloads when you finish editing, for everyone who doesn't have folder sync.
· Grove
Proving the API key never leaks
Your Anthropic key is the one thing in Grove that could genuinely cost you money, and Grove writes a lot of files — exports, backups,
.jsonmaps, PNGs.So there's now a test that fails the build if the key appears in any of them. Not a code review promise, an actual gate. It felt like overkill until I remembered that the whole pitch is "your thoughts never leave your device," and a key leaking through a backup file would make that a lie.
· Grove
AI that proposes and never writes
Three AI actions shipped: Sort my thoughts groups the tray under branches, Go deeper suggests sub-ideas, and Ask me questions plays Socrates and turns your answers into nodes.
None of them touch the map directly. Sort produces an editable preview where you can rename a proposed branch, move a thought to a different group, or throw the group away. Go deeper produces dashed ghost buds you keep or dismiss individually. Ask me questions only ever adds the words you typed yourself.
The rule underneath all three: your words are never reworded. When the AI proposes a new branch title it's a suggestion in your vocabulary, and when it files your thought it files it verbatim. Getting that right meant rejecting a few designs that would have been slicker.
· Grove
Capture first, file later
Rebuilt the whole map screen around a tray at the bottom. Type a thought, press Enter, it lands in the tray. File it onto a branch now or in a week.
This came from watching myself not use my own tool. The blocker was never typing — it was that typing required first deciding where the thought went, and by the time I'd decided I'd lost it.
Also added the outline view, which is the better way to read a map on a phone, and made the Map ⇄ Outline toggle keep your place.
· Grove
One file, no server, no account
Started from the constraint instead of the feature list: everything has to fit in a single HTML file you could email to yourself.
That kills a lot of ideas early, which is the point. No accounts, because there's no server to hold them. No sync, at least not yet, because there's nothing to sync through. No analytics, because there's no way to send them.
What's left is a mind map that opens instantly and works on a plane.