Why Kamoji works the way it does

Every significant feature decision in Kamoji has a reason behind it, and a few of them are the opposite of what you'd expect from a car gadget in 2026. Here's why they're built the way they are.

No touchscreen

This was decided early and never revisited. The reference point was cheap smartwatches with tiny touchscreens: imprecise, quick to pick up fingerprints, and a category that shows exactly why a touchscreen isn't always the right interface on a small device. Physical buttons are more reliable and more appropriate for something that lives in a car, where your attention should be on the road rather than on hitting a target on glass. It's also consistent with where automotive interiors are heading generally — manufacturers went from buttons to touchscreens and are now moving back toward physical controls.

Offline by default

There's a category of product that's essentially an open-source AI assistant in small-robot form — always-on cloud connectivity, voice recognition, the works. We looked at that category and decided against it: always-listening microphones raise real privacy questions, and depending on a cloud service means depending on its uptime, its latency, its API costs, and its continued existence. Kamoji is designed to be a fully standalone, offline experience — plug in power and it works, no WiFi setup, no account.

That doesn't rule the option out for people who want it. Kamoji's architecture is open-source and the hardware can support it — makers who want to build an AI assistant on top of the board can, and we've published a tutorial showing how: XiaoZhi on Kamoji: voice assistant firmware, end to end. We just don't think it should be the default for everyone.

The ferrofluid visualizer

Ferrofluid is a magnetic liquid that forms spikes and flows in response to sound and motion — a niche product most people have never encountered, because ferrofluid displays are expensive and rare. There isn't a digital ferrofluid simulation that does the effect justice, so Kamoji doesn't try to simulate the fluid itself. It uses a metaball simulation instead, which produces visually similar organic, flowing forms in real time on the display. Most people who see it won't know what they're looking at technically. That's fine — the effect is the point.

Takumi's Cup Challenge

The metaball work proved what the display could do with particle effects, which led to a full fluid simulation driven by the gyro sensor: the Cup of Water Test, run inside the device itself. We started with a flat water surface that tilted with the gyro reading, then kept pushing toward more realistic fluid behaviour — under one constraint throughout: the water had to look and behave like liquid and be fun to watch, not just physically accurate. Getting both at once took a lot of iteration.

G-force, without pretending to be a lab instrument

G-force sensors show up almost exclusively as factory-fitted systems in high-end vehicles — there's no real aftermarket accessory market for them. Kamoji has one, and it isn't lab-grade: the reading depends on where the device sits in the car, how it's oriented, and other variables that aren't controlled for. It doesn't need to be scientifically precise to be useful. It's accurate enough to compare meaningfully between vehicles and to show how a driving style changes the numbers on the same car — which is essentially what it's for. We expect owners to compare scores and argue about them.

OTA updates, without a mandatory app

Kamoji works fully without a phone, an app, or a cloud account. OTA firmware updates exist and reach every unit in the field, but they're opt-in, with no subscription attached. The OTA system itself isn't new: it's the same deployment infrastructure that already runs across hundreds of Originally US's own IoT installations, refined over more than a decade of keeping those systems running in production. That's an unusual decision for a mobile app company to make — an app that's genuinely optional — but it's the one that matches how Kamoji is supposed to work.

This is the fourth post in a series on how Kamoji got built. Next: learning industrial design from scratch, to get the helmet right.