# Rork Design/Build credits vs a fitness kit your Cursor agents keep

> Mobile Design vs Build credits and App Store submit in Rork, versus an owned fitness kit repo for Cursor.
> By Dave · 2026-09-11
> Source: https://otf-kit.dev/blog/otf-vs-rork

Rork is an AI chat builder aimed at mobile and web founders: describe an app, iterate in Design mode, spend credits in Build mode, preview on device, and follow a documented App Store path that uses an Expo token plus your Apple Developer account. The homepage also markets Rork Max App for building and publishing iOS apps on the go. That is a concrete credit-metered mobile sandbox — not a generic “AI website” chat.

This is the own-blog decision post for the sandboxed-agent catalog row labeled Rork. It is not a UI `/compare` page. The reader already uses Claude Code or Cursor. The question is whether Rork’s Free / Pro / Max credit ladder and in-product store submit should remain the system of record, or whether a fitness-shaped production kit repo is the better buy once the domain model hardens.

Important correction vs an older OTF article: [Rork can scaffold React Native; it cannot follow you to the App Store](/blog/rork-cant-ship-to-app-store) argued follow-through failure on store shipping. Rork’s current docs explicitly walk App Store submission. Do not treat that May 2026 claim as today’s fact. The 2026 wedge is different: owned fitness kit + EAS deploy scripts in a buyer repo versus staying on Design/Build credits inside Rork. Sister sandboxed rows with other exits: [otf-vs-bolt](/blog/otf-vs-bolt), [otf-vs-emergent](/blog/otf-vs-emergent), [otf-vs-v0](/blog/otf-vs-v0).

## What Rork optimizes for

Rork splits work into Design mode and Build mode. Free stays in Design mode — explore screens for iPhone, Android, web, and wider Apple surfaces. Paid plans turn on Build mode so you get working Swift, Kotlin, or React code you can preview, test on a device, and publish.

Documented plans (subscriptions docs):

- **Free ($0)** — Design only; 5 design credits/day; up to 35 credits/month in major markets (5 elsewhere); private projects.
- **Pro ($20/mo)** — 100 credits/month; Build for iPhone (SwiftUI), Android (Kotlin + Compose), web; Dev mode; email support.
- **Max (from $200/mo)** — 1,000–10,000 credits/month tiers; Pro platforms plus iPad, Apple Watch, Vision Pro, native games, iOS widgets, priority chat.

A credit is AI compute for design/build/edit. iOS builds and cloud simulator sessions can add machine cost on top of the triggering message. Pro is enough for iPhone — Max is for the wider Apple family and heavier credit packs.

```text
1. Start a private Rork project
2. Burn Design credits until IA and screens stabilize
3. Pay for Build mode only when a device vertical slice is worth it
4. For stores: Apple Developer account + Expo token per Rork’s App Store guide
5. List what still must live in YOUR IdP, Stripe, and EAS accounts
```

Step 5 is where Cursor/Claude Code buyers diverge from founders who are happy living on Rork’s meter.

## Design/Build credits vs an owned fitness tree

Credits are honest about compute. They are a weak substitute for:

- Fitness domain already encoded (classes, memberships, trainer roles) instead of re-prompting it every reset
- `CLAUDE.md` / `.cursorrules` / prompt recipes that survive when the chat tab closes
- EAS Build profiles and App Store/Play deploy scripts that live in a repo you own — see [one codebase, three platforms](/blog/one-codebase-three-platforms) and [staged OTA rollouts](/blog/eas-update-staged-rollout-guide)

Catalog row for Rork: mobile-focused sandboxed generation with the same production-handoff gap as the tier. OTF’s stated advantage: fitness kit ships as a real app with EAS Build + store deploy scripts included, not only a sandbox preview.

Verified kit inventory (outcomes): booking kit ships cross-platform client, Supabase RLS with `available_slots()`, Stripe/Resend server routes, preview at `booking-preview.otf-kit.dev`, agent files, delivery via `sync-kits.yml` (e.g. `otf-kit/booking-kit`). Fitness kit and saas-dashboard share that delivery class.

## When Rork is the right home

Stay in Rork when most of these hold:

