Buy me a coffee

You've scrolled past the features. You've read the format spec (or at least skimmed it). You're still here.

That either means you're lost, or you care.

Either way — hi. I'm Viktor. I build this from Prague.

$ cat what-your-coffee-actually-buys.log

01Mass coffee deployment (the irony is not lost on me)

022am parser rewrites that absolutely could have waited until morning

03Debugging SQLite on Sunday mornings instead of going to the gym

04Keeping the .trn spec MIT licensed forever

05One step closer to the day your workouts aren't trapped in someone else's database

06Definitely not mass-produced mass gain supplements

☕

Buy me a coffee

One-time · No account needed · 100% goes to the project

(.´࿉˽࿉.)◞

thank you

─── but wait, why does a workout app need support? ───

Here's the thing. TRN isn't just an app. The app is one part.

The bigger part is the .trn format — an open standard for describing workout programs. Like Markdown for text or JSON for data, but for training. MIT licensed. Free forever.

The idea is simple: your workouts should move freely. Write a program in any editor. Share it on Reddit. Import it into any compatible app. Switch apps without losing your history.

Right now, every fitness app is a walled garden. Your data is their data. Sharing means screenshots. Switching means starting from zero.

We're building the rabbit hole out.

Open format

The .trn spec is MIT licensed. Anyone can implement it in their app. We want them to.

Portable data

Export, import, modify, fork. Your workouts belong to you, not to an app.

Build on it

Parsers, converters, alternative apps — the whole point is that anyone can build.

No money? No problem.

▸Post a .trn workout on Reddit, Discord, or X
▸Implement .trn in your app — the spec is here
▸Tell a friend who trains
▸Open an issue on GitHub when something breaks (it will)