RestoBooking — Restaurant Reservations on a Tablet

A working tool for restaurant administrators: manage reservations on an Android tablet, keep working without internet and synchronise changes with the server when the connection returns.

Built for the restaurant team

RestoBooking connects the restaurant’s website booking form with staff interfaces. Guests submit reservation requests online; administrators review bookings, assign tables, record notes and mark arrivals during service. The tablet application belongs at reception and in the dining room.

The administrator’s workflow

The reservation list brings together the booking time, guest name, party size, table and status. Rooms and table capacities provide the seating context. Staff can add a booking directly when a guest calls or arrives, alongside requests received from the website.

Keep working without internet

The Android application stores data locally and keeps a queue of bookings created or changed without a connection. Administrators can continue recording reservations offline. When connectivity returns, pending changes are sent to the server and the application refreshes its data.

Several tablets, one restaurant

A venue can use several tablets for its administrators. Connected devices exchange reservation data through the shared server. Each offline tablet keeps its own pending changes; those changes become available to other devices after server synchronisation. Offline work does not imply instant updates between disconnected tablets.

A refreshed view of the workflow

These portfolio visuals use the selected tablet design: reservations grouped by time, readable guest information and an explicit connection status.

The interfaces and device scenes shown here are modernised design visualisations created for this case study. They use fictional demonstration data and are not screenshots of the current released product. The product interface itself has not been changed.

Advantages

• 📱 A tablet workspace for administrators — reservation details stay close at hand during service.
• 📴 Continue recording bookings offline — changes remain on the tablet until connectivity returns.
• 🔄 Synchronise with the server — locally created and edited bookings can be sent after reconnection.
• 👥 Use several tablets in one venue — connected staff devices work with a shared reservation server.

Technologies

The Android application uses React Native, Redux Toolkit and MMKV local storage. The website booking form and web administration use React and JavaScript. A PHP backend built with Symfony and API Platform provides the shared API. The mobile code contains connectivity checks, pending-change queues and data refresh after reconnection.