A nursery app that tells parents the day without tiring teachers

The same questions arrive at five o'clock every evening: what did she eat, did she nap, how many toilet visits. While teachers answer them one by one in the WhatsApp group, a photo landing in the wrong chat or an “her aunt is collecting her today” message turns into both a trust problem and a liability one. And when re-enrolment season comes round, what parents have seen over the year feeds straight into their decision.

How many separate apps does this need?

  • 01

    Parent Mobile App (iOS + Android)

    The main app where parents see the daily development report, sleep and feeding logs, the photo feed, the meal menu, their tuition statement and absence requests — with access strictly limited to their own child's data.

  • 02

    Teacher and Classroom App (tablet-first)

    A floor-level app where teachers log sleep, meals, nappy or toilet changes, mood and activities with a single tap from the class list, and take photos; when the connection drops, entries are written to an offline queue.

  • 03

    School Management Panel (web)

    The administrator interface for enrolment and class management, authorised pick-up contacts, allergy and medication records, tuition instalment plans and collection tracking, announcement sending and parental consent records.

What the app includes

  • One-tap meal logging for selected children from the class list
  • Start-stop nap timer with total sleep duration per child
  • Diaper change and toilet log with nappy and formula stock alerts
  • Tagging children in a photo, then distributing it only to consenting families
  • Single-use pickup code verified at the door and logged immutably
  • Allergy card plus signed-off medication dose times
  • Fever, fall and incident log with an early-pickup call to the parent
  • Weekly menu published with allergen markings
  • Instalment plans with sibling and early-payment discounts
  • Bus boarding and drop-off roll call on the driver's screen
  • Offline queue on the tablet that syncs when connectivity returns
  • End-of-year development portfolio and a one-time downloadable archive

State of the sector

Choosing a nursery is largely a decision about trust, and parents make it on indirect signals because they cannot see their child during the day. When one school on a street sends parents a daily report, a photo feed and a check-out notification while another gets by with an evening WhatsApp message, the difference registers before price does. The real pressure point is the re-enrolment season: a parent who has been able to follow their child's day all year is no longer someone you have to win over for the next one. On top of that, when photo permissions, pick-up authorisations and medication approvals are never put in writing, a single incident leaves the school with no defence.

Metrics that matter here

  • Active parents per enrolled child — The number of parents who install the app and open it at least once a week; it shows whether communication has genuinely moved from the group to the app.
  • Daily development report completion rate — The percentage of children whose record the teacher completes before the day closes; if the screen flow is heavy, this rate drops immediately.
  • Tuition collected on time — In-app statements, reminder notifications and card payment directly reduce late payments and the manual chasing that goes with them.
  • End-of-term re-enrolment rate — The reports and photo feed reaching parents through the year are the biggest source of the visibility that drives the renewal decision.

Common mistakes in this sector

  • Giving teachers a 30-field daily form It looks thorough, but by the end of the first week nobody fills it in, parents receive empty reports and the app dies. Fields should be limited to the ones parents actually read, and entry should happen in bulk from the class list in a single tap.
  • Moving to the app without closing the WhatsApp group With two channels open at once, everyone stays in the one they know and teachers write the same information twice. Photos and daily reports should be published only in the app from day one, and the group closed after a short transition.
  • Reducing photo permission to one tick box on the enrolment form A parent may refuse social media sharing while being perfectly happy with in-app sharing. Permission types should be collected separately, be withdrawable later, and photo distribution should follow those records automatically.
  • Leaving payments out of scope An app that only shares information leaves the school's most time-consuming job exactly where it was. When instalment plans, statements, card payment and overdue reminders ship in the first release, the investment pays back far faster.

Regulation and compliance

