Mobile app

The mobile app is the same product as your website — same menu, same customers, same orders — delivered as a native app on the arc theme.

#Setting it up

Mobile app in the sidebar. Configure your app name, icon, splash screen, and brand colours. The preview shows what customers will see.

#Building and releasing

Restro builds and submits the app for you. You will need developer accounts with Apple and Google in your own name — the app is published as your brand, not ours, and the stores require the business behind it to hold the account.

#Push notifications

The app notifies a customer every time their order moves: confirmed, being prepared, ready, out for delivery, completed, and cancelled. These come from the same order lifecycle events as everything else, so a status you set in the kitchen display, on the orders screen, or through the API all reach the customer the same way.

The wording adapts to the order type — a pickup customer is told to come and collect, a delivery customer is told the order left the restaurant — and it is sent in the language the customer's device is set to. Tapping a notification opens that order in the app.

Nothing needs configuring. Notifications start working as soon as a customer installs the app and allows notifications.

#What customers control

Customers manage this themselves under Account → Notifications in the app:

• Order status — on by default, and the reason most people keep the app installed.
• Offers and news — off until the customer explicitly turns it on. Marketing is tracked separately from order updates, so turning off promotions never stops someone hearing that their food is on the way.

If a customer denied notifications at the system level, the app tells them and links to their device settings.

Customers who order as a guest, without an account, still get order updates on the device they ordered from. Signing in afterwards carries that device over to their account. Signing out stops notifications on that device.

#Tracking

Browser pixels do not run in a native app. Restro sends the same commerce events server-to-server through each tracking provider's API, so your Meta and Google reporting covers app orders too. See Extensions.

#What differs from the website

Very little by design. The app supports device location for branch selection and saved payment details, and it cannot use a custom domain because it is not a website. Everything else — menu, availability rules, discounts, credit, accounts — behaves identically.