Zeplo | Multi-Sector Booking App

Zeplo is a Flutter booking application. The same project builds a reservation app for a restaurant, a cinema, a theater, a parking garage, a beach club or a coworking space — you choose which by the entrypoint you run, not by forking the source.

What changes between editions is the thing your customer selects: a table on a floor map, a seat in an auditorium, a price zone, a parking bay, a sunbed in a row, a desk or a meeting room. What does not change is everything around it — onboarding, sign in, checkout, bookings, profile and notifications are one implementation shared by all six.

It runs on bundled sample data, so there is nothing to stand up before the first build — unzip, run, and every screen works. When you want accounts and data that outlive the session, switch to Firebase with one flag on the build command: Authentication and Cloud Firestore sit behind the same interfaces the sample data uses, and the security rules, indexes and a seed script ship with the item. No screen changes, and there is no server code to deploy.

Every one of the 109 designed screens is shown there full size, grouped by edition; 46 of them are built in the app today.
Try it: the APK of the restaurant edition runs on the sample data, so you can book a table without an account or a backend.

An edition is an entrypoint plus a sector configuration. lib/main_restaurant.dart and lib/main_cinema.dart are five lines each; they hand the app a configuration object that names the booking unit, its plural, the copy around it and the sample venue it opens on. Adding a seventh industry means adding a configuration and an entrypoint, not editing screens.

That is why the shared core is worth more than the six editions: 28 of the 109 designed screens are common, so checkout, authentication, the bookings list and the notification centre have one implementation and behave identically whichever edition you ship.