Health, home and travel decision

Steps: Workout & Pedometer

A capable developer can reimplement a useful local step-and-workout tracker with route playback and basic on-device coaching, but replicating the app's polished cross-device UX, App Store presence, and global real-time leaderboard at scale is non-trivial.

View on the App Store
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off120 h to build

$30/mo6 h/mo upkeep

No published price to break even against.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Collect step and workout data from Apple HealthKit and CoreLocation; persist workouts and stats locally; display interactive charts, calendar heatmap and widgets; record and replay GPS routes with 3D playback; provide simple on-device AI feedback (rule-based or using on-device ML).

What it still won’t have

  • Polish and design-quality of the App Store release (icons, animations, theme variants)
  • Mature Apple Watch complication design and store-grade widgets
  • A built-in global leaderboard with real-time ranking and hosting/scale handled
  • Any proprietary on-device AI sophistication the app ships with
  • App Store presence, ratings, and existing userbase

What remains hard

  • Brand trustAS SEEN AT WWDC 2026
Read the build prompt

First-year cost

No published price

Steps: Workout & Pedometer does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build an iOS fitness tracker in Swift using SwiftUI + Combine, HealthKit, CoreMotion, CoreLocation and WatchKit; store workouts and step history in Core Data; include: HealthKit sync (steps, workouts, HR), live workout recorder (GPS, pace, elevation), GPX export, local 3D route playback, interactive charts and calendar heatmap, home widgets and a basic on-device AI Coach implemented as rule-based analysis or a small Core ML model; include a simple Node.js + Express backend with Postgres to host an optional global leaderboard (flat REST API: submit workout summary, fetch top N), and map tile usage via Mapbox (configurable key); explicitly out of scope: App Store release tasks, payment/subscription handling, and a production-scale real-time ranking system; require error handling for HealthKit/Location permissions, unit tests for data layer and workout recorder, and end-to-end tests for workout saving and GPX export.
How we checked1 sources · 2/3 runs agreed · evidence score 52

How the score was reached

  • Partly verdict base52
  • Evidence score52

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 1

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat quoted from the page