WorkShock Food & Cakes

A restaurant's own ordering app, from the menu to the pickup counter.

Shock Food & Cakes is outside the area the major delivery platforms cover, so they wanted an ordering app of their own. We designed and built it, together with the screens the restaurant runs on.

Client: Shock Food & Cakes, a restaurant in Croatia
We built: The customer app, the kitchen board, the pickup screen and the backend
Our part: All of it, design included
Status: Live

A phone stands on the pickup counter, leaning against a paper takeaway bag with a 001 sticker. The app shows order 001 as ready: come to the counter and pick up your order. Behind, out of focus, the cake display and the kitchen. — The app tells the customer when to come to the counter, and the order is waiting under the same number.

Why a custom app, and not a delivery platform?

The platforms don't reach them. They wanted ordering anyway, done properly.

Where the big platforms operate, a restaurant can simply sign up. Shock Food & Cakes doesn't have that option, so the choice was their own app or no online ordering at all.

They came to us before the restaurant opened and asked for one thing: a custom app that handles the whole process well, from the order to the handover at the counter. Customers already know how ordering food on a phone works. The job was to meet that expectation and to make it fit how this restaurant runs.

What does the whole process look like?

One order, on the customer's phone, the kitchen board and the pickup screen.

The app, the kitchen board and the pickup screen all look at the same order. When the kitchen moves it on, the status changes once and all three follow.

PlacedThe customer checks out, and the order lands on the kitchen board.
ConfirmedThe kitchen accepts it, and the app shows a pickup time.
PreparingThe kitchen starts on it, and the app counts down.
ReadyThe kitchen marks it ready, and the number lights up in the restaurant.

What's in the app?

What people expect from an ordering app, in the restaurant's own name.

None of this is new to anyone who has ordered food on a phone, and it shouldn't be. Customers don't have to learn anything.

Ordering: The menu by category, extras on each item, a cart and a short checkout
Payment: By card in the app, or by card or cash at pickup
Tracking: The order's status in the app, as push notifications and as a Live Activity on iPhone
Account: Sign-in with Apple, Google or email, order history, and the restaurant's loyalty programme

The app's menu: categories with photos, then the burgers with their prices.

One menu item: the burger at 7 euros, its description, and extras, with the restaurant's rule that the first two extras are free and each additional one costs 50 cents.

Ready for pickup

Kitchen boardThursday · 11:25

Received

00311:24

Confirmed

00211:21

Preparing

99811:10

99911:13

Ready

99510:58

99611:02

00111:16

And on the restaurant's side?

A board for the kitchen and a screen for the counter.

Orders arrive on the kitchen board as tickets, and staff move each one along as they work. The customer's app and the pickup screen in the restaurant follow the ticket, so the kitchen has nothing else to update.

How much of it did Threennovate build?

All of it, designed and built for Shock Food & Cakes.

Product design: How an order moves from the customer to the counter, and every screen along the way
Mobile app: Menu, item customisation, cart and checkout, order history and order tracking, with email, Google and Apple sign-in; Flutter
Restaurant screens: The kitchen board and the pickup display; React, TypeScript
Backend: Orders and their status, shared by all three screens; Supabase, Cloudflare Workers
Payments: In-app card payments, or payment at pickup; Stripe
Notifications: Push notifications and Live Activities on iOS; Firebase Cloud Messaging
In use: Live at the restaurant