personal / July 2026 to present
Restaurant QR Ordering System
A restaurant workflow spanning customer ordering, kitchen, cashier, and admin views while moving toward Angular and ASP.NET Core.
Overview
A restaurant needs one flow that makes the customer order simple while giving kitchen, cashier, and admin roles the right operational view.
I am rewriting the earlier Next.js version toward Angular and ASP.NET Core, keeping parity with the earlier flow while strengthening boundaries.
Architecture and stack
The current direction uses Angular 22, ASP.NET Core 8 Web API, Supabase and PostgreSQL, with Auth, Realtime or Storage where used, and a legacy version as a parity reference.
Security and authorization
The project explores server-side repricing, database-enforced order-status transitions, JWT and JWKS validation, plus RLS and RPC protection.
Testing and verification
Local API and end-to-end checks support the rewrite. Final live migration and deployed verification are still pending.
What I directed
I define the migration direction, choose parity boundaries, integrate AI-assisted implementation, and verify critical flows.
What I learned
How frontend and backend boundaries meet around pricing, status transitions, authorization, and real operational roles.
Current limits
Active rewrite. Live migration and final deployed verification are pending, so the rewrite is not presented as fully deployed.
AI-assisted development
AI helped with implementation, debugging, review, tests, and documentation. I directed the requirements and decisions, then verified the result through builds, tests, repository review, and manual checks.
Selected evidence
Restaurant QR Ordering System
Real project material, selected for clarity. No generated product screens.
