A squad with positions and age groups
A player with a photo, position, shirt number and age group, linked to a parent or guardian when they are a minor.
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.
Call-ups with confirmation
The coach calls players up for a match or training, the player confirms or declines, and the list closes at the deadline you set. Anyone who has not answered gets a push.
Monthly fees and one-off charges
A monthly fee as a card subscription and one-off charges for kit or tournaments, with the list of who is behind on the dashboard.
Match reports, top scorers and results
Score, goals, assists and cards for every match. The top scorers and the season's results come from adding up the match reports.
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 youth football academy that also has an adult amateur team. Players with a photo, date of birth, position, shirt number and age group, and minors linked to a parent or guardian who uses the app for them; coaches with their own accounts who see only their own age groups; training sessions with day, time and place, with the register taken by the coach; matches with opponent, date, place and age group, and call-ups where the player or the parent confirms attendance by a deadline, with a push to anyone who has not answered; a match report for every game with the score, goals, assists and cards, feeding the top scorers and the season's results; a monthly fee billed as a card subscription, plus one-off charges for kit and tournaments, with a history per player; a noticeboard and match photos; and an admin dashboard only I can see, with players per age group, average training attendance, arrears and top scorers per age group.
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 subscribe when you want your own domain without the badge or your app in the stores, and on the Builder plan you take the code with you if you ever want to.