webkoding
zeplo.webkodingtheme.comLive
Three Zeplo screens: a floor plan of tables, a cinema seat picker, and the membership tier that changes what a booking costs.Open the live demo →

No signup. Try it with a test card; the demo resets itself regularly.

The same project builds a reservation app for a restaurant, a cinema, a theatre, a car park, a beach club or a coworking space. Which one you get is decided by the entrypoint you run, not by forking the source.

What changes between editions is the thing the customer picks — a table, a seat, a zone, a bay, a sunbed, a desk. Onboarding, sign-in, checkout, bookings, profile and notifications are one shared implementation, so they behave identically whichever edition you ship.

What you get, before you pay

Everything in the box, so there is nothing to discover after checkout.

Files

  • zeplo.zip, installed from the source you build
  • Unminified source, no obfuscation
  • Changelog and sample data

Licence

  • 1 application you build and publish
  • Licence key sent by email after payment
  • GPL v2 or later

Updates and support

  • 1 year of updates and email support
  • After that the software keeps working
  • Renew only if you want new versions

Requirements

  • Flutter
  • Firebase (optional)
  1. 1
    Pick an edition

    Restaurant, cinema, theatre, car park, beach club or coworking — chosen by the entrypoint you run.

  2. 2
    Build and click through it

    Bundled sample data, so there is nothing to deploy before the first build.

  3. 3
    Wire up a backend if you want one

    Firebase Auth and Firestore sit behind the same interfaces, with rules and a seed script.

What it does

  • Six editions from one codebase, selected by a five-line entrypoint
  • 28 shared core screens: onboarding, auth, checkout, bookings, notifications
  • Floor maps, auditorium seating, price zones, parking bays, sunbed rows, desks
  • Runs on bundled sample data — nothing to deploy before the first build
  • Optional Firebase Auth and Firestore behind the same interfaces, with rules and seed script
  • Adding a seventh industry means a configuration and an entrypoint, not editing screens

What you need

  • 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 Zeplo 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.

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.

Everything else is in the Zeplo documentation, and anything it does not answer goes to support@webkoding.com.

Not quite it? Three nearby

Not ready to buy?

We will write when there is a new plugin, or a release worth knowing about. A few emails a year, each about something we actually shipped — no offers, no sequence, and your address goes nowhere else.

One click to leave, from any of them. What we do with it.