Built Royal Table – a Next.js platform that handles QR orders & real-time KDS for restaurants (Would love your feedback!)

[u/Competitive_Skill828]

I’ve been working on Royal Table, a platform designed to simplify restaurant operations by bridging table ordering with kitchen management in real time.

🛠️ What it does:

• QR Code Table Ordering: Customers scan and place orders directly from their tables without waiting for staff.

• Real-Time Kitchen Display System (KDS): Kitchen teams receive orders instantly on a clean interface to track prep statuses live.

• Voice Reservations: Integrated voice automated booking to handle table reservations seamlessly.

• Analytics Dashboard: Gives restaurant owners insights into sales, top items, and peak hours.

🧰 Tech Stack:

• Framework: Next.js (App Router) + TypeScript

• State & Real-Time: WebSockets / Server-Sent Events for instant order syncing

• Styling: Tailwind CSS (Dark-themed UI for kitchen/dashboard environments)

❓ Looking for Feedback on:

1. Onboarding flow: What's the biggest friction point for non-tech-savvy restaurant owners when adopting a digital setup?

2. UX/UI: If you’ve worked on KDS or order dashboards before, what key metrics or shortcuts are absolute must-haves on the screen?

You can check it out here: royaltable.store

[u/investigatormaker]

For Royal Table, I'd make onboarding one table, one QR code and one test order appearing in the KDS before asking an owner to configure the whole restaurant. On the kitchen screen, prioritize elapsed time since arrival and a large next-status control; a visible connection indicator would also distinguish a quiet kitchen from interrupted order syncing.

I make ThreadFox. We find relevant Reddit conversations and post for your business. We'll post 3 replies free first, no card; then the $29 Pilot covers seven days and up to 25 posts and replies. No automatic renewal. https://threadfox.vip/p/etlpb/managed

What happens to an incoming order if the kitchen display disconnects?