Articles · App ExamplesUpdated September 2026

A swim school app is a booking app that knows which level the child swims at.

A swim school app is a booking app until you look at what is being booked. It is a child at a particular stage of learning to swim, in a class with a fixed number of places per instructor. A slot is not free because the lane is empty. It is free if a swimmer at that level fits under the ratio the deck actually runs. That is the rule the class schedule apps built for yoga studios never had to carry.

This page covers the records a swim school keeps, what the law requires when you hold data about children, how makeups and waitlists eat a timetable, and who should be able to see which child.

See what the ratio does to one level

The short version

A swimmer has a level, and a level has a ratio.

Two facts decide whether a booking is real. Whether the swimmer is at the level that class teaches, and whether a place is left under the ratio for that level. Miss either one and you have sold a seat that does not exist, or put a nervous five year old into a stroke class.

Most people start out looking for a swimming lesson booking app, and booking is the visible half. The half that decides whether the app is any good is what it knows about each swimmer.

The record is the swimmer, not the account

One adult pays and two or three children swim. If the booking hangs off the account, every later question gets harder: which class is the younger one in, has the older one passed her level, who was absent on Tuesday. A swim class app keyed to the class can answer who is in lane three and little else. Make the swimmer the record. The account pays and gives consent. The swimmer has a date of birth, a level, a class and a history.

A level is not a label. It is a list of skills with a tick against each one, and the point of an app over a laminated card is that the list travels with the child. Instructors assess on deck, with wet hands, in the last two minutes of a lesson. If that takes more than a few taps it gets done from memory in the car park, or not at all.

Capacity is the field people get wrong. It is not a room size. It is the ratio you run for that level multiplied by the instructors on deck, and the ratio is tighter for preschool than for stroke development. Store it on the class, not in a policy document, because the booking screen has to turn away the ninth child by itself at nine at night.

Try it

What the ratio does to one level

Capacity here is not a room size. It is the ratio you run at this level, multiplied by the classes you put on. Change the ratio and the whole level moves.

8 classes needed

That leaves 0 open places, which is your makeup capacity for the week. A booking screen that only counts seats will sell the place anyway, and the instructor finds out on deck.

Makeups and waitlists are most of the work

Swim schools mostly do not sell courses. They run a standing arrangement: the same slot every Tuesday at quarter past four until the child moves up or leaves. That is one enrolment with a register attached, and modelling it as repeated bookings makes every later question awkward.

An absence turns into a makeup credit, and those rules are the most argued about thing in the building. Write yours down before you build: how long a credit lasts, how many a family may bank, whether it can only go into a class at the same level with a free place, whether credits survive a withdrawal, and whether a lesson the school cancelled counts differently from a child with a cold. Bought software has already picked answers you may disagree with.

Money follows the arrangement rather than the visit, which is why the billing side has more in common with a membership management app than with a shop. Families are charged monthly whether or not the child swam. The fields that generate phone calls are holds, the exact date a pause starts and ends, sibling discounts, and what happens to an unused credit over the summer.

The waitlist is where the growth hides. A school that knows twelve families want Thursday at five knows what to open next term. An entry worth keeping records the swimmer, the level, the days that work and the date they asked.

Who sees which child

Four groups use this app and none of them want the same screen. A parent wants their own children, the next lesson and the credit balance. An instructor on deck wants one class list, which is why a swim instructor app is a different app in everything but name. A supervisor wants the whole session across every lane, and the office wants attendance and money.

Notes that go home are the same shape of problem as a parent teacher communication app: a short note attached to a person, visible to the right adult, and kept. Photographs are where a swim school gets into trouble fastest. Apple's App Store Review Guidelines say an app that collects, transmits or can share personal information from a minor must include a privacy policy and comply with all applicable children's privacy statutes, and photos and videos are named in that list. Apple also notes that a parental gate is generally not the same thing as parental consent to collect personal data.

That leaves one rule the whole design rests on, which is a parent seeing only their child. It has to hold on the server, not in the screen that leaves the other names out. This page stops short of how you enforce it, because the answer is the same for every app that mixes several families into one class.

Apple, App Store Review Guidelines, section 5.1.4 Kids

What each way of running the register gives you

ApproachLevel and skills per swimmerRatio enforced at bookingParent books their own makeupYour makeup rules, not theirs
Paper register and a spreadsheetin the folderNoNoYes
General class booking toolNoa seat count onlyYesNo
Swim school platformYesYesYeswithin its settings
Leisure centre systemYesYessometimesNo
An app you buildYesYesYesYes

Building one around your own timetable

Swim school platforms exist and for plenty of schools they are the right answer. They stop fitting when the rules are genuinely yours: a ratio tighter than the standard, a level named something only your school uses, two pools staffed differently, a makeup policy you have defended for ten years. At that point you are either paying for the platform and keeping a spreadsheet next to it, or you are building.

Newly is an AI app builder. You describe the app in plain English, including how a credit expires and what the ratio is at each level, and it writes a real React Native and Expo project that you own, running it on a cloud simulator while it builds. It costs $25 a month and there is no free plan. It is not swim school software and does not arrive with a curriculum in it.

The limits matter more than the pitch here, so here they are plainly. There are no built-in payments, so fees keep running through the provider you already use. iOS goes out through TestFlight and App Store Connect and needs your own Apple Developer account. Android publishes to Google Play internal testing from the Deploy tab, and also builds a standalone production APK with the JavaScript bundled. Code comes out through the command line tool, and you can connect a GitHub repository you own from the Deploy tab and keep the two in step. No backend is bundled either, so where swimmer records live stays your decision to make and answer for.

Questions people ask about swim school apps

It is the app a learn to swim programme runs on: swimmers with levels and skill checklists, classes with a ratio and a capacity, a register the instructor marks on deck, makeup credits when a child is away, and a parent view showing the next lesson. What makes it its own category is that a place is only free when a swimmer at that level fits under the ratio.

Describe the way your school actually runs

Write down your ratios level by level, what happens to a credit when a child is away, and who is allowed to see which swimmer, then build the booking around those rules instead of around someone else's defaults.

Start building