A small restaurant can have its own pickup ordering and loyalty app, with no commission per order, by describing it to App Builder Agent: menu with photos and sold-out toggles, orders with a pickup time and live status, a digital stamp card, and an owner screen for the kitchen. The agent writes the code, shows a phone preview in the browser, and you change it in plain English. The first version fits in the Free plan; unlimited APK builds are $1.49 per 30 days on the Member plan at the time of writing. Payment happens at pickup or through your existing checkout link, not inside the app.
The delivery platforms taught customers to order from their phones and taught restaurants what 15 to 30 percent commission feels like. A pickup app of your own keeps the habit and drops the fee, and adds the thing the platforms never give you: the customer's name, their usual order, and a loyalty card that brings them back on a Tuesday. This guide is for an independent restaurant, cafe or takeaway in the US, UK, Canada or the EU with one location and a small team. It covers what the app needs, the prompt to paste, what the first minutes look like, how it reaches customers' phones, and what it costs.
What the app needs
Two apps live in one project: the customer app and the owner/kitchen app, sharing a hosted backend so an order placed on one phone shows up on the other.
- Menu with categories, photos and modifiers. Starters, mains, sides, drinks. Each item has a photo, price, description and structured options (size, spice level, extras) so the kitchen reads a choice rather than a sentence.
- Sold-out toggle per item. When the special runs out at 8 pm the owner flips a switch and it disappears from every customer's phone on the next refresh.
- Pickup orders with a time. The customer picks "as soon as possible" or a slot, the app quotes a ready time based on how many orders are open, and a notification arrives when the order is ready.
- Order status. Received, preparing, ready, collected. The customer sees it; the kitchen changes it with one tap.
- Loyalty stamp card. One stamp per order over a minimum, a free item after nine, a QR code in the customer's profile that staff scan to stamp or redeem. The mechanics are the same as in a punch card loyalty app for a coffee shop.
- Owner and kitchen screen. Today's orders sorted by pickup time, a big-font ticket view for the kitchen, the menu editor, and a daily summary (orders, revenue, best sellers) exportable as CSV.
- Contact details. Hours, phone, directions, and a banner for holiday closures.
If you want table ordering by QR code inside the restaurant as well, that is a separate flow described in the hotel or restaurant menu app guide; it can be added to the same project afterwards.
The prompt to paste
Sign in to the AI app builder with a Google account, create a mobile app project, and paste this with your own menu:
Pasting your real menu matters more than anything else in the prompt. The agent uses it as seed data, so the first preview already reads like your restaurant rather than "Item 1", and you can judge the layout on real dish names and prices.
What you get in the first minutes
The agent writes the app in React Native, sets up the hosted backend (database, sign-in, file storage on the platform's servers) and shows the customer app in a phone-shaped preview beside the chat. Place a Diavola with a note, then switch to the owner login and watch the ticket appear. Mark it ready and check the customer view updates.
Then iterate by describing changes: "show the ready time estimate on the cart screen", "stamps should animate when added", "hide the pizza category before 5 pm", "add a 'call the restaurant' button on the order status screen". Each small change lands in the preview in well under a minute. Two details worth asking for early: the place-order button should disable while the request is in flight (double taps make duplicate tickets), and the kitchen view should show the age of each ticket in minutes with a colour change at 10 and 20. Both are one sentence to the agent and save you a bad Friday night.
Getting it onto phones
The kitchen phone or tablet gets the APK first: choose Download APK from the preview and install it directly, no Play Store involved. The free APK download covers a first device; the $1.49 Member plan gives unlimited builds for the kitchen device and as many test phones as you like.
For customers, put the APK download link in a QR code on the counter, on the takeaway menu and on your website. Regulars tap, allow the install once, and the app is on their home screen. When you want to be found in the Play Store, ask for a signed store build: the builder generates a signing key for the project, keeps it encrypted, and produces a signed APK plus an AAB with your own package id and an auto-incrementing version code. As of 2026 a Play Console account costs a one-time US$25 with identity verification, apps upload as AAB, and each app needs a privacy policy URL and a Data safety form; personal accounts opened after November 2023 must run a closed test with 12 testers for 14 days first. The steps are in publishing on Google Play from the US, UK or EU.
iPhone customers use the web version of the same project, published at a link on appbuilderagent.com; it runs in the browser and can be added to the home screen. A native iPhone app requires exporting the source (Member plan and above) and building it with Xcode or Expo EAS on a Mac, plus Apple's US$99 per year developer program.
What it costs
At the time of writing: the Free plan gives 500K AI tokens a month, which covers building and refining a first version like the prompt above; a free APK download is included. The Member plan is $1.49 per 30 days for 5M tokens, unlimited builds and source export. Pro is $5.72 per 30 days for 10M tokens if you change the app often. There is no per-order fee and no per-customer fee. Prices can change; check the site.
The comparison that matters for a restaurant is against the platforms and the ordering SaaS: a delivery marketplace takes 15 to 30 percent of each order, and white-label ordering services typically list monthly plans plus card processing. A commissioned custom app from an agency in the US, UK or EU runs roughly US$20,000 to $150,000 or more. With your own app the running cost is the plan, the one-time Play fee if you list it, and the card fees on whatever payment page you already use.
Notes for the US, UK, Canada and the EU
- Tips. US and Canadian pickup apps normally show a tip step (a few percentages plus custom); most UK and EU takeaways leave it out. Say which you want in the prompt.
- Prices and tax. UK and EU menus are VAT-inclusive; US menus show tax at checkout; Canada shows GST/HST and provincial tax. Ask for the right convention and the agent will apply it everywhere, including the CSV export.
- Allergens. UK and EU food businesses must make allergen information available for every dish, and many US states have similar rules. An allergen line per item (contains gluten, dairy, nuts) is a one-sentence addition and customers expect it.
- Privacy. The app stores names, emails and order history, so GDPR (EU), UK GDPR and California's CCPA apply. Ask for an "export my data" and "delete my account" button in the profile, and publish a privacy notice; a privacy policy for your app explains what it needs. General information, not legal advice.
- Payment. Contactless cards and mobile wallets dominate in all four regions. Because the app links to your existing checkout page instead of taking cards itself, that page should already work on a phone. Pay-at-pickup remains the simplest fallback.
Tip: Run one lunch service with the app and the phone line both open. Have staff use the kitchen screen for every order, including phone orders (the owner "add order" form takes ten seconds). By the end of the shift you will have a list of five changes in plain English; paste them into the chat that afternoon.
To see the shape of a finished result before you type anything, browse the food and delivery apps in the gallery. When pickup works, the natural next step is delivery to the neighbourhood, with zones, a driver login and live status, covered in the food delivery app guide. The general playbook for other kinds of small business is in an app for your small business without hiring a developer.
Frequently asked
Does the app charge a commission per order like the delivery platforms?
No. The app is yours, orders go to your own hosted backend, and the only running cost is the plan you are on (Free, or Member at $1.49 per 30 days at the time of writing). There is no per-order fee.
How do customers pay?
The app does not process card payments itself. Customers pay at pickup, or you link to the online payment page you already use (a Square or Stripe checkout link, PayPal, or your existing online ordering page). Staff mark the order paid on the kitchen screen.
How does the loyalty card work without special hardware?
Each customer has a QR code in their profile. Staff open the owner app, scan it with the phone camera, and a stamp is added. After the set number of stamps the reward appears in the customer's app and staff redeem it the same way.
Can I offer delivery too?
Yes, later. Start with pickup because it needs no drivers or zones. When it works, ask the agent for delivery zones, a driver login and live status; the food delivery guide covers that step.
Do I need to be on Google Play?
Not to start. Regulars can install the APK from a link or QR code on the counter. When you want to be searchable in the Play Store, the builder produces a signed APK and AAB and you register a Play Console account (a one-time US$25 fee as of 2026).
Build it now — free to start
Type the idea, sign in, and the agent builds it in your browser. Change anything by describing it.
Open the builder ›