Sights with a location
A beach, viewpoint, museum or trail with photos, opening hours, entry price, a tip and an address. Each sight has its own page and appears on the map.
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.
Itineraries by number of days
A one, two or three day itinerary with the order of stops and the suggested time at each. The visitor saves the itinerary and ticks off what they have seen.
The season's events
Festivals, fairs and concerts with date, place and price, filtered by the travel dates of whoever opens the app.
Tours with seats and a voucher
A boat trip, hike or city tour with departures by time, a seat limit and card payment. When a departure is full, the booking fails in the database.
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 a tourism app for a seaside town. Sights with name, category, photos, description, opening hours, entry price, a tip and an address with a map location, each with its own page built for search engines; one, two and three day itineraries, each with an ordered list of sights and the suggested time at each stop; visitors sign up, save itineraries, mark sights as visited and leave a review with a rating and comment; an events calendar with date, place and price, filtered by the travel dates the visitor enters; tours with departures by date and time, a seat limit, a meeting point and card payment, issuing a voucher with a QR code; tour guides with their own accounts who see only the passenger list for their own departures and check the voucher at boarding; and an admin dashboard only I can see, with the most viewed sights, the most saved itineraries, bookings per tour and revenue 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.