The route is the story: what a niche outdoor video tool taught me about the next wave of creator software
Every social media operator I know is drowning in the same problem, and it has nothing to do with posting frequency. It’s the gap between the raw material a creator captures and the finished asset that actually performs. You shoot 400 clips on a trip, a hike, a shoot day, a conference — and then you spend six hours in an editor trying to turn a pile of files into something a human will watch past three seconds. The tools that win the next two years won’t be the ones that help you post more. They’ll be the ones that help you finish faster from material you already have. That’s why How It Went, a small indie app that builds a film from a GPS route, is worth your attention even if you never touch a bike. The pattern it’s selling — automate the assembly, keep the human judgment — is exactly the pattern serious social teams should be stealing. Herbert Poul built it for bikepacking, but the lesson is platform-agnostic.
What How It Went actually does, and the problem it’s really solving
Strip away the outdoor framing and How It Went is an assembly engine. You feed it a GPS track plus your photos and clips, and it generates a finished short film: the route draws itself across a tilted map, each photo appears at the location where you shot it, and video clips play at their capture points. Distance, elevation gain, and the mountain passes you crossed get pulled in as captions automatically. The maker’s own framing, from the launch thread, is that a slideshow “loses the days I care about most, the long ones where I was too tired to stop for pictures” — the track is the one artifact that recorded every hour, so the film is built from the route rather than from the highlights.
That’s a genuinely different mental model from CapCut or Canva, where you start with a timeline and drag clips onto it. Here you start with metadata — a GPX file — and the timeline assembles itself. The maker calls out two engineering problems that are worth understanding because they’re the same problems any creator tool faces: first, camera clocks. An action cam that was never set to local time puts your lunch stop in the wrong valley, so the app lets you fix the clock once per camera and every shot from it shifts together. Second, rendering happens on-device — Flutter paints every frame offscreen and hands it to the platform’s own encoder (AVAssetWriter on Apple, MediaCodec on Android) — so the film is ready the evening you get home rather than queued on a server.
The whole film is free on iPhone, iPad, Mac, and Android, from your own files, at every export size. Version 2.0.0 shipped with a Premium tier on top: five more map looks, a photos-first layout, a soundtrack style you pick, and an opening on a photo or clip of your own. Pricing is pay-once or yearly, with a one-week free trial — the exact figures are not disclosed on the page. There’s also a launch promo: the code PRODUCTHUNT gives Premium for life, free, until October 31 or until 99 people redeem it, at my.howitwent.app/redeem. One commenter, ivor cruz, reported the link wasn’t working a couple of hours in — a reminder that launch-day redemption flows are exactly where indie products break.
Why this matters more to a TikTok or Reels creator than to a LinkedIn one
Here’s the operational reality: short-form video platforms reward watch time and completion rate, and the single biggest lever on completion is whether the first two seconds promise a payoff. A route-drawing animation is a built-in hook — motion, geography, a sense of progress. A LinkedIn carousel of the same trip gets a polite scroll. If you’re publishing to TikTok or Instagram Reels, an auto-assembled geographic narrative is closer to a native format than a static photo dump will ever be. On LinkedIn, the same asset works as a “here’s what I learned on the trail” post, but the video is doing emotional labor, not algorithmic labor. Know which one you’re buying.
How it differs from the tools you already pay for
The honest comparison set isn’t video editors — it’s the whole repurposing-and-scheduling stack that social teams live in. Buffer, Hootsuite, Later, and Metricool all solve distribution: they get your finished asset onto the right platform at the right time, with analytics and UTM tracking layered on top. None of them help you make the asset. CapCut and Descript help you make it, but they’re timeline-first — you still do the assembly by hand. How It Went sits in a third category: metadata-driven generation, where the structure of the output is determined by data you already collected rather than by editing decisions.
That’s a narrower wedge than it sounds, and that’s the point. The maker explicitly says it was built for riding and the on-screen words still say “ridden,” inviting hikers, skiers, and paddlers to try it. That’s a product with a sharp initial user, not a general-purpose editor. For a social operator, the takeaway isn’t “switch your editor.” It’s that the highest-leverage automation is domain-specific: if your content has a repeatable structure — a workout, a recipe, a product teardown, a travel day — someone will (or already does) build the assembler for it. The generic timeline editor is the thing that gets commoditized, not the judgment about what to include.
Where the math breaks
Auto-assembly is only as good as the metadata. If your GPS track is patchy, or your camera clocks are wrong and you don’t fix them, the film places your content in the wrong place — and a geography-driven video with wrong geography is worse than no video. The maker flags the clock problem directly, which tells you it’s the failure mode users hit first. In my experience with any tool that auto-generates from captured data, the first ten minutes of setup (syncing clocks, confirming the track imported cleanly) determine whether the output is usable or embarrassing. Budget for that, not for the render.
What creators and social teams should borrow from this
Three operational lessons, and I’d argue the third is the most valuable.
One: build your own “route.” Every repeatable content format has a spine — a data source or structure that determines the sequence. For a fitness creator it’s a workout log. For a food creator it’s a recipe step list. For a SaaS founder it’s a changelog or a support-ticket theme. If you can name your spine, you can template the assembly, and templating assembly is how you go from two posts a week to ten without hiring. This is the same logic behind repurposing workflows: shoot once, cut the same footage into a long-form YouTube edit, three Reels, and a carousel — the YouTube long-form is the source of truth, the shorts are derivatives. How It Went just makes the derivation literal.
Two: on-device rendering is a feature, not a detail. The maker chose to render on the phone or Mac rather than on a server so the film is ready the evening you get in. For a creator on a deadline — a same-day event recap, a live-trip post — server-queue latency is the difference between posting while the moment is hot and posting two days late when the algorithm has already moved on. When you evaluate any AI video tool, ask where the render happens. Cloud rendering means upload time, queue time, and a dependency on someone else’s GPU availability. I’d bet on-device (or at least local-first) rendering becoming a selling point across the category, the same way offline editing did.
Three: the free tier is the distribution strategy. The whole film is free at every export size; Premium adds map looks, a photos-first layout, a soundtrack style, and a custom opening. That’s a smart split — the output is free, the polish is paid. If you’re building or buying creator tools, watch this line. Charging for export is a growth killer; charging for aesthetic differentiation is a moat. Whether it holds up commercially is another question, and one the page doesn’t answer.
The scheduling piece nobody talks about
Notice what How It Went doesn’t do: it doesn’t post for you. There’s no scheduling, no cross-posting, no analytics dashboard. That’s a deliberate boundary, and it’s the right one for a small team. The temptation for every creator tool is to bolt on a scheduler and become a platform. But Buffer and Later already own that layer, and API rate limits on every major platform make scheduling a full-time engineering job on its own. The smarter play — and the one I’d recommend to any indie founder reading this — is to own one step of the workflow completely and let the schedulers handle distribution. A finished film exported to your camera roll is a perfectly good handoff. Don’t build the pipe if someone else already laid it.
Where my judgment says it falls short
Let me be blunt about the limitations, because the launch page won’t be.
The addressable audience is narrow by design. The maker says the on-screen words still say “ridden.” That’s charming and honest, but it’s also a conversion problem: a hiker who downloads it and sees “ridden” on their summit film will bounce. The invitation to hikers, skiers, and paddlers is a request for feedback, not a shipped feature. If you’re not doing a distance-based outdoor activity with a GPS track, this isn’t your tool yet — and I’d want to see a roadmap before betting a workflow on it.
A GPS track is a hard dependency, and the page is ambiguous about alternatives. One commenter, Adam Petritsis, asked directly whether a GPS track is required or whether the film can be built from iPhone photo locations alone. As of the scrape, there’s no maker reply. That’s the single most important open question for anyone outside the bikepacking niche: if you can build from photo EXIF geodata, the addressable use case widens enormously — travel, events, weddings, real estate. If you can’t, it stays a niche outdoor tool. I’d test this first.
The launch mechanics have friction. The PRODUCTHUNT lifetime-Premium code is capped at 99 redemptions and expires October 31, and at least one commenter reported the redemption link down within hours. For a pay-once-or-yearly product, a broken promo link on launch day is a real conversion leak. It’s also a useful reminder for anyone running their own launch: test the redemption flow on a clean device before you hit publish.
The social-sharing piece is aspirational. abhishek jain commented that the output “can be more appealing, and sharable to social media like Insta, TikTok etc.” — note the “can be.” The app exports video; it doesn’t format for each platform’s aspect ratios or hook conventions. You’ll still be doing the 9:16 crop and the caption work yourself. That’s fine, but don’t buy it expecting a publish button.
Pricing transparency is incomplete. Pay-once or yearly, one-week trial — but the actual numbers aren’t on the page. For a tool competing against free tiers of CapCut and Canva, the price point matters enormously, and I can’t evaluate the value proposition without it.
What I’d watch / test next
If you run social for a brand or you’re an indie creator, here’s what I’d actually do this week — not with this app specifically, but with the pattern it represents.
First, audit your own “route.” Open your last five posts and ask: was there a data source or structure that could have assembled them automatically? A workout log, a product changelog, a location history, a set of interview clips. If yes, you’ve found a templating opportunity, and you should prototype it manually before you buy a tool for it.
Second, test How It Went’s core question yourself if you’re in the outdoor niche: import a track and a handful of photos, fix the camera clocks first, and see whether the auto-placement is good enough to publish without a manual pass. The free tier makes this a zero-cost experiment. Report back to the maker — he’s explicitly asking for it, and that feedback loop is how niche tools either widen or die.
Third, watch the on-device rendering trend. When Adobe and CapCut start marketing local-first rendering as a feature, you’ll know the category has shifted. Until then, the indie tools are where the interesting bets are.
And fourth, don’t confuse a finished asset with a distributed one. The schedulers — Buffer, Later, Metricool — still own distribution, and they will for a while. The creator who wins the next year is the one who automates assembly and keeps human judgment on the hook, the caption, and the platform fit. How It Went is a small, honest example of the first half of that equation. The second half is still your job.
