All sports

Fix your form.
See what your stride does.

Turn your phone into an AI biomechanics lab.

Set the phone side-on and run past it. Llyr reads your body through the stride, counts your steps per minute, and gives you cues you can actually use. The numbers it can't work out honestly, it leaves out.

One phone, propped at the side Nothing to strap on Reads you as you move Analysis runs on the phone
A runner filmed side-on at a track, with Llyr's joints and bones drawn on him and his front knee marked at 92 degrees. A hatched band across the bottom of the frame marks his feet, which fall outside it. A runner filmed from the side. Llyr's skeleton is drawn on the joints it found, his front knee is marked at 92 degrees, and the bottom of the frame is hatched where his feet fall outside it. 92°
Solid is what it found from the side. 92° is his front knee, worked out from those points. Hatched is his feet, outside the frame. Llyr won't call foot strike.

One number it trusts. Four it won't invent.

Running apps love a spec sheet: contact time to the millisecond, a foot-strike verdict, a pronation grade, an injury risk score.

A phone camera only looks at your stride about fifteen times a second. At that rate most of those numbers are guesses with a decimal point on them, so Llyr leaves them out.

Can see

Cadence Steps per minute is slow enough to count properly fifteen times a second, so it's the one number Llyr stands behind.

Can see

Your body position through the stride Your trunk, arms and legs from the side, followed frame by frame the whole way through.

Can see

Cues on the replay, in plain words You watch it back from the side with the correction drawn on your own video.

Can't see

Foot strike and ground contact time Both happen in the gaps between frames. A verdict here would be a coin toss with a label on it.

Can't see

Pronation, or any angle read from the front Pronation needs a view from behind and more detail than one camera gives. From the front, Llyr can't tell how far away a joint is, so any exact angle would be invented.

Can't see

Injury risk Nobody has shown that running a certain way causes a certain injury. Llyr is not going to tell you what's about to hurt.

Three moves, trackside.

1 Llyr's run gait screen with a runner filmed side-on, showing the Side and Rear framing options and a cue to aim the camera up a little.

Frame it

Phone side-on to the way you're running, whole body in shot. Llyr tells you to tilt it up or down before you start.

2 Llyr's run gait screen with a runner filmed side-on at a track, Side and Rear framing options, and a cue reading tap Analyze, then start running.

Run

Run an even stretch at a normal effort. Sprinting for the camera looks like a different runner.

3 Llyr's run gait screen with framing marks drawn on a runner filmed side-on and an on-screen cue reading aim the camera up a little.

Read it back

Your steps per minute, plus what changed in your shape, with a photo saved for each thing it flagged.

What we can promise today.

In early access

No runner has used this long enough to quote, so there are no reviews here. When there are real ones, they'll carry real names.

Shape, not times

Llyr looks at how you move. It doesn't time you, race you, or tell you what a session did for your fitness.

What it won't say is built in

Those four are blocked in the code itself, not just left out of the writing. No part of the app can get round them.

Judge it yourself

Join the list, film one steady stretch, and see whether the cues match what you already suspect about your running.

See what your stride does.

Join the early-access list. Sign up here and running is what you'll hear about.

100Seats in the first group

That is the whole of it. We would rather have a hundred people actually filming and telling us what broke than a list of ten thousand who never open it.

No spam. Just an email when there's something to try.

100 seatsIn the first group Get Early Access