Buy the Arcade kit when the product is a games store
If the product you are shipping this quarter is a games store, buy the Arcade kit. The product page is a React Native and Expo template for that job: a five-tab store, hero carousels, an HTML5 game catalog, and a player profile, at $99. Browse, play, a library, and a player profile are the product. This is the SKU that already names those objects.
The other kits you can buy alone today at $99 are the SaaS Dashboard and the Fitness kit. Pricing lists those three as the live kits. Booking remains a preview on the bundle path until it is live. Marketplace is coming soon and is not sold on its own. Waiting on either one leaves the catalog, the library, and the profile unbuilt. If you already need two or more live kits in the same purchase, use pricing and the pack-versus-one-kit post. If the only product is the games store, checkout is the Arcade kit.
Name the product before you open checkout
A games store, for this decision, is a specific object. People open a home, scan a featured row, browse by genre, open a game, play it, keep a library, and return to a profile that remembers them. Search, filters, and wishlists sit on that path. Sign-in exists so the library belongs to someone.
Catalog, play, library, and profile means this SKU. A dashboard product means the SaaS Dashboard. A fitness product means the Fitness kit. All three live kits are $99. The product object is the difference. Booking and Marketplace appear beside them as other cards. Pricing does not sell those two as solo live kits, so they stay off this checkout.
What you already have on day one
The Arcade product page is the inventory. The hero describes one template: React Native and Expo, a five-tab games store, hero carousels, a real HTML5 game catalog, and a player profile.
Discover and play is a dark-first home with a featured hero carousel, genre browsing, full game-detail pages, and instant search. The labels in that block are Home, Store, Browse by Genre, Game Detail, and Search.
The library block is instant-play picks, the player's game library, and a profile with level, coins, and an Arcade Pass state. Its labels are Instant Play, My Library, and Player Profile.
Sign-in is a first-run onboarding flow plus email, Google, and guest, listed as wired. Its labels are Onboarding, Sign In, and Sign Up.
The same page checks off hero carousels, a game store, a real game catalog, game detail pages, category browsing, search and filters, a player library, wishlists, and a player profile.
The storefront on the page is seeded: genre chips for Action, Racing, Puzzle, Arcade, and Sports, a top-this-week list of titles, an Arcade Pass line, and a free-games count. That chrome is the UI. It is not your license count, and it is not a player-count claim.
The stack block names Expo SDK 54, with one codebase for iOS, Android, and a web export; React Native 0.81; TypeScript 5.9; a Hono API; and Postgres with Drizzle, including schema, migrations, and seed data. The page says iOS and Android are tested. An Expo Go preview on SDK 54 opens the live kit with no build step.
Every kit ships with CLAUDE.md, .cursorrules, and 26 tested prompts, aimed at Cursor, Claude, Lovable, and Bolt. That hands the repo to an assistant. You still read the catalog and the profile.
The purchase line is one-time, source on GitHub, demo stays free, kit price $99.
One codebase. iOS, Android, and web.
The Fitness Kit ships with auth, a database, and a backend already connected — no setup. Live demo at fitness-preview.otf-kit.dev.
Run this checklist before you pay
| This quarter | Checkout |
|---|---|
| Games store only: browse, play, library, player profile | Arcade kit, $99 |
| Dashboard product only | SaaS Dashboard template |
| Fitness product only | Fitness kit template |
| Two or more live kits, or a live kit plus a run of landings | Pricing bundle |
| Booking or Marketplace as the games-store base | Neither is a solo live kit, and neither is this catalog |
Stay on the Arcade row when the rest is also true.
You would otherwise build the catalog, the library, and the profile before launch. You need iOS, Android, and a web export from the Expo SDK 54 codebase the page names. A marketing site on its own belongs with the landing templates. The free SDK versus paid kit post is that fork. Day-one sign-in matches email, Google, or guest. You want the Hono API and the Postgres plus Drizzle setup the page names, including schema, migrations, and seed data. A server or database you have already committed to elsewhere is a port, so price that port before you pay.
Pricing describes each live kit as login, payments, and a database already wired. The Arcade page names email, Google, and guest, plus Postgres. It does not print a payment-provider name in the stack list, so read that surface in the repo you receive.
A second live kit already funded beside the games store moves the decision to pricing and the pack post. This kit is the games-store purchase. The pack is the purchase you make when a second live kit, or a stack of landings, is already on the plan.
The other live kits are different products
Pricing's solo buy row is SaaS Dashboard, Fitness, and Arcade, each at $99.
The SaaS Dashboard template is the dashboard kit. Use it when that dashboard is the product. The Fitness kit template is the fitness product. Both can ship on a phone. A fitness product does not include the Arcade page's genre browse, playable HTML5 catalog, or profile with level, coins, and an Arcade Pass.
The bundle post is where pack versus one kit gets decided. This post stays on the single games-store SKU.
When you do not need this kit
Skip this kit when the product is a SaaS dashboard or a fitness app, and decide on those template pages.
Skip it when you need components and themes, and the critical path has no catalog, library, sign-in, or database. Stay on the free SDK.
Skip the single-SKU button when two or more live kits, or a live kit plus a run of landings, are already planned. The prices that govern the pack are printed on the pricing page.
Skip the wait for a solo Booking or Marketplace buy button. Pricing marks Booking as a preview on the bundle path until it is live, and Marketplace as coming soon and not sold individually. A games catalog is not what those rows describe.
Skip the purchase when you already run a catalog, accounts, and a profile service and only wanted a look at the UI. Open the demo. The kit is source for a store you intend to own.
What you still do after the repo is yours
The storefront is seed data rendered through the Drizzle schema: genres, a ranked list, search, and an Arcade Pass state. Replace that seed with the catalog you have rights to ship. Ratings, play counts, and free-game figures in the demo chrome stay demo figures until they are your numbers.
Level, coins, and Arcade Pass are profile fields you can keep or rename. Coin sources, pass price, and what the demo's "no ads" and "cloud save" lines mean for your titles are still your call. The page shows those words on the pass line. Your economy is a later edit.
Guest sign-in lets someone play before creating an account. You still decide how that session becomes an account and what happens to the library. New fields, wishlist rules, and the entitlement behind Arcade Pass land on the Hono API and the Drizzle schema. CLAUDE.md, .cursorrules, and the 26 prompts describe the repo to an assistant. Game licensing and the store listing stay with you.
The versions printed on the page today are Expo SDK 54, React Native 0.81, and TypeScript 5.9. The Expo Go preview is pinned to SDK 54. Schedule any later upgrade on purpose.
Check the demo, then use this checkout
Open the live demo once at https://arcade-preview.otf-kit.dev and walk home, the carousel, genre browse, a game detail, search, the library, and the profile. When that path is the product, buy it here: Arcade kit, $99. The page states a one-time purchase and source on GitHub.
When the walk-through is a different product, use the checklist. The other live $99 pages are the SaaS Dashboard and the Fitness kit. When you need more than one live kit, the bundle decision stays on the pricing page.
Sources
- Arcade kit product page: https://otf-kit.dev/templates/arcade-kit
- Arcade demo: https://arcade-preview.otf-kit.dev
- Pricing: https://otf-kit.dev/pricing
- SaaS Dashboard template: https://otf-kit.dev/templates/saas-dashboard
- Fitness kit template: https://otf-kit.dev/templates/fitness-kit
- Everything Bundle versus one kit: https://otf-kit.dev/blog/everything-bundle-vs-single-kit
- Free SDK versus a paid kit: https://otf-kit.dev/blog/free-sdk-vs-paid-kit-when-to-buy
Stop wiring. Start shipping.
- Login, database, and backend already connected — nothing to set up
- iOS + Android + web from one codebase
- AI configs pre-tuned + 40+ tested prompts included