Work · Garmin · Connect IQ
AllTrails for Garmin
Browse your AllTrails routes, lists, and nearby trails from your Garmin watch. I led the launch at AllTrails and built the app, largely solo.

AllTrails for Garmin brings the AllTrails app to Garmin watches and bike computers.
Pair your watch with a short code, then browse saved routes, lists, and nearby trails on your wrist. Download a trail directly, and Garmin’s navigation gets you from browse to trail faster, so you can start a route without switching devices.
It’s an AllTrails product, and I built it at work, largely solo and AI-first. It went live in the Connect IQ Store on October 29, 2026, on 120 Garmin devices in eleven languages.
Who it’s for
It’s for hikers who already wear a Garmin and plan their hikes on AllTrails. Instead of picking a trail on your phone and sending it over through a multi-step process, you can find one from the watch itself. Pairing needs a paid AllTrails membership and a linked Garmin Connect account with activity sharing on, so activities you record on the watch make it back to AllTrails.
Why I pitched it
I researched the idea and pitched it in July 2026. AllTrails could already send a route to a Garmin, and so could plenty of other apps, so I focused on putting the AllTrails content you’d want on your wrist: your favorites, your saved routes, and the maps you’ve made, plus nearby trails and more. In its first week, a prototype on a fēnix 8 went from browsing to downloading to Garmin’s native navigation. That made the payoff clear to company leadership, and from there I led the launch from start to finish: built the Garmin app itself, tech-led our server and web workstreams, and made most of the product calls that went into the launch MVP. I also project-managed aspects like coordinating marketing and legal to make sure the launch was a success.
How I built it
Almost everything ran through Claude Code sessions, and as with most AI-assisted work these days, the code itself was the cheap part. The work was making agent output trustworthy at speed, while keeping the project coherent across hundreds of short sessions. Each session read the same project rules and task board, took one task, verified it, and closed it out.
You can’t check a Garmin watch app by looking at one simulator. There are over 100 devices with different screen shapes, fonts, firmware, and memory, some with only 128 KB for the app. So I built a harness that lets an agent check its own work across all of them.
One tier renders key app states on every device and grades each frame for missing glyphs, clipped and truncated text, and blank screens. Another runs flow tests through the real view models and router, faking only the network, clock, location, and storage.
The agents worked under a rule that a build and unit tests are not enough, and before launch the harness showed why. A green menu theme doesn’t exist below API level 5, and it crashed the home menu on over 50 devices. Graphics.FONT_NUMBER_MILD has no letters, so the pairing code, which mixes letters and numbers, drew as empty boxes on more than half of them. Both compiled clean and passed every unit test.
Reading screens, not lines
With agents writing most of the code, I reviewed what the app did on screen rather than reading every diff. A contact sheet put every state on every device in one grid, filterable by device and screen, and a before-and-after gallery showed what each change moved. That let me review flows and architecture rather than lines.
The cost is that a bug with no visible symptom can get past me. So each change also went to a fresh-context agent that saw only the diff and its evidence, never the plan, since an agent that knows the intended story tends to confirm it.
Some trade-offs
At launch, it hands you off to Garmin’s navigation rather than drawing its own map, and it needs a paid membership and a linked Garmin Connect account to pair. It was also built mostly by one engineer, so I spent the last stretch making sure I wasn’t the only one who knew how it worked. That meant a store submission runbook, an on-call guide, and a support guide captured from the production build with each release.
I wrote up the build in more detail in From zero Garmin experience to shipping our MVP in a month.