A front desk with parcels and visitors
The doorman logs the parcel and the resident gets a push right away. A visitor pre-approved by a resident appears on the front desk's list for the day, with name and time.
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.
Amenity booking with rules
Function room, barbecue area and court, each with its own calendar, a minimum notice period and a usage fee. Two bookings in the same slot fail in the database.
Maintenance requests with a number and a reply
Noise, a leak or a dead light bulb becomes a ticket with a photo, a status and the manager's reply. Residents follow it without asking in the group chat.
Announcements and documents
Notices from the manager by push to everyone or to one block, and meeting minutes, house rules and financial statements kept in one place.
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 residential building with three blocks. Residents with name, contact, block, flat number and type, owner or tenant, registered by the building manager or approved by them; the front desk has its own account and logs parcels with a photo and recipient, the resident gets a push on arrival and the front desk marks the pickup; residents pre-approve visitors and contractors with name, ID and date, and the front desk sees the day's list and logs entry and exit; amenities with their own calendar, a minimum notice period, a usage fee and rules, preventing two bookings in the same slot; maintenance requests with a category, a photo and a status of open, in progress or resolved, with a reply from the manager; announcements by push to everyone or to one block; a documents area with meeting minutes, house rules and financial statements; and a manager dashboard with uncollected parcels, the month's bookings, open requests by category and residents per block.
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.