Use cases

Loyalty program app

A points or stamp card on the phone, QR code scanning at the till, rewards at a target, a birthday coupon and a nudge for customers who stopped coming.

A paper stamp card works until the customer loses it, and it leaves nothing behind: you do not know who the person is, how much they spend or when they stopped coming. In the app, the balance is a record tied to the customer's account. A purchase adds points with a QR code scan at the till, the reward becomes available when the balance reaches the target, and anyone who has not shown up in a month gets a message with a reason to come back.

People reach this page looking for

  • loyalty program app
  • how to create a customer loyalty program
  • digital stamp card app
  • rewards points app for small business

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

Points or stamps, on your rules

A point per dollar spent or a stamp per visit, with a target and a reward you define. The rule is a record, so changing the promotion does not need a new app.

02

Scanning at the till by QR code

The customer shows the QR code from their account, the staff member scans it with a phone and enters the purchase amount. The balance goes up right away, with date, store and staff member recorded.

03

A redemption that deducts the balance once

Rewards with a points cost and an available quantity. Redeeming generates a code the till confirms, and the balance is deducted exactly once.

04

Birthdays and lapsed customers

An automatic coupon in the birthday month and a message to anyone who has not bought in thirty days, by email or push. It is the part of the program that brings people back.

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 loyalty program app for a coffee shop with two locations. A customer signs up with name, mobile number, email and date of birth and gets a personal QR code; every dollar spent is worth one point, and the staff member scans the customer's QR code with the phone camera, types the purchase amount and picks the location, recording who added the points and when; rewards with a name, photo, points cost and available quantity; the customer sees their balance, statement and the rewards already within reach, and requests a redemption, which generates a code confirmed by the staff member and deducts the balance exactly once; points expire twelve months after they are earned, with a notice thirty days before; in their birthday month the customer gets a coupon by email; anyone who has not earned points in thirty days gets a push with bonus points; staff see only the scan and redemption screen; and I see a dashboard with active customers, points issued and redeemed per month, average visit frequency and customers per location.

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.

AquaVale — Plumbing & Repair Services

Sales & CRM

An institutional site for a service company: a catalogue, a portfolio, a journal and care plans, with a panel that receives every quote request.

12 screens

Cadence

Sales & CRM

A sales CRM whose coach reads the deal and tells you the next move.

12 screens

Questions

Frequently asked questions

No. The app opens in the browser from a link or a QR code on the counter and installs to the home screen as an icon, with no store involved. If you later want App Store and Google Play versions, the same project ships as a native app under your own developer account.

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.

Build this app freeUse cases