Prototype 2025: PatchJournal v3 — iOS Companion App

PatchJournal v3 is the third version of the iOS companion app for the Moog DFAM — expanded this time to cover the full setup: DFAM, Subharmonicon, Arturia Minibrute 2, and a Korg alongside it. Where the second version reached full release, this one went further in the development process than either previous version before it stopped. The first version proved the AR concept. The second version proved the full pipeline. This one ran into something different.

The Lizard Brain

Seth Godin calls it the lizard brain — the primitive, pre-rational part of the mind that resists finishing. It does not object with reasons. It does not explain itself. It just applies friction, quietly, until the project slows and eventually stops. I had read Linchpin. I knew the term. I could name the mechanism. And I still stopped. That is the part worth sitting with: awareness of the pattern does not automatically dissolve it. The development was progressing. The design work was good. The lizard brain won anyway.

Expanded Instrument Coverage

The scope had grown significantly from the previous versions. Where v2 covered the DFAM exclusively, v3 set out to document every parameter across the full instrument setup — multiple synthesizers, each with their own patch routing, knob positions, and switch states. The AR layer was retained, now calibrated to identify and overlay multiple hardware panels in the same shot. Designing for a mixed-signal setup introduced questions that a single-instrument app never has to answer.

The Pivot

What came out of stopping was a redirect. The energy went toward a DAW plugin instead — a direction that felt more contained, more immediately connected to the production workflow, and less dependent on the iOS review pipeline. Whether that was genuine instinct or a rationalisation the lizard brain fed me, the pivot produced something real. The plugin work is documented separately.

PatchJournal v3 is unshipped. The design is documented here. The decision to stop is documented here too — not as failure, but as a data point. Every version of this app has clarified something different about the distance between a working prototype and a finished product.