WebSocket

Backend

WebSocket is a persistent two-way connection between browser and server; I use it to show changes live without reloading the page.

How I use WebSocket

The server pushes new data the moment something changes, instead of the page asking over and over whether there's anything new.

For you, that means guests, the kitchen and drivers see the same state at the same moment: a new order shows up on screen immediately and statuses change without anyone hitting refresh. There's less confusion, and the server doesn't waste resources answering the same question again and again.

In practice I use Supabase Realtime: the page subscribes to changes in a table and shows them as they arrive, for order status, the kitchen screen and the driver's position on the map. I make sure each user only receives changes they're allowed to see, and that the current state reloads when the connection drops on a weak signal.

I choose WebSocket when several people need to see the same state at once, such as orders, bookings or chat, together with Next.js and Supabase. For data that rarely changes, a normal page load is enough.

Used in: BrzoJelo.

Projects using WebSocket

Websites and apps I built where WebSocket was used.

  • BrzoJelo — QR Ordering, Kitchen and Delivery for Restaurants

    BrzoJelo — QR Ordering, Kitchen and Delivery for Restaurants

    My own platform for small restaurants and fast food. A guest scans the QR code on the table and, with nothing to install, browses a menu with photos, allergens, sizes and extras, orders and follows the order status live. The kitchen works from a screen with cards by status, and staff sign in with a PIN. For delivery there is a driver panel, GPS tracking on a map, chat and a photo as proof of delivery. From the admin panel the owner manages the menu, QR codes for every table, stock, analytics with PDF and CSV export and an activity log. The core is free and other modules are switched on as needed. Built with Next.js and Supabase.

Frequently asked questions about WebSocket

What is WebSocket?

WebSocket is a protocol that keeps an open two-way connection between the browser and the server, so either side can send data at any time. It's used for chat, notifications, order tracking and anything that needs to update live.

What's the difference between WebSocket and a regular HTTP request?

With HTTP, the browser sends a request, gets a response and the exchange ends, so it has to ask again to learn about anything new. WebSocket keeps the connection open, so the server announces a change the moment it happens, without repeated requests.

Can you build live order tracking?

Yes. In BrzoJelo, guests follow their order status live, the kitchen sees new orders on screen without refreshing, and the driver's position appears on a map, all through Supabase Realtime.

How much does a website or app built with WebSocket cost?

It depends on the type of project: Digital QR Menu from €40. These are starting prices; you get the final price and timeline in a written offer by email.

All skills →