- You need a mobile-first chat builder with Design → Build → device preview this week
- Documented App Store submit inside Rork (Apple Developer + Expo token) is enough store process
- Your team iterates in Rork’s agent / Dev mode more than in Cursor day-to-day
- Pro ($20) or Max (from $200) credit spend beats standing up a monorepo first
- The fitness domain is still fluid — you are still discovering screens, not enforcing tenant invariants

## When Cursor wants a fitness kit instead

Prefer the kit when most of these hold:

- Day-30 work is memberships, schedules, and roles you refuse to re-prompt after each credit reset
- Maintainers live in Cursor or Claude Code on disk
- You need a buyer mirror repo from `sync-kits.yml`, not only a hosted Rork project
- Store shipping must be scripts and EAS profiles you keep — not only Rork’s in-product submit for the first binary

## Decision map

![Decision diagram comparing when to prefer Rork sandbox versus owning a production kit](https://cdn.otf-kit.dev/blog/otf-vs-rork/inbody-01-decision-20260911m.jpg)

*Pick Rork for credit-metered mobile Design/Build; pick a kit when the artifact must be a fitness monorepo your agents keep editing.*

| Signal | Lean Rork | Lean fitness / production kit |
|---|---|---|
| Meter | Design/Build credits (Free / Pro / Max) | Kit + your cloud / store bills |
| First ship path | Rork App Store guide + Expo token | EAS Build + scripts in buyer repo |
| Domain start | Prompt fitness IA each session | Fitness kit domain already in-tree |
| Editor after week 2 | Rork agent + Dev mode | Claude Code / Cursor on disk |
| Continuity | Project history + monthly credit reset | Agent docs and migrations in git |

![Architecture diagram of Rork credit sandbox versus filesystem kit repo handoff](https://cdn.otf-kit.dev/blog/otf-vs-rork/inbody-02-handoff-20260911m.jpg)

*Left: prompt → credits → hosted Rork project → store submit. Right: sync kit → conventions → EAS/your infra → same tree next quarter.*

**Rork line.** Chat → Design (Free) or Build (Pro/Max) → device preview → optional App Store submit. Leftover work: IdP, billing edge cases, durable agent house style, fitness invariants you will not re-prompt forever.

**Kit line.** Sync buyer monorepo → conventions in-tree → schema and privileged routes → deploy on hosts you choose → filesystem agents keep editing. Leftover work: product customization, not inventing the skeleton.

![OTF cast reviewing a holographic ship checklist in a warm workshop lab](https://cdn.otf-kit.dev/blog/otf-vs-rork/inbody-03-cast-fresh-20260911d.jpg)

*Ship checks count when they sit on a repo you still open after credits reset.*

## Sequencing without dual-writing

1. **Week 0–1 in Rork** — Design mode for IA; Build mode only for one device slice.
2. **Freeze entities** — roles, membership events, store requirements that survived review.
3. **Pick the system of record** — stay on Rork credits/Dev mode/store submit, or move the frozen model onto a fitness kit Cursor already expects.
4. **Do not dual-write** schema and auth across Rork and a kit for a month.

## Bottom line

Rork’s documented product is a mobile-first sandboxed builder: Design vs Build, Free / Pro ($20/mo, 100 credits) / Max (from $200/mo), SwiftUI and Kotlin+Compose and web on Pro, wider Apple surfaces on Max, and App Store publish via Expo token + Apple Developer account (rork.com + docs.rork.com).

OTF’s purchase is different: an owned fitness/production kit with agent conventions and EAS store scripts in a buyer repo via `sync-kits.yml`. Choose Rork when the win is credit-metered mobile Design/Build and in-product store submit. Choose a kit when the win is still opening the same fitness tree in Cursor after the monthly credit anniversary.

## Sources

Rork product site (AI chat builder for mobile/web, App Store shipping, Rork Max App): https://rork.com/

Rork plans & subscriptions (Free / Pro / Max, Design vs Build, credits, platform matrix): https://docs.rork.com/introduction/subscriptions

Rork App Store publish guide (Expo token + Apple Developer account flow): https://docs.rork.com/store-guides/publish-app-store