Zeplo documentation
One booking codebase that ships as six different industry apps.
Before you start
- Flutter installed, with the toolchain for whichever platform you ship
- An Apple and a Google developer account to publish under your own name
- A Firebase project only if you want the optional Auth and Firestore backend
- Nothing else for the first build: it runs on bundled sample data
Runs on bundled sample data with nothing to deploy. Firebase is optional, and the project would be your own.
What it does not do
- It is the customer's app. The staff side — the floor view, moving a table — is Zeplo Admin, a separate product.
- It does not include a backend. Firebase is optional and would be your project; the bundled sample data is for building against, not for running a business on.
- It does not process payments. The checkout flow is built; the provider and the store review are yours.
What is in the download
One Flutter project that builds six industry editions, with 28 shared core screens — onboarding, authentication, checkout, bookings, notifications and profile — and the per-edition pickers: floor maps, auditorium seating, price zones, parking bays, sunbed rows and desks.
Bundled sample data, and optional Firebase Auth and Firestore implementations with security rules and a seed script.
The first build
Install Flutter, then run the entrypoint for the edition you care about. Nothing has to be deployed first, which means a broken first build is a toolchain problem and not a backend problem.
Click through the whole edition on sample data before you change anything. It is the cheapest way to decide whether the flow suits your business.
If you want Firebase, create the project, apply the included rules, and run the seed script — the interfaces the app talks to do not change.
Shipping your own edition
Start from the closest existing edition rather than from the shared core. The differences between a cinema and a theatre are smaller than the work of building either from scratch.
A seventh industry is a configuration and an entrypoint. If you find yourself editing a shared screen to add an industry, that is a sign the configuration is missing something — and editing the screen will cost you the next six updates.
Publish under your own developer accounts, with your own branding.
Licence, updates and support
- One licence covers 1 application you build and publish.
- 1 year of updates, from the date of purchase.
- 1 year of email support.
- Instant download + licence key by email
- 30-day money-back guarantee
Questions this page does not answer go to support@webkoding.com. If you bought from us and cannot find your licence key, look it up here.
Common questions
Six editions — is that six codebases?
One. Which edition you get is decided by the entrypoint you run, not by forking the source, so a fix to checkout fixes it in all six. What changes between them is the thing the customer picks: a table, a seat, a zone, a bay, a sunbed or a desk.
Do I need Firebase?
No. It runs on bundled sample data with nothing deployed, and Firebase Auth and Firestore are optional implementations behind the same interfaces. Rules and a seed script are included for when you do want them.
Can I add a seventh industry?
That is the design: a configuration and a five-line entrypoint, rather than editing screens. The 28 shared core screens stay shared.
Is this the staff side as well?
No. Zeplo is the customer’s app. Zeplo Admin is the staff side and is a separate product — a React web project rather than part of this download.
Can I publish it under my own name?
Yes. It is a Flutter project you build and publish under your own developer account.