Skip to main content

Cafe · Mobile app and admin dashboard

Café 8848

Customers order and collect points from their phone. Staff run the rest from a dashboard.

Café 8848 interface

Case study detail

Built with

  • Flutter
  • Next.js
  • FastAPI
  • PostgreSQL

What we covered

  • Hospitality
  • Mobile ordering
  • Drink customization
  • Loyalty points
  • Admin dashboard

The cafe runs on a phone app and a dashboard. Customers use the app to read the menu, say how they want a drink made, order it, and collect points. Staff use the dashboard for the menu, the order queue, customer records, and reward tiers. Both sit on the same database, so what a customer sees and what the counter sees agree.

The problem

Orders, loyalty cards, and stock lived in three separate places, on paper, in spreadsheets, and in the point of sale. Points were stamped by hand, so they went missing whenever a card did. Anything anyone wanted to know about the day had to be pieced back together from all three.

What we built

The customer app is Flutter, so one build covers iPhone and Android. People browse the menu, set how a drink is made, order, and scan a QR code to collect points. The dashboard is Next.js and covers the menu, the order queue, customer records, and reward tiers. Behind both sits FastAPI and PostgreSQL, holding the orders, the payments, and the points.

The result

Customers order from their phone and their points are added when they scan. Staff work from one order queue, and the menu, the prices, and the rewards are changed from the dashboard rather than by us.