Use cases

Grocery store app

Ordering from thousands of products in the app, items sold by weight, agreed substitutions, delivery slots and a weekly deals flyer.

A grocery store does not sell like a restaurant: the cart has forty items, some sold by weight, and something is always missing at picking time. The app that works here solves picking before the customer complains. It accepts weighed items at an estimated price, asks at checkout what to do if a product is out, and delivers in time slots you cap to match the team's capacity.

People reach this page looking for

  • grocery store app builder
  • online ordering app for a local grocery store
  • supermarket online shopping app
  • digital weekly ad for a grocery store

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

Thousands of products by aisle

A product with brand, aisle, unit of sale and photo, loaded from a spreadsheet the first time. Search by name and browsing by aisle, as in the store.

02

Items sold by weight

Bananas and meat go in by the kilo at an estimated price, and the real weight is adjusted at picking. The total is recalculated before the final charge.

03

Substitutions agreed at checkout

For each item, the customer chooses whether to accept a similar product, be asked first or leave it out. The picker sees the choice next to the item.

04

Delivery slots with a cap

Delivery times with a maximum number of orders in each. When a slot fills up, it disappears from the options, and the team does not promise what it cannot deliver.

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 shopping app for a neighbourhood grocery store. Products with name, brand, aisle, photo, price, sold per unit or by the kilo, and an availability status; search by name and browsing by aisle; a weekly deals flyer with a sale price and an end date, returning to the regular price on its own when it ends; a cart where items sold by weight show an estimated price; on each item the customer chooses between accepting a similar product, being asked first or leaving it out; delivery slots by day and time with a cap on orders, plus in-store pickup; a delivery fee and minimum order per neighbourhood; card payment in the app or on delivery; the picking team sees the order queue, marks each item as picked, substituted or out of stock and enters the real weight of items sold by weight, and the total is recalculated before the final charge; the customer tracks the order through received, picking, out for delivery and delivered, with a push at every change, and repeats a previous order with one tap; and an admin dashboard only I can see, with orders per slot, average basket, the items most often out of stock 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.

Vianda — Restaurant Delivery

Commerce

A restaurant delivery app: menu with add-ons, cart, delivery fee by neighbourhood and a live kitchen board.

8 screens

Balcão — Online Grocery Store

Commerce

A neighbourhood shop catalogue that closes the sale on WhatsApp: products, variants and a sales panel.

11 screens

Morada — Real Estate Portal

Commerce

A real estate website: search by neighbourhood, full listings, agents and viewing appointments.

9 screens

Palco — Event Ticketing

Commerce

An event ticketing app with sessions, tiers, checkout, a QR ticket and check-in at the door.

9 screens

Aurelia

Commerce

A slow-fashion label site: seasonal collections, timeless essentials, traceable materials and a newsletter.

6 screens

Questions

Frequently asked questions

The simplest way is to charge after picking: the order comes in at the estimated amount, the team enters the real weight, the total is recalculated and the customer pays the final amount by card, in the app or on delivery. That way nobody has to refund a difference afterwards.

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