
BillBite: Group Meal Ordering & Bill Splitting
Role: Product, UX/UI and Development (solo)
Stack: Next.js, Tailwind CSS, Supabase (PostgreSQL, Auth, Row Level Security)
Status: Built for and used by my office team.
Overview
BillBite replaces the spreadsheets and chat threads our office used for group lunch orders. I designed and built it solo, from the interface to the PostgreSQL schema. Nearly 30 colleagues used it every day for a year, until I left the company.
The problem
Group orders meant confusion over who ordered what, manual maths for tax and delivery, and awkward repayment chases between coworkers.
How it works
A host creates an order for a restaurant and shares a unique link.
Colleagues join the link as signed-in users or as guests, with no account needed.
Each person picks their own items. Tax is split in proportion to what they ordered, and delivery is split evenly, so everyone sees exactly what they owe.
The host’s upfront payment is recorded. Participants mark when they’ve paid back, and the host confirms. The app tracks repayment but doesn’t process money.
Engineering decisions
Guest access without sign-up. Guests join through anonymous Supabase sessions, so the first order takes seconds, which suited a lunchtime tool. Anonymous users get a real identity, so the same security rules apply to them as to everyone else.
Database-enforced security. Row Level Security scopes access by role. Triggers stop participants editing host-only fields like payment confirmation, and a controlled function lets people join an order by link without browsing anyone else’s.
Relational data model. A reusable restaurant and menu catalogue feeds orders. Each participant’s selection and fee share lives in a per-person contribution record.
Separate creator and host roles. One person can set up an order while another hosts it and pays upfront.
Integrity in Postgres. Constraints keep payment records consistent, whatever the front end does.
Outcome
Nearly 30 users relied on it every day for a year. It stopped being used when I left the company, since it was tied to that team’s workflow.
Reflection
Designing for coworkers meant balancing security with speed. The fewer steps between “I’m hungry” and “my item is added,” the more people used it, and guest access was the clearest example.
0 likes · 23 views · Aug 19, 2025
A simple web app that turns messy office lunch orders into smooth, fair payments.
Timeline
Jun 1, 2025 - Aug 19, 2025