A training camp is more than a folder of GPX files

Five days in the mountains leaves you with five disconnected activities, a camera roll, and nothing that holds them together. Why training apps are bad at trips, and what a better shape looks like.

Come back from five days of running somewhere good and look at what you actually kept.

Five activities in a list, indistinguishable from the five before them. A camera roll where the photos sit next to a screenshot of a boarding pass. Maybe a note in your phone. The trip — the thing you will still be talking about in two years — exists nowhere as one object.

Every training app is built around two units of time: the session and the plan. Trips are neither. A week in the Alps is not a workout and it is not a training block, so it falls between the two and gets stored as debris.

The unit that is missing

What is missing is a container for a stretch of time that meant something. Not a plan, not a session. A stretch.

Two kinds cover most of it:

A trip. A long weekend, a camp, a week somewhere with better hills than home. Bounded, short, and the reason you have photos.

A block. The sixteen weeks you just finished. Bounded, long, and the reason you have numbers.

They want different treatment, which is why lumping them together does not work. A trip wants the photos and the places. A block wants the totals and the shape of the progression. A trip is worth marking on a calendar because it is a minority of the month; a block covers every day you are looking at, so marking it distinguishes nothing.

Why the existing attempts feel hollow

Garmin shipped Epics in August 2026, which is the same idea, and the loudest complaint on their own forum is instructive: an epic lives inside the Epics screen and never appears anywhere else. One user put it as "what purpose does it really serve?"

That is the trap. If the container is a page you have to navigate to on purpose, you will look at it twice and never again. The value only appears when it turns up where you already are — beside the day you were there, in the list you already scroll — and when it can leave the app entirely.

What holds a trip together

In Stopa a story groups the sessions in a date range with your notes and your photos, on the days they happened. The sessions are already there; the story is what makes them one thing.

The membership is a rule rather than a hand-picked list, which matters more than it sounds: widen the range by a day and the session from that day joins on its own. You are describing a period of time, not curating a playlist.

A block story is the other shape — the totals, how much of the plan you actually completed, and the progression, snapshotted so it still reads correctly after you start the next block.

And it can leave: share it as a card, or as a short film the app assembles from the sessions and photos. That last part is the honest reason to build any of this. A training log nobody sees is a filing cabinet. Something you actually want to send to the two people you ran with is a different object.

Two things it does not do yet

Being straight about this, because the version on the App Store is the version I am describing:

There is no combined route map yet. Each session keeps its own route, but the single map with all five days drawn on it is not built. It is the next thing on this feature, together with the same layer in the film.

A story does not write anything back. It groups what is already recorded. It does not change a session, and it does not touch your plan.

The smaller point

Most of what makes training worth doing is not in the numbers. It is in a specific week, in specific weather, with specific people. That is not sentimentality — it is the part you will actually use to decide to do it again.

The numbers are already well served. The stretch of time is not, and it takes almost nothing to keep it: a date range, the sessions inside it, and the photos you took anyway.

Related:

We're building in public - follow along on X, Instagram, TikTok and Facebook.