SeaBear Studios — Ideas SeaBear Studios — iOS/macOS development, web applications, technology security, and GenAI consulting. 2026-05-19T00:00:00.000Z https://seabear.dev/ SeaBear Studios hello@seabear.dev The half-frame that became PersistentBackgroundNavigation https://seabear.dev/ideas/seabearkit-persistent-background-navigation/ 2026-05-19T00:00:00.000Z 2026-05-19T00:00:00.000Z A flicker I couldn't unsee in Tesserae's navigation, weeks of dead-end forum threads, and the structural fix that became SeaBearKit's first utility. There was a flicker in Tesserae I couldn't stop seeing. The root view had a color gradient with animated nodes drifting across the screen, slow and atmospheric. Every time I pushed a new view onto the NavigationStack, the gradient pulsed. Not for long. A single wrong-color half-frame as the transition logic recomputed the destination's chrome.

The user doesn't have words for it. They feel it.

I spent weeks chasing it. Every forum thread I found assumed the background was a property of the view, something you set with .background(...) and then chase around with modifiers when it misbehaves. I tried the modifier stack. I tried setting the background on the NavigationStack itself. I tried .toolbarBackground(.hidden). I tried Color.clear on every layer I could find. Each attempt moved the artifact somewhere else without removing it.

The breakthrough was changing the question. The background wasn't supposed to be inside the thing that's transitioning. The background is the room. The views are the furniture being rearranged. You don't repaint the walls when you move a chair.

Structurally, that meant pulling the background out of the navigation hierarchy entirely. The app gets a ZStack at the root, the background sits as one sibling, the NavigationStack sits as the other. Then .containerBackground(for: .navigation) { Color.clear } tells the navigation chrome to stop drawing its own surface on top. The background never participates in a transition because it never tears down. Push, pop, present, dismiss; the nodes keep drifting.

I called it PersistentBackgroundNavigation. It worked the moment I wired it into Tesserae.

Two things from this are worth recording.

The first is that Apple's SwiftUI conventions encode an assumption that views own their visual surface. That assumption is right most of the time, and it's why nobody writes a tutorial on hoisting the background out of the hierarchy. It's also why the workaround took weeks to find: the convention is loud and the structural alternative is quiet.

The second is that the fix didn't feel like mine. It felt like something other people would also want. I had reached for it because Tesserae has a particular contemplative mood that breaks if anything chrome-related flinches between screens. But a quiet animated background under a navigation stack is a recurring idea, not a personal one. So I lifted the relevant files into a SwiftUI package, wrote a one-liner API for it, and shipped it. That package is SeaBearKit, and PersistentBackgroundNavigation is still the first utility in the README.

Some of the best small libraries come out of refusing to live with an artifact nobody else is bothered by.

]]> Dot notation came from jq, not design https://seabear.dev/ideas/reverie-dot-notation/ 2026-05-18T00:00:00.000Z 2026-05-18T00:00:00.000Z Reverie uses dot notation because the original CodexCLI was bash + jq, and jq's path syntax is dots. The interface accreted from the implementation. The original CodexCLI was a bash script that read and wrote keys in a single JSON file. To do that, it needed jq. And jq's native path syntax for accessing nested data is dot notation: .server.production.ip.

So when a user typed ccli set server.production.ip 192.168.1.100, the script split the key on dots and built a jq expression. The dot notation was the cheapest possible adapter between user input and jq syntax. I could have used slashes or colons or any other separator, but I would have just translated them to dots inside the script. Skip the translation.

Now it's a CLI + MCP server in TypeScript with file-per-entry storage, and the dot notation stays. Partly muscle memory. Partly because every key in every store I've populated since then uses it. Partly because, looking back, it was the right answer all along, just for a different reason than the one I had.

]]>