A player for the stream the station already has
The app plays the stream URL from your streaming server, whether Shoutcast, Icecast or the service the station already pays for. The play button stays fixed on every screen.
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.
A schedule with who is on air
Shows with day, time, presenter and photo. The app compares the schedule with the current time and shows the show on air and the next one.
Song requests and messages
The listener requests a song with their name and neighbourhood, and the request goes into the show's queue that the presenter sees in the studio, marking what has been played.
News, competitions and alerts
Stories with photos, competitions with rules and entry, and a push when a favourite show starts or the prize draw result is out.
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 an FM radio station that also streams online. A live player that plays the station's stream URL, fixed at the bottom of every screen, with the name of the show on air; a weekly schedule with shows, day, start and end time, presenter and photo, highlighting the current show and the next one; listeners sign up and send song requests with artist, song, name and neighbourhood, and messages to the presenter; presenters have their own accounts and see the request queue for their own show, marking each one as played; news with photos and categories published by the team; competitions with rules, a deadline and entry, with one entrant drawn at random when the deadline passes; listeners mark favourite shows and get a push when they start; and an admin dashboard only I can see, with requests per show, entries per competition and listeners signed up per month.
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.