Back to Archive

Grace Restaurant OS

Year2025
TypeEngineering
Grace Restaurant OS

The Challenge Grace Tasty Bites was suffering from operational friction. Staff scheduling was manual, payroll calculations were prone to human error, and the ordering process was disconnected from the kitchen. The objective was not just to "build an app," but to engineer an operating system for the restaurant that could function without constant internet connectivity. The Architecture Built entirely in Kotlin, the system relies on a robust SQLite relational database to handle the complex web of dependencies: linking Users to Roles, Shifts to Staff, and Orders to Inventory. Role-Based Architecture: A single codebase serves three distinct interfaces based on the user's role (Admin, Employee, Customer). Automated Payroll: I engineered a logic layer that aggregates shift logs to calculate monthly earnings automatically, eliminating hours of manual administrative work. File I/O & Reporting: The app utilizes Android's File Storage APIs to dynamically generate and export PDF invoices and receipts, bridging the gap between digital data and physical records. Key Takeaway This project moved me beyond simple UI development into the world of Data Persistence. Designing a schema that could handle many-to-many relationships without data redundancy taught me the importance of architectural planning before writing a single line of code.

Technologies

Next.jsTypeScriptTailwind CSSSupabase

The Brief

A native Android app that unified three distinct user roles; Admin, Staff, and Customer, into a single offline-first application, replacing manual paper workflows with automated payroll and digital ordering.