Health, home and travel decision

Steps & Beasts

A competent developer can reproduce the core pedometer + collectible loop, but matching the full polished app (art, animations, cross-device polish, and App Store traction) is multi-week work and costly to fully replicate.

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-off46 h to build

$0/mo3 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

  • Read steps from Apple Health each day, count toward a daily goal, hatch a daily egg when goal reached, add the hatched Beast to a local collection, and display progress via app UI and home-screen widget.

What it still won’t have

  • High-quality original art and animations for 200+ unique Beasts
  • Polish, UX tweaks, and iterative design improvements visible in release notes
  • App Store listing history, ratings, and developer brand trust
  • Cross-device conveniences like Apple Watch-specific polish (unless implemented)

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Steps & Beasts 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 a self-contained iOS app in SwiftUI that reads steps from HealthKit, stores user data in Core Data, and provides a gamified daily-egg hatching experience. Stack: Swift + SwiftUI, HealthKit, Core Data, WidgetKit, UserNotifications, and XCTest. In scope: HealthKit integration (including historical import), daily goal & streak logic, rarity assignment and collection model for ~200 beasts, basic animated egg hatch interaction, Beast collection and detail screens, a home-screen widget showing egg evolution, local notifications, onboarding and permission handling, sharing images, error handling, and unit/UI tests. Out of scope: server-side backend, multiplayer or marketplace features, paid subscriptions or in-app purchase plumbing beyond stubs. Deliverables: Xcode project with CI-friendly test suite, sample assets for beasts, and documentation to build and run on device.
How we checked1 sources · 3/3 runs agreed · evidence score 56

How the score was reached

  • Partly verdict base52
  • 3/3 assessment runs agreed+4
  • Evidence score56

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.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded