01
Order in a few taps
A menu by category, with the options people actually ask for: size, milk, an extra shot, syrup. The price updates as they choose.
Live demo · Mobile app
Try a mobile app before you build yours
Order a coffee, collect points and track your order in a mobile app made for a fictional café. Use it in the phone on screen, or scan the code to open it on your own phone.
See it the way a customer would, without the website around it.
Café Bruma is a fictional café chain in Quebec City. The menu, prices and payments are made up, and no card is ever charged.
What you can try in this app
Every screen works. Order a drink, pay, wait for the notification and spend your points, the same way a customer would.
02
Pickup at the right café
The customer picks a branch and a time, as soon as possible or a set slot. On a real project, the order shows up on a tablet or the point of sale at that branch.
03
Apple Pay, Google Pay or a card
Each phone shows its own wallet button. In a real app, payment goes through a provider like Stripe, and card numbers never touch your servers.
04
A heads-up when it’s ready
The order goes from received to preparing to ready, and the app tells the customer. On a real phone, that is a push notification, even with the app closed.
05
Loyalty without a paper card
Points on every dollar, a stamp card for drinks, and rewards the customer applies to their order in one tap.
06
In French or English
The customer switches the language inside the app, turns notifications on or off, and repeats a past order from the home screen.
Who an app like this is for
Cafés and restaurants
Order ahead, skip the line, and bring regulars back with points. Fewer phone orders to take, and a counter that moves faster at rush hour.
Shops and retailers
In-store pickup, a loyalty card that lives on the phone, and offers you can send to customers who already buy from you.
Gyms and service companies
Class or appointment booking, memberships, reminders and payments in one app your clients keep on their home screen.
How we build it
One codebase for iPhone and Android, published under your name in both stores.
- 1
Map the main flows
We start with the three or four things your customers do most, like ordering, paying and collecting points, and design those screens first, in French and English.
- 2
One codebase, two stores
For an app like this one, we write a single TypeScript codebase and ship it to iOS and Android with Capacitor, with native plugins for push notifications and payments. When a feature needs deeper native work, we write that part natively.
- 3
Connect your systems
The menu, prices and branches come from your point of sale or a back office your team edits. Orders go to the right branch and payments to your processor.
- 4
Publish and keep it running
We prepare the store listings, screenshots and privacy details, go through Apple and Google review, then ship updates on a steady schedule.
What is under the hood
- One TypeScript and React codebase, packaged for iOS and Android with Capacitor
- Push notifications through Apple and Google, sent when an order changes status
- Apple Pay, Google Pay and cards through a payment provider such as Stripe
- Menu and loyalty card saved on the phone, so the app opens fast with a weak signal
- Interface that follows each platform: tab bar, headers, buttons and payment sheet
- French and English, with the customer’s choice saved on their account
- Order status sent live from the back office to the app
- Store listings, privacy labels and review for the App Store and Google Play
Questions about mobile apps
Montreal · Quebec City · Canada
We build the product. You ship the outcome.
Websites, apps, portals, and mobile — one studio, working software.