Case study · Food delivery

Lunch ordered by teachers, delivered by riders.

A food ordering platform with a customer app, a rider app, restaurant menus, payments and an admin that sees the whole day.
Client
TEACHERS LUNCH
Sector
Food delivery
What we built
Customer app, rider app, restaurant and admin web, API with payments.
Platform
Two Flutter apps, Next.js web and admin, NestJS API with Stripe and Twilio.

In short

Teachers Lunch connects restaurants to staff who cannot leave the building at lunchtime. Orders flow from a menu to a cart to a rider's map, with payment, chat and notifications handled in the same API, and an admin panel with analytics for the operator.

The brief

Four parties, one lunch hour.

Customer, restaurant, rider and operator each see a different slice of the same order, and all of it has to happen before the bell.

What had to be true

  • Menus and carts that are quick

    Restaurants, categories, menus, favourites and a checkout with saved addresses and cards.
  • Riders with a route

    A rider app with order lists, details, map directions and chat.
  • Payments and messages handled

    Card payments with webhooks, SMS via Twilio, push notifications and in app chat.
  • An operator who can see it all

    Admin with analytics, broadcasts, FAQs and feedback.

What we did

We built the order as one object that four apps look at.

Each app shows the state it needs; the API keeps the truth.
01

Customer flow tuned for speed

Dashboard, favourites, cart and checkout with stored addresses and cards, because lunch is a repeat purchase.

Reorder in a few taps.

02

Rider app with directions

Order list, order detail, map directions and a chat thread with the customer.

The rider knows where and who.

03

Operations in the admin

Analytics, global categories, broadcasts and feedback so the operator runs the service day to day.

No developer in the loop.

What changed

From menu to delivery without a phone call.

What the platform covers end to end.

2

apps: customers and riders

Paid in app

cards with webhook confirmation, SMS and push updates

Live

analytics and broadcasts for the operator

Technology

What this was built with.

Chosen to fit the problem and the team who owns it now.

01Mobile

  • Swift
  • Kotlin
  • Flutter
  • React Native

02Web

  • React
  • Next.js
  • TypeScript
  • Node.js
  • Laravel
  • WordPress

03Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5verified reviews on Google