Meow Management

The Problem

Small restaurant teams often track inventory counts, shift notes, and finances across disconnected paper logs, group texts, and spreadsheets. Meow Management centralizes those three things into one mobile dashboard, so a shift lead can check stock, log a note, or review finances from the same app.

My Role

I built Meow Management's mobile client and backend schema: the Expo/React Native app, the Supabase database and row-level security policies, and Miso, the in-app chatbot that searches inventory and notes.

Key Technical Decisions

• Supabase Postgres with row-level security. Inventory, tasks, and finance data is scoped per account at the database layer through RLS policies, not just filtered in the UI, so a client-side bug can't leak another account's data.
• Firebase for auth, Supabase for data. Firebase handles account sign-up and session state while Supabase, backed by its own migrations and edge functions, owns the operational data — keeping authentication and application data as separate, purpose-built concerns.
• Dedicated tabs instead of one dashboard. Inventory, tasks, finance, and a management log each get their own tab backed by their own Supabase tables, so day-to-day updates map to how a shift actually works instead of competing for space on one screen.
• Miso as a scoped chatbot, not a general assistant. The in-app chatbot is built as a fast search layer over existing inventory and notes data, so it only ever answers questions the underlying data can actually support.

Challenges & Solutions

Low-stock alerts needed to be useful without turning into noise. They're scoped per item on the inventory tab, so a manager sees a flag when something is actually running low instead of getting alerted on every stock change.

Status & What's Next

Meow Management runs end-to-end against a live Supabase backend, with full CRUD across inventory, tasks, and finance, chatbot-assisted search, and an invite flow so more than one team member can access the same restaurant's dashboard.