Use cases

Build a community

Profiles, feeds, posts, comments and directories, with ownership rules per record.

Community apps are about who may do what. Ownership rules are first-class here: a member edits their own post, a moderator edits any, a visitor reads what is public — expressed once as an access rule instead of scattered across the screens.

People reach this page looking for

  • how to build a community app
  • create a social network for a niche
  • member directory app with profiles
  • build a forum or feed app without code

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.

01

Profiles and a feed that belong to your community

Posts, comments, likes and follows as models you own, with the moderation rules you actually want.

02

Ownership rules that hold up

A member edits their own post, a moderator edits any, a visitor reads what is public. Said once, enforced by the database.

03

Directories, groups and topics

Searchable listings of people, places or businesses, with the fields your niche cares about instead of a generic bio.

04

Notifications people actually come back for

Push and email when someone replies, joins or mentions them — installed on the phone, not just open in a tab.

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.

Describe it in plain language

Say what the app does and what it has to remember. No diagram, no schema, no naming a single framework.

Watch it get built

Screens, data models, login and payments appear while you read. Anything you do not like, you say so and it changes.

Publish, then keep changing it

Live on your domain in seconds, with version history behind you. Tuesday's conversation is Tuesday's release.

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 community app for urban gardeners. Members have a profile with a photo, city and bio; they publish posts with pictures, comment and like; there are topics you can follow; a member can edit or delete only their own content while moderators can edit anything; a public directory page lists members by city for search engines; and members get a push notification when someone replies to them.

Questions

Frequently asked questions

Yes, and this is the part communities usually get wrong. Ownership is a first-class rule: the author edits their own record, the moderator role edits any, and anonymous visitors see only what you marked public — decided in the database rather than in each screen.

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.

Build this app freeUse cases