META PERSPECTIVES

The Primitive Edge

Every component technology is primitive, yet the design of their combination produced a cutting-edge product. The absence of frameworks made dialogue with constraints possible.

The Bill of Materials Is Unremarkably Ordinary

Break down TokiQR's component technologies, and every one of them is either mature or an open specification.

No proprietary protocols. No servers. Every component is available to anyone.

Yet line up "30 seconds of voice in a single QR code," "built-in AI assistant," and "serverless permanent preservation," and it looks like nothing but a cutting-edge product. In reality, the design of the combination is the entirety of its uniqueness — the parts themselves hold no secrets.

The sense of being cutting-edge comes not from the novelty of individual technologies, but from the precision of their combination.

Without Knowing the Characteristics, You Never Get Here

Given the goal of "putting voice into a QR code," the natural first attempt is Opus or AAC. The natural conclusion: "it won't fit."

Testing Opus at 2–4 kbps reveals DTX spitting out silence frames. Entropy reaches 7.7, rendering DEFLATE useless. Only by actually hitting these walls and experiencing the limits firsthand did the option of Codec2 — designed for military communications — come into view. At 450 bps, it outputs 75 bytes per second. Robotic but intelligible. Up to roughly 29 seconds fit within QR Version 40's 2,953-byte ceiling.

The same applies to the Claude API. If all you want is "a chatbot," the choices are endless. But when you factor in compatibility with the serverless principle, the judgment that a stateless API call plus a Cloudflare Worker relay plus API key storage in localStorage would work — that judgment was possible only because the boundary conditions of each technology were already understood.

The more primitive the technology, the more its characteristics are exposed — and the more combination feasibility depends on understanding those characteristics.

What Frameworks Take Away

Frameworks increase the number of things you don't have to think about. At the same time, they increase the number of things you can't think about.

TokiQR has no React, no build tools. Just raw HTML, CSS, JavaScript, and WASM. That means every byte's destination is visible. The ability to design down to the single byte against the QR's 2,953-byte ceiling exists precisely because of this transparency.

Through a framework, you can see "why it works," but the cause of "why it doesn't work" gets buried under layers of abstraction. The calculation that Codec2's 450 bps yields 75 bytes per second, the overhead of Base64url — all of these could be pushed to their limits only because each one was directly accessible.

Conversely, had TokiQR been built on a framework, the very idea of embedding voice in a QR code might never have emerged. Abstraction is convenient, but it removes the opportunity to confront physical constraints. And if you can't confront constraints, you can't create within them.

Constraints Refine Design

This is a byproduct of the serverless principle. Because a complex infrastructure was off the table, only primitive technologies were available — and consequently, we had no choice but to find a combination of primitive technologies that could produce a cutting-edge result.

Heatmaps, onboarding tours, and CRMs were never adopted because they all presuppose server-side state. The AI assistant alone was viable because it completes within a stateless call. We didn't narrow the choices; the constraints narrowed them for us.

What high-level frameworks hide behind abstraction, low-level approaches force you to decide yourself. That is both a burden and a barrier to entry. The same parts are available to everyone, but not everyone arrives at the same combination.

Being primitive is not a weakness. A blade is sharpest when it is simple.