QR-Connect banner

QR-Connect

3 devlogs
6h 40m 36s

QR Connect is an opensource ordering system designed for local restaurants. It enables customers to scan table-specific QR codes, browse a digital menu, and place orders directly from their smartphones. Kitchen staff receive real-time notification…

QR Connect is an opensource ordering system designed for local restaurants. It enables customers to scan table-specific QR codes, browse a digital menu, and place orders directly from their smartphones. Kitchen staff receive real-time notifications and manage orders through a dedicated dashboard.

This project uses AI

used ai generated images as placeholders, components placements and notifications in adminside.

Demo Repository

Loading README...

Pragnyan Ramtha Adapa

I implemented qr code generators for kitchen staff would be able to generate QR codes that are specific to some tables

the users at those tables scan them.

there was a bug, and now the client side website also has call waiter button that now does send a notification and a banner to the backend.

the waiters can now know which table they should go to.

Also, i fixed a bug where the additional notes field doesn’t seem to send anything to the kitchen staff.

Changelog

Attachment
Attachment
Attachment
Attachment
0
Pragnyan Ramtha Adapa

Shipped this project!

Hours: 6.0
Cookies: 🍪 9
Multiplier: 1.5 cookies/hr

I built a opensource QR code menu ordering system.

The most painful part was connecting the clientside with the kitchen side !

Since this event is about cooking something that’s tasty, why not help out some restaurants ! or people who wanna help them !

Pragnyan Ramtha Adapa

worked on the kitchen and admin dashboard, since i already planned it all out in the backend, it wasn’t a big problem now.

but it does work now:

order something here: https://qr-cart-six.vercel.app/menu/1 (please use phone view)
and you would be able to see it here: https://qr-kitchen.vercel.app/ (use the correct pin)

dont actually use this project as a production deploy, maybe dm me and ill put out a verison for you !

Having the client and admin apps in separate repos was becoming a massive headache for shared types,

so I just merged them into a proper monorepo using git subtrees (atleast learnt something new).

It feels so much cleaner having everything under one roof.

I also reorganized the Firebase rules into their own folders.

It’s finally starting to look like a professional project instead of two separate experiments.

Attachment
Attachment
Attachment
Attachment
0
Pragnyan Ramtha Adapa

Used web sockets for sync between the customer’s phone and the kitchen tablet.

Seeing a “New Order” pop up on the KDS the exact second I tapped checkout on my phone was such a pain to implement 😭!

Used Firestore listeners to keep things easy.

Still fighting some Tailwind layout issues on smaller screens, but the core flow is solid.

im thinking to build a toggle so the chef can kill items if they are out of stock. No more disappointed customers ordering sold-out pasta!

Changelog

Attachment
Attachment
0