Reps

Reps is a strength training log built for the pace of an actual workout. Log a set in seconds on iPhone, check it off from your wrist, review the week on your Mac, put your history on the TV in the garage gym — one app, every Apple device, synced through your own iCloud. No social feed. No subscription pressure. A log, done properly.

What's in the app

• Inline set logging. Exercise, reps, weight, optional RPE and rest — entered in place on the main screen, edited in place, shake to undo.
• Every Apple screen. iPhone and iPad for logging, Mac for review, Apple Watch to check off sets mid-workout, Apple TV for a 10-foot view of history and stats.
• Personal records that mean something. Estimated one-rep maxes per exercise, top weights, weekly volume summaries, per-exercise history with what you did last time right there.
• lb and kg, selectable per profile. Bodyweight and band work treated as real training, not a missing-weight edge case.
• Six equipment contexts — gym, barbell, dumbbells, cables, bands, bodyweight — so plans match what you actually have.
• An MCP connector for AI assistants. Claude can read your history, surface PRs, summarize your week, plan a session, and log sets — reads from your synced store, writes dispatched through the app so sync stays intact.
• AI workout planning built in, with a chat flow that drafts sessions against your profile and equipment.
• 16 languages. Fully localized at launch, from Japanese to Arabic.
• Private by architecture. Your training data lives in SwiftData mirrored to your private iCloud. Optional HealthKit read and write-back. No accounts, no server of ours.

Why the studio built this

Workout apps keep becoming content platforms: programs to buy, feeds to scroll, streaks to protect. The thing a lifter needs between sets is smaller than all of that — what did I do last time, and where do I write what I just did. Reps is built around those two moments. Everything else, including the AI planning and the MCP connector, exists to serve the log, not to replace it.

How it was made

One SwiftUI codebase across five platforms, SwiftData persistence mirrored through CloudKit's private database, WatchConnectivity pushing live workout snapshots to the wrist and syncing completions back. The MCP connector is a small dependency-free Python server that reads the Mac app's local store and dispatches writes through the app's own URL scheme, so a set logged by an assistant flows through the same sync path as a set logged by thumb. HealthKit integration is read-and-write-back, strictly optional.

Frequently asked

What does Reps actually track?

Sets. Exercise, reps, weight, optional RPE and rest time, logged inline with in-place editing and shake-to-undo. Weights in lb or kg; bodyweight and band work are first-class.

Which devices does it run on?

iPhone, iPad, Mac, Apple Watch, and Apple TV — one app, synced through your private iCloud. The Watch mirrors the current workout for set check-offs; the TV shows history and stats at room scale.

Can AI assistants work with Reps?

Yes. The MCP connector lets assistants like Claude read history, surface personal records, summarize the week, plan a workout, and log sets. Writes go through the app so sync stays intact.

Does it connect to Apple Health?

Optionally. Reps can read body metrics and write completed strength workouts back. It works fully without Health access.

Is Reps available now?

It's on its way to the App Store. Use the notify form above and you'll get one email when it ships.