Let AI Turn Your Run Data into a Post: Social Copy Is Live in PaceGuru

The ten minutes every runner knows

You finish a 10K with great numbers: seven seconds per kilometer faster than last time, with a lower heart rate. You want to post it — and then—

You stare at the digits, not knowing where to start.

Write the pace? Friends who don't run won't know what "5:03" means. Write how it felt? "Felt good today" says nothing. Paste all the raw numbers? That reads like a work report.

So many runs worth remembering end up as a lone screenshot captioned "done."

We wired copywriting into the sharing flow

The share menu on every run record now has a "Social Copy" entry. Tap it, and AI reads the run's key numbers — distance, pace, heart rate, plus how they compare to your recent form — then writes a caption you can post as-is.

Four styles to choose from:

• Recommend: evangelist energy, warm but not overhyped — for selling "running itself" to your friends
• Minimal: restrained data statements, one highlight per line, for daily-log style posts
• Data-driven: makes the progress legible — pace, heart rate, trend comparisons, the stuff runners get
• Humor: self-deprecation and light jokes, for "survived today's intervals" moments

A few design decisions

Title separate from body

Generated copy has its own headline, with the body below. Card-style previews on most platforms are built for this structure — the headline grabs attention, the body carries the detail. Mash it into one paragraph and everything disappears when the card collapses.

Platform-neutral

We didn't tune for any specific platform — no built-in tone or hashtag stuffing for any particular app. The copy reads fine wherever you paste it. Where you post is your business; ours is telling the story of the run well.

Follows your app's language

Whatever language your app is set to, that's the language the AI writes in. Chinese users get Chinese copy, Japanese users get Japanese — no "English app generates a Chinese post" mismatches.

No repeated requests for the same run

Generated copy is cached. Open the same record again and you see the previous result instantly — no repeat request, no repeat wait. What you want is a fast copy, not watching the AI write it again.

When to reach for it

In my own use, two scenarios stand out:

One is a run with a story. A new PB, a first time at some distance, holding it together through awful weather — the AI digs the progress out of the numbers and turns it into a proper record.

The other is can't be bothered. Everyday training doesn't have that much to say, but a continuous record is its own kind of meaning. Tap, pick a style, copy, post — thirty seconds for a record, which beats "never mind, not posting."

One last thing

Social sharing isn't vanity — it's the cheapest positive feedback an ordinary runner can get. Next time you finish a run, let AI save you those ten minutes.