Trust

When a routine says it is from your coach, it really is.

Anyone can send you a file. The question is whether it is the one the creator actually published, unchanged, with their name on it honestly. A published stack answers that before you run a single step, and the app tells you plainly when it cannot.

Checked on importSignatureEvery assetExpiry
The import screen in Timer Stack, showing where a routine came from before it is added
Before anything is added to your library, you see what it is and where it came from.

What Travels

Send the routine, not instructions for rebuilding it.

Share a workout today and what arrives is a description: a screenshot, a caption, a video to pause and rewind. The other person still has to reconstruct it, and most never do. A stack travels as the routine itself, so it lands ready to press start.

  • The sequence: every step with its label, duration, icon and colour, plus the rounds, rests and nesting that shape how it flows.
  • The cues: music attached to steps, sounds, and any description, image, audio or video a creator embedded, so guidance arrives exactly when that step does.
  • The presentation: the name, category and cover, and for published routines the creator identity that appears while it runs.
  • The proof: a signature and a hash of every file, so the routine can be checked against what was actually published.
A share card showing a routine's duration, rounds and timer count above a QR code
Duration, rounds and steps are visible before anyone imports.
Receiving a routine from someone nearby, with no link and no connection

What Is Actually Checked

Three checks, every time, before the routine reaches your library.

The verified badge is not something a creator types into a field. Your phone works it out for itself, in the moment before the routine appears.

  • It was sealed by the creator. Publishing seals the routine with a key only that creator holds, and your phone checks the seal against their public identity. Nobody else can produce one that matches.
  • Nothing was swapped on the way. Every file inside carries a fingerprint. Change a single character of a step, or quietly replace a logo, and the fingerprints stop matching.
  • The identity is still current. Creator identities carry an expiry date, checked as the routine arrives, so one cannot keep vouching for things long after it should have lapsed.

If any of that fails, the routine still imports. It simply arrives unverified, and the app says so rather than quietly pretending otherwise. For the curious: the seal is an ECDSA signature on the NIST P-256 curve, and the fingerprints are SHA-256 hashes.

Why It Is Built This Way

A shared routine has to survive being useful to somebody else.

Trust has to last the whole handoff. A routine is worth sharing precisely because it travels: link, QR code, file, gallery. Every hop is a chance for something to be altered, and the person receiving it is the least equipped to notice.

⚡

Light enough to send anywhere

The routine itself is small, so it fits in a QR code on a gym wall or a message thread. Heavier media resolves separately rather than bloating every copy.

🔑

Creators keep their name

Publishing under your identity means a routine circulating with your brand on it can be shown to be yours, not an imitation assembled by someone else.

👁

Runners see the state

Verified, unverified, or edited: the app shows which, rather than presenting every import as equally trustworthy and hoping for the best.

📴

Nothing depends on our servers

The checks run on your device against the routine you received. One passed between two phones in a room with no internet verifies exactly the same way.

📱

Your identity follows you

A creator's signing key is held in the Keychain, encrypted end to end and carried across their own devices by iCloud. It used to be bound to one handset, which was safer on paper and wrong in practice: changing phone meant losing the identity your audience recognised.

After You Import

Your copy is yours to change. The original stays identifiable.

An imported routine is a working copy, not a locked document. Retime the intervals, swap the music, cut the steps you do not need. It does not phone home and it does not expire.

What you cannot do is edit a routine and still present it as the creator's published original. The moment the contents stop matching the signed manifest, the verified state no longer applies, because the thing it vouched for has changed. That is the honest behaviour, and it protects the creator and the next person to receive it equally.

None of this is only for creators. A routine you throw together for a training partner travels exactly the same way a studio's published programme does. The difference is how it is presented, and whether it carries a seal, not how it works.

Editing an imported routine in Timer Stack

Most people will never think about any of this.

That is the point. The work happens in the second between tapping a link and seeing the routine, so the only thing you have to decide is whether you want to run it. The gallery is the fastest way to see it happen: pick a routine, import it, run it.