Classes whose places genuinely run out
A class with a time, an instructor and a cap. When the last place goes, the sign-up fails in the database, and there is a waiting list.
What gets built
Four things you could have working this week
Not a feature list. These are the apps people actually describe, and what the platform hands back when they do.
Membership as a subscription
Monthly, quarterly or annual plans billed on their own by card, with anyone overdue appearing on a list rather than in a spreadsheet.
A training plan per member
Exercises, sets, reps and load, written by the instructor and opened on the member's phone, with the load history for each exercise.
Check-in and attendance
The member confirms they came, and you see attendance per member and per class, which is the number that predicts a cancellation before it happens.
Included
The parts nobody wants to build twice
Database, login, payments and publishing are part of the platform, not a list of services you go and wire up afterwards.
A real database, not a form dump
Every screen reads and writes models you can open, query and export. The data is a database of yours from the first minute, not a spreadsheet the app pretends to read.
Login for your own users
Email, magic link and Google sign-in, with roles and per-record ownership enforced by Postgres itself. A badly written screen cannot become a leak, because the database answers empty.
Payments that land in your account
Stripe, Pagar.me and Mercado Pago connect once. Card, Pix, boleto and subscriptions, with the card fields rendered by a hosted vault your app never touches.
Web, installable, and in the stores
One project published three ways: your own domain, an icon on the phone straight from the browser, and a signed binary submitted under your own store account.
Found in search, and by the models
Titles, metadata, sitemap, structured data and social images are generated with the app. Pages get found instead of only being linked.
React code you can take with you
Real React, edited line by line or by clicking the element on screen, exported as a ZIP or pushed to your GitHub. No lock-in you have to negotiate your way out of.
How it works
From a paragraph to a published app
Three steps, and the second one is the one people do not believe until they watch it.
Start here
A prompt you can paste right now
This is a complete first message, not a slogan. Paste it, change the nouns to yours, and you have an app to react to instead of a blank page.
Build an app for a gym. Members sign up and subscribe to a monthly, quarterly or annual plan by card, with recurring billing and payment history; classes have a discipline, an instructor, a day, a time and a cap, and members sign up while places remain, joining a waiting list when they do not; members check in on the day of the class; each member has a training plan written by an instructor with exercises, sets, reps and load, and records the load they used; instructors see only their own classes and those members; and I see a dashboard with active members, overdue accounts, average attendance per class and occupancy per time slot.
Ready to start from
Templates in this category
A template is a working app with data already in it. Open one, make it yours, publish it under your own account.
Questions
Frequently asked questions
Describe it. See it running. Publish it to the store.
Free to start, no credit card. You only pay when you want to publish under your own brand, and you take the code with you if you ever want to.