Dirt Bike Dialed

Every motocross rider tweaks their suspension. Clickers in, clickers out, sag measurements, spring rates — the variables are endless. And every rider tracks them the same way: napkins, Notes app screenshots, or pure memory.

The result is predictable. You find a setup that works, forget what you changed, can't reproduce it, and spend the next three ride days chasing the same feel. There's no structured way to log settings, compare across conditions, and build a history of what actually works for your bike and riding style.

Dirt Bike Dialed was designed as a purpose-built journal, not a generic notes app with a motorcycle skin. The data model mirrors how riders actually think about suspension: front and rear as separate systems, each with compression, rebound, and sag values.

The app needed to work at the track — meaning offline-first architecture was non-negotiable. Cell service at motocross tracks is unreliable at best. Everything saves locally and syncs when connectivity returns.

Flutter was the right call for cross-platform. One codebase, native performance on both iOS and Android, and the widget system made it fast to iterate on UI without sacrificing quality.

This app went through 27 development iterations before shipping. Not because the code was bad — because the UX had to feel right in a very specific context. You're standing next to your bike with dirty gloves, squinting at your phone in the sun. Every tap has to count.

The input flow was rewritten multiple times until logging a new setup took under 30 seconds. Comparison views were redesigned until the differences between two setups were immediately obvious at a glance.

This is what building for a community you belong to looks like. Troy rides motocross. The feedback loop wasn't user testing sessions — it was riding with the app and feeling what was wrong.

Dirt Bike Dialed shipped to the App Store as a polished, focused tool for a niche audience. It doesn't try to be everything — it does one thing well. Log your suspension settings, compare them, and stop guessing.

The 27-iteration journey is a feature, not a bug. It means every screen, every flow, and every interaction was refined through real use, not hypothetical user stories.