Mico Ang

DineEase Restaurant Operations Platform

DineEase case study covering restaurant operations, calorie-aware menus, ordering, reservations, employees, kiosks, publishing, analytics, and audit logs.

Work with me

Ordering and the work behind it.

Customers browse menus and place orders. Restaurant staff use the same system to manage those orders, reserve tables, and update availability.

The parts I work on.

These areas share restaurant and menu data, alongside order, reservation, and employee records.

Run service from one workspace

Restaurant setup, opening controls, live orders, and counter workflows share the same operational context.

  • Restaurant profile, location, media, hours, and readiness guidance
  • Independent controls for incoming orders and reservations
  • Live order feed, service states, sales cards, and fast actions
  • Counter kiosks and paired read-only customer displays

Publish menus with useful food context

Menu data stays reusable across guest ordering, counter displays, posters, and QR table experiences.

  • Manual or ingredient-calculated calories per serving
  • Price, availability, ingredient, image, category, and costing data
  • Guided poster layouts and a full-screen interactive canvas
  • Multiple displays and synchronized QR table menus

Connect discovery to checkout

Guests can find a restaurant, understand its food, apply offers, and complete an order without losing context.

  • Mapbox discovery by category, service, open state, and proximity
  • Public restaurant pages with menus, media, reviews, hours, and offers
  • Calorie-aware cart totals and item-level nutrition context
  • Pickup or delivery with card, pay-in-store, and GCash choices

Coordinate reservations and the dining room

The calendar combines guest bookings, table capacity, restaurant tasks, and service follow-up.

  • Shareable reservation flow for date, time, party size, and fitting tables
  • Capacity-aware seating that excludes tables too small for a party
  • Draggable floor-plan tables with availability and reservation states
  • Reservation outcome and task-completion follow-up

Give restaurant teams operational structure

Onboarding, attendance, leave, documents, and employee context live in one auditable staff lifecycle.

  • Invitation-based employee onboarding with profile and documents
  • Shared attendance tablets with individual employee PINs
  • Leave approval, clocked-in status, and consecutive-late flags
  • Employee profiles combining workplace, activity, and performance context

Turn service data into business decisions

Sales, order health, menu profitability, expenses, and event history make operational tradeoffs explainable.

  • Sales trends, order states, average order value, top items, and busiest hours
  • Ingredient cost, selling price, markup, revenue, and margin by menu item
  • Recurring and one-off operating expenses beside food cost and revenue
  • Searchable event logs for orders, refunds, reservations, attendance, and staff actions

Project context

  • Status: Ongoing ASTA platform. Large connected product system
  • Role: Co-founder and Technical Lead. Product and engineering leadership
  • Responsibility: Frontend architecture. Interface systems and delivery

How it's built.

Nuxt and Vue handle the interface. Django and PostgreSQL support the backend, with WebSockets for live order updates.

  • Nuxt: Application framework
  • Vue: Component architecture
  • Django: Business workflows and APIs
  • PostgreSQL: Operational data model
  • WebSockets: Live order events
  • Stripe: Payment workflows
  • Mapbox: Restaurant search and maps
  • Tailwind CSS: Responsive product styling