The tutoring app that runs the session, not just the booking.
A tutoring app means two different things depending on who is asking. A student or a parent means an app that teaches, or finds someone who will. A tutor means the app that runs their week: who is booked, who has paid, what was covered last Tuesday, and what happens when a student gets stuck at 10pm with nobody online. Most guides to educational app development cover the first meaning. This page covers both, because they share more than people expect: a student record, a session log, and a way to see progress.
It also covers the feature that now sits in every tutoring app pitch, the AI explain button, with a plain account of what it does in an app you build yourself: which requests it makes, what it costs the owner, and where it stops.
See what a tutoring app has to recordThe short version
One student record, one session log, and rules for money and minors.
A tutoring app needs a student record that is separate from the guardian who pays, a session log with a fixed list of attendance outcomes (because that one field decides the invoice), booking rules for recurring slots and cancellations, a payment path that follows Apple's rule for one-to-one services, and, if it explains work, an AI feature scoped to explain the step rather than hand over the answer. Students under 13 add parental consent under COPPA. The rest of this page takes each of those in turn, with the primary sources.
Three shapes
Student app, tutor app, or marketplace?
Before the fields, decide which of the three products you mean, because they fail in different places. A math tutoring app for students lives or dies on the explanation. A tutoring app for tutors lives or dies on the calendar and the invoice. A marketplace lives or dies on having enough of both sides.
| Student-facing tutoring app | Tutoring app for tutors | Tutoring marketplace | |
|---|---|---|---|
| Who opens it every day | The student, between sessions | The tutor, before and after each session | Parents looking for a tutor, tutors looking for work |
| The core record | A topic and the student's attempts at it | The session: booked, attended, covered, billed | The listing, the match and the review |
| What working looks like | The student gets unstuck and the tutor can see where | Nobody is double-booked and nobody goes unpaid | Enough of both sides that a search returns a result |
| How money moves | A subscription, usually through in-app purchase | Hourly rates or packages, by card or invoice for one-to-one lessons | A commission on every lesson |
| Hardest part to get right | Explaining without doing the work for them | Cancellation and no-show rules | Supply and demand, not software |
Try it
Which tutoring app are you actually building?
Tick what is true for you. The answer is a shape and a list of modules, not a sales pitch: one of the outcomes is to buy something off the shelf.
The shape you are describing
Tick the statements above to see the shape and its modules.
The student record
What a tutoring app has to record.
Every tutoring business runs on the same five records, whatever it calls them. The common mistake is to collapse them into one form. Keep them separate and the awkward cases (a parent paying for two children, a student moving up a level, a no-show that still gets billed) stop being special cases.
Student
The learner, and only the learner.
- Name, grade or level, and the subjects covered
- The goal: an exam, catching up, or getting ahead
- Diagnostic score at intake
- Accommodations and preferred format
Guardian
The person you actually have a relationship with when the student is a minor.
- Name, contact details and relationship to the student
- Consent on file, with the date it was given
- Billing contact, which may be a different person
- Who is allowed to see progress
Session
One row per session, whether or not it happened.
- Date, time and time zone, duration, and in person or online
- Attendance outcome from a fixed list
- Topics covered and what the student struggled with
- Homework set, the tutor's private note, and the rate applied
Progress
What the guardian is paying for.
- Assessment scores over time
- Mastery per topic, not one overall grade
- Homework completion
- The tutor's summary every fourth or fifth session
Billing
The record that has to agree with the session log.
- Hourly rate or package, and sessions remaining
- Invoice and whether it has been paid
- Cancellation fees applied, tied to the attendance outcome
- Refunds and make-up sessions, with a reason
Lock this field first
Attendance outcome should be a fixed list, never a text box, because each value has a different billing consequence. The moment a tutor can type "sort of came" into it, the invoice stops being defensible to a parent.
| Attended | Yes |
| Late cancellation | Yes, by your window |
| No-show | Yes |
| Tutor cancelled | No |
| Rescheduled in time | No |
The workflow
How a tutoring session actually runs.
The booking is the smallest part. This is the loop a working tutoring app has to support, from a parent's first message to the report that keeps them paying.
- 1
Intake
Who the student is, what they need, and who pays. Capture the guardian and the student as two different people from the first message.
- 2
Diagnostic
A short assessment or a first session that sets a baseline score. Without it, progress is a feeling rather than a number.
- 3
Recurring booking
A weekly slot, not a string of one-off bookings, with the cancellation window shown at the moment of booking.
- 4
Reminder
Twenty-four hours before, sent to the guardian for younger students and to the student for older ones, with both time zones on it for online sessions.
- 5
The session
Start, attendance outcome, topics covered, all timestamped when they happen rather than reconstructed on Friday.
- 6
The note
What they struggled with and what was set as homework. This is the note the next session opens with, and the note the explain feature reads.
- 7
Practice between sessions
A short set on the same topic, due before the next slot, with the student's steps stored rather than just the final answers.
- 8
Billing and the report
The session deducts from a package or lands on an invoice, and every fourth or fifth one rolls up into a progress note for the guardian.
Step seven is where most tutoring apps overreach. Spaced practice is its own product, and a flashcard app does that job better than a booking screen ever will, which is why the sensible version of a tutoring app either links out to one or borrows its mechanics for a single topic at a time.
The loop is worth building carefully because tutoring, done consistently, is one of the best-evidenced things in education. A 2020 systematic review from the National Bureau of Economic Research pooled the experimental studies on PreK-12 tutoring and found an overall effect of 0.37 standard deviations, with stronger effects for teacher and paraprofessional tutors than for volunteers or parents, and larger math effects in later grades. Read the NBER review. An app does not create that effect. It protects it, by making sure the sessions happen, get noted, and build on each other.
Tutor booking app
The booking rules that break spreadsheets.
A tutor booking app is where a generic booking widget starts to fail, because tutoring has rules that a hair salon does not. Six of them do most of the damage.
| Rule | What it means | What the app has to enforce |
|---|---|---|
| Availability windows | The tutor's real hours, per weekday, with buffers between sessions. | No booking inside a buffer or outside the window, checked per tutor. |
| Recurring slots | Most students hold the same slot every week for months. | One booking creates a series. Cancelling one occurrence does not cancel the series. |
| Cancellation window | Commonly 24 hours. A late cancellation is billed, a tutor cancellation is not. | The attendance outcome is set by the clock, not by whoever remembers. |
| Time zones | Online tutoring crosses them constantly. | Store times in UTC, show each person their own zone, put both on the reminder. |
| Packages | A block of sessions bought up front, sometimes with an expiry. | A balance that decrements on attended and late-cancelled sessions, with a warning before zero. |
| Group sessions | One tutor, a few students, one slot. | A capacity per slot, and a different payment rule on iOS. |
If most of your sessions are fixed weekly slots for a cohort, the calendar side of the product looks more like an app for class schedule than a booking widget, and it is worth borrowing that model: a timetable first, with exceptions layered on top, rather than a pile of individual appointments.
Payments on iOS
The Apple rule that decides how you charge
Apple's App Store Review Guidelines are unusually specific about tutoring. Guideline 3.1.3(d) says that if your app enables the purchase of real-time person-to-person services between two individuals, and it gives tutoring students as its first example, you may use purchase methods other than in-app purchase, while one-to-few and one-to-many real-time services must use in-app purchase. Guideline 3.1.3(e) goes further for anything consumed outside the app, such as an in-person lesson: you must use other purchase methods, such as Apple Pay or card entry. Read guideline 3.1.3
In practice that gives a tutoring app three lanes: one-to-one lessons can be paid by card or invoice without an in-app purchase, group sessions delivered in the app cannot, and a practice library or any other digital content is an in-app purchase. Decide which of the three you are selling before the payment screen is designed, because it changes both the code and the review outcome.
Math tutoring app
What a math tutoring app needs that other subjects do not.
Math punishes a generic tutoring app fastest, because the unit of work is not a paragraph. It is a chain of steps, and the useful information is which step went wrong.
01
Notation that renders
Fractions, exponents, roots and equations have to look like math on a phone, in a note a tutor types in thirty seconds.
02
Work, not just answers
The record of a problem is the student's steps. An app that stores only the final answer cannot show where the error started.
03
Photo in, problem out
Students photograph the textbook. The app needs to accept the photo and turn it into a problem the tutor and the explain feature can both read.
04
Error patterns over time
The same sign error in week two and week six is the real finding. Tag the mistake type on each problem so it shows up across sessions.
05
A separate answer key
The tutor's answer is the source of truth. Whatever explains a step is checked against it, never trusted to compute it.
The rule
The answer key belongs to the tutor. The explanation belongs to whatever helps the student get there.
The last point matters more as students get older. The NBER review found that math tutoring yields larger effects in later grades, which is exactly where problems get long enough for an unverified explanation to go confidently wrong.
AI tutoring app
What the AI explain button actually does.
Every AI tutoring app promises to explain. Most of the promises are vague, so here is the concrete version: what a good explain feature is scoped to do, and what happens underneath in an app you build yourself.
Scope it to explain, not to finish
- It takes the problem and the student's last step, not an empty chat box.
- It asks what the student tried before it says anything.
- It gives the next hint, then the next, and shows a full worked solution only when the student asks twice or the tutor has allowed it for that topic.
- It never grades. The tutor's answer key does that.
- It logs every exchange to the session record, so the tutor opens the next session knowing where the student got stuck.
What that looks like
How it works in an app you build yourself
In an app built with Newly, an explain button is a request from the app to a text model, made through the app's own backend on behalf of a signed-in student. There is no AI provider account or API key involved, and nothing secret ships inside the app. When you describe the feature you pick the model from a catalog filtered by text, images, audio or video; the documentation does not fix a single model and says the list changes over time, so any page that promises a specific one is guessing.
Each explanation is one metered request. It spends the app owner's credits in development and in production alike, a student is limited to 50 requests a day, and if the balance runs out the button stops working until credits are added. See the AI features documentation
That is the whole mechanism. What the model says depends on the prompt you wrote for it, which is why the scope list matters more than the model name. The chat screen itself, with its loading and retry states and how the conversation is stored, is a separate topic: adding an AI chatbot to your app covers it.
Buy or build
How much does a tutoring app cost?
Four ways to get one, with the honest trade in each. The prices are the ones on the vendor pages on the day this was written, not estimates.
| Approach | Your own session record | Booking rules yours | Explain tied to your material | Who maintains it | What it costs |
|---|---|---|---|---|---|
| Tutoring marketplace | No | No | No | The marketplace | A commission on every lesson |
| Tutor management tool | partly, custom fields inside their model | mostly, within their options | No | The vendor | TutorBird lists $16.95 a month plus $4.95 per additional tutor, checked 20 September 2026 |
| Booking widget, video call and a spreadsheet | the spreadsheet, and it drifts | the widget's, not yours | No | You, by hand | Low, until someone is double-booked |
| Custom-built tutoring app | Yes | Yes | Yes | You | From $25 a month for the builder, plus Apple's $99 a year developer membership |
TutorBird's price is from its pricing page, checked 20 September 2026, and includes a 30-day free trial. Marketplace commissions vary by platform and are not quoted here.
The honest reading of that table: a solo tutor teaching standard hourly lessons should subscribe to the management tool and get on with teaching. The build case appears when the process is the product: placement by diagnostic, packages with expiry dates, a mix of group and one-to-one, progress reports in your own format, or an explain feature that works from your own worked examples. At that point the vendor's schema is the ceiling, and teams that hit it end up building their own.
Minors
The privacy rules a tutoring app cannot skip.
In the United States, the FTC's COPPA rule applies if your service is directed to children under 13 and collects personal information from them, or if you have actual knowledge that you are collecting it from a child under 13. Personal information is broader than a name: the FTC's list includes a photo, video or audio recording of a child, which is exactly what a photograph-the-problem feature and a recorded session collect. Before collecting it you need the parent's verifiable consent. Read the FTC's COPPA compliance plan
Apple's review guideline 5.1.4 says the same thing from the other side: apps may ask for a birthdate and parental contact information only for the purpose of complying with laws like COPPA and GDPR, and must still include useful functionality regardless of a person's age.
The practical design is the one the student record section already asked for: the guardian creates the account and gives consent with a date on file, and the student's profile hangs off it. That is not a coincidence. The data model that keeps the invoice honest is the same one that keeps the app legal.
When to build your own
Building a tutoring app around your own rules.
The reason to build a tutoring app rather than subscribe to one is rarely price. It is that your intake, your packages, your progress note or your explain feature do not fit the vendor's model, and bending them to fit costs more than the subscription saves. That gap is what Newly is for: describe the student record, the session rules and the explain feature you actually run, and it builds a real native iOS app around them for $25 a month.
Publishing follows Apple's process rather than a shortcut: the build is uploaded to App Store Connect, you test it on TestFlight and submit it for review under your own Apple Developer Program membership. Two limits to know before you start: the current version does not produce Android builds you can put on Google Play, and it has no built-in payments connection, so the card or invoice step is wired by you, with the keys kept on the backend and never in the app.
Sources
Where the specifics came from.
Four things on this page come from a primary source rather than industry habit:
FAQ
Tutoring apps, answered.
A tutoring app is one of three products that share a name. A student-facing tutoring app teaches or explains, usually one subject, and the student is the daily user. A tutoring app for tutors runs the business: student and guardian records, recurring bookings, attendance, session notes, invoices or packages, and progress reports. A tutoring marketplace matches students with tutors and takes a commission. All three need a student record and some form of session log, which is why the fields on this page apply to each of them.
Start with the session log, not the booking screen.
A tutoring app earns its keep in the note after the session and the rule that decides who pays for a no-show. Get those on paper, then build the app around them in Newly.