Wootera Digital Technologies Logo
Menu

Zonno Dancea system for dance schools

Dance schools usually run their schedule, class and workshop sign-ups, passes and payments in spreadsheets, messages and on paper. Zonno puts it into one system with a student app on the phone.

← All case studiesProduct website: zonno.app ↗

Who it is for and what it does

Zonno is our own product for dance schools and instructors. The school keeps its schedule of regular classes and one-off workshops in it; students sign up themselves – in the app or through a button on the school's website, an e-mail address is all they need.

The system tracks passes (entry and time based), shows who has paid and who owes, can send a push reminder before a class (once the school sets it up) and gives an overview of income, expenses and instructor pay. Attendance is checked in with a QR code.

Students get a mobile app for iOS and Android with the current schedule and their passes. App and administration are in Czech, English and Hungarian; prices in CZK, EUR, HUF and USD.

What it does

  • Schedule of classes, workshops and events; courses carry levels that students choose by
  • Online sign-ups in the app or through an embedded button on the school's website
  • Entry and time passes with validity tracking, extended when the school cancels a class
  • Finance overview: payments, debts, income and expenses, instructor pay
  • Push reminders before classes (set up by the school) and QR-code check-in
  • Room renting
  • Student mobile app (iOS, Android) with push notifications
  • School registration with a 30-day trial, Stripe subscription including plan changes

How it is built

  • Backend: Node.js and Express, Microsoft SQL Server via Sequelize, scheduled jobs (reminders, closings)
  • Web app for schools and students plus a separate admin: Next.js and React, Tailwind CSS
  • Mobile app: React Native (Expo) for iOS and Android, built with EAS, push notifications
  • Payments and subscriptions: Stripe (Checkout, customer portal, proration on plan changes)
  • E-mail via SendGrid, files in S3, PDF generation, Sentry error monitoring, runs in Docker
  • Marketing site zonno.app: TanStack Start with server-side rendering, deployed on Cloudflare

How long it took

  1. April 2026

    Development starts. The backend grew out of the proven cleanQR base (sign-in, payments, e-mail), so the first weeks went into the schedule and passes, not infrastructure.

  2. Spring–summer 2026

    Web app for schools and students, Expo mobile app, release to the App Store and Google Play, Stripe integration.

  3. September–October 2026

    School administration, onboarding and plan switching, Hungarian version, marketing site in four languages.

  4. As of October 2026

    Over 600 commits across four repositories (backend, web app, mobile app, admin). Development continues.

Facts come from the product repositories' history and zonno.app; we do not publish customer counts.

What we learned

  • Starting from an existing base paid off: sign-in, payments and e-mail were not built twice, and the first usable version took weeks.
  • A mobile app is worth it only where the user opens it every week – for students with a schedule and a pass, it is.
  • Multiple languages and currencies are cheaper to design in from the start than to bolt on later.

Want something similar for your company?

Development at a rate per month of work, smaller jobs proportionally less, the code is yours, running is optional.

Software development subscription