Data processed in a nursery belongs to a child and is largely special-category: allergies, medication in use, medical reports and photographs. Under KVKK (Turkey's data protection law, aligned with GDPR), explicit parental consent must be obtained separately for each of these purposes, be withdrawable, and be stored with a timestamped record. The privacy notice is presented at enrolment; retention periods and a deletion policy for children who have graduated are defined. As data controller, the school should assess its VERBİS (the Turkish data controllers' registry) obligation and restrict access rights on servers and backups. In addition, the e-Arşiv invoicing obligation applies to tuition collection, and the registration, fee-publication and attendance rules in MEB (Turkish Ministry of National Education) private education legislation remain in force.

The real challenges in this sector

  • Several children in one frame: consent-based photo distribution

    Activity photos rarely contain just one child. Once a teacher uploads a photo, the children in the frame have to be tagged and the photo released only to parents who have given consent. If a child without consent is in the frame, the photo is either distributed with the face area masked or not published at all. Automating that decision in the app means the teacher does not have to weigh it up every single time.

  • Teachers make hundreds of entries a day; a long form means no entries at all

    A teacher records sleep, meals, toilet visits, mood and activities for 15-20 children. The screen has to support bulk actions from the class list: writing the same meal entry to several selected children in one tap, a start-stop timer for naps, and no mandatory free-text fields. Because it is used one-handed in a dimly lit nap room, touch targets are kept large.

  • Putting on record who is allowed to collect the child

    Pick-up authorisation is the riskiest point in a nursery's operation. Each child needs a standing list of authorised adults, a photo ID card and a way to grant one-off temporary authorisation. When a parent grants temporary authorisation from the app, a single-use code is generated, verified at the door and logged immutably with the time, the code and the staff member who handed the child over. Where custody restrictions apply, the second parent's access is separately limited.

  • Media weight: the cost of photos and video accumulating over a school year

    Every class produces dozens of photos a day and several videos a week. If files are stored in their raw form, storage and bandwidth costs run out of control by mid-term. Plan for server-side resizing on upload, video compression, time-limited signed links in the app, and moving older-term media to cold storage. You also need to solve how a graduating child's family receives the year-end archive as a one-time downloadable package.

  • Emergency alerts must not share a channel with activity updates

    If a fever, a fall or an early pick-up request arrives through the same notification channel as a photo from a painting session, the parent mutes everything and misses what actually matters. Notifications are split into separate channels for health, payments, the daily feed and announcements, and parents can turn each channel off individually. The health channel is sent with priority that overrides quiet hours, and read receipts come back to the school.

Required integrations

  • Tuition and instalment collection via iyzico or PayTR (Turkish payment providers) or a bank virtual POS
  • GİB (Turkish Revenue Administration) e-Arşiv integration so tuition invoices reach parents automatically
  • Collection and account reconciliation in Paraşüt, Logo or Mikro (Turkish accounting platforms)
  • Channel-separated push notification infrastructure over APNs and FCM
  • Bulk SMS provider as a fallback channel for parents who have not installed the app
  • GPS/vehicle tracking service for the school bus, or a location feed from the driver's device

Who this page is for

  • A newly opened single-site neighbourhood nursery

    The right scope here is narrow: teacher tablet, parent app and pickup authority. Payments and transport come in a later phase; the first goal is closing the parent chat group and getting families to open the app daily.

  • A crèche and day nursery that also takes children under three

    Under-threes generate far more entries: diaper changes, bottle and puree times, several separate nap windows. The scope must give this group its own form, plus logging for expressed-milk handover and storage, and an hourly summary notification.

  • A regional nursery chain with several branches

    The need shifts to consolidated management: capacity and occupancy per branch, fee and discount rules set centrally, separate role permissions for branch managers and head office, one parent account covering siblings at different branches, and staff assignment across sites.

A phased plan that splits the budget

  1. 1

    Phase 1 — Working daily-record core for one location 6-8 hafta

    Ships the teacher tablet, the parent app and the enrolment side of the admin panel: bulk meal entry, nap timer, toilet and mood logs, consent-based photo feed, authorised pickup list and door code verification. This alone lets the school close its parent chat group, which is the order that matters: parents must first get used to opening the app.

  2. 2

    Phase 2 — Payments, health records and institutional workflows 5-7 hafta

    Adds instalment plans, an in-app statement, card collection through a virtual POS, automatic delivery of the e-Arşiv invoice (Turkey's electronic invoice archive) and overdue reminders, together with the allergy and medication card, dose sign-off, allergen-marked menu, event calendar and separated notification channels. It comes second because a payment flow only pays off once parents already open the app daily.

  3. 3

    Phase 3 — Transport, archive and multi-site management 5-8 hafta

    Adds bus roll call with optional live vehicle tracking, the end-of-year portfolio and downloadable media archive, the enrolment enquiry form and waiting list, plus a consolidated panel and role permissions for several sites. It is left last because each of these only becomes meaningful once the first two phases have accumulated data.

Typical scope and timeline

Typical scope: a parent app, a teacher tablet app and a web management panel. Daily development reports, sleep and feeding logs, consent-based photo sharing, pick-up authorisation with QR check-out, allergy and medication records, announcements and an activity calendar, instalment-based tuition collection and the e-Arşiv (Turkey's mandatory e-invoicing system) invoice flow. Bus register and live vehicle tracking are added in a second phase.

Estimated timeline: 10-16 weeks

Off-the-shelf or custom build?

Topic Off-the-shelf Custom build
Speed of launch and monthly cost A ready-made nursery platform can go live the same week, with updates and maintenance included; for a single small site that is genuinely a sensible starting point. Custom development takes weeks to stand up and the cost lands up front, but no per-child or per-parent subscription line grows alongside enrolment.
Consent, pickup authority and custody rules Off-the-shelf tools usually offer one photo-consent checkbox and a fixed authorised-pickup list, which covers most schools' everyday needs. Separate, revocable consent types, automatic masking when a non-consenting child is in the frame, and restricted access for a second parent under a custody order only work when the rules are written into the system.
Accounting, virtual POS and e-invoice connection Most foreign-built nursery platforms do not support Turkish virtual POS or the e-Arşiv invoice flow; the local packages that do bring the integration ready-made. Custom work connects to whatever bookkeeping software, bank POS and discount rules the school already uses, and folds sibling discounts or mid-term enrolment into the plan generator.
Data ownership and the graduation archive When a subscription ends, exporting years of photos and development records is limited to whatever format the vendor allows; some packages do offer a decent bulk export. The database and media store sit in the school's own account, so handing a graduating family their archive package and setting retention and deletion policy under KVKK (Turkey's data protection law) stays the school's decision.

Sector glossary

Settling-in period
The first days a child attends for shortened hours while getting used to the setting. The app has to track it separately: attendance hours change daily and parents expect the most frequent updates during exactly these weeks.
Portfolio (development file)
The file where a child's work, observation notes and photos accumulate across the year. Schools use it in parent meetings and at year end, so the app is expected to build it automatically out of the daily records.
Authorised pickup person
Someone the parent has registered in advance as allowed to collect the child. Standing authorisations (a grandmother, an uncle) are kept separate from one-off permission for a single day, and the door check is made against this list.
Full-day and half-day groups
The split that drives both capacity and fees. Half-day groups have no nap or lunch entry and a different fee and transport plan, so the group type changes which daily fields appear and how the instalment plan is generated.
Aidat (the monthly tuition instalment)
The sector's word for the annual tuition split into monthly instalments — not to be confused with residential service charges. Registration fee, meals and transport are usually tracked as separate lines, and sibling or upfront discounts apply to this amount.

Frequently asked questions

Let us talk about your project

A free 30-minute call to scope it out, then an itemised quote within 48 hours.

Get a Free Quote

This page explains the problems an app must solve in this sector. We share references and comparable projects during the call.

Other sectors

All sectors →