Skip to content
Xavellus

The parent app is the product, and most schools buy it backwards

A college ERP can succeed on staff screens alone, because students carry phones and log in themselves. A school cannot. Primary pupils have no phones, so every digital thing a school does reaches families through a parent — which makes the parent app the part that decides whether the whole purchase worked.

6 min read

Why schools are not small colleges

This is the single biggest mistake in school software, and it is usually invisible at purchase. Vendors build for colleges first, because colleges have bigger budgets and clearer procurement. Then they sell the same product to schools with the student portal renamed.

But a student portal assumes a student who logs in. An eight-year-old does not. So every feature that depended on the student reaching into the system — seeing homework, checking attendance, receiving a notice — quietly stops working, and the school concludes that software does not help.

The functions are not different. The audience is. In a school, the person on the other end of almost every workflow is a parent, and the app in their hand is not a nice extra — it is the entire delivery mechanism.

What parents actually open the app for

Watch usage and it collapses to four things, in this order.

  • Did my child reach school today. Attendance, same morning, not in a monthly summary.
  • What do I owe and how do I pay it. Balance, and a way to pay without going to the office.
  • What did the school just tell me. Notices and messages, in a language the parent reads.
  • How is my child doing. Marks and report cards, which matter enormously but only a few times a year.

What gets built instead

Chat. Almost every parent app ships a messaging feature, and almost every school regrets it. Teachers end up on call at ten at night, conversations move off the record, and nobody can answer who said what when a dispute arrives.

Also: dashboards. Charts of a child's performance trend against the class average. Parents do not want a dashboard, they want to know whether the fee is paid and whether the child arrived.

The honest version of a parent app is small. Four things done reliably, with notifications that fire when they should, beats a feature grid nobody opens twice.

The things that decide whether it gets used

Language, first. If notices arrive in English at a school where parents read Urdu or Marathi, the app is decoration. This is worth checking on generated documents and not just the interface.

Then: does it work on a cheap Android phone on a weak connection? Parent phones are not review units. An app that needs a recent handset to load excludes exactly the families a school most needs to reach.

Then: one login, several children. A parent with three children in the school should not have three accounts, and should see all three without logging out.

And: what happens when a parent has no smartphone. There must be a fallback — SMS, or a printed notice — or those families simply stop receiving information the school believes it sent.

Where Xavellus stands on this

We treat the parent as the primary user for schools, not a secondary one. Attendance, fee balance and payment, notices, marks and report cards are the app's core, and notifications are wired to the events parents care about rather than to everything the system does.

One login covers all a parent's children. For Urdu-medium schools, documents and parent-facing screens are genuinely in Urdu — embedded Nastaliq in the PDFs and a right-to-left interface, not English with a translated menu. For Marathi and Hindi schools that is not yet true; documents come out in English, and we would rather write that down than let a medium list imply otherwise. Where a family has no smartphone, notices still go out on paper from the same record, so nobody drops off the list silently.

Messaging does exist, contrary to where the section above was heading — threads, read receipts, media, the lot. The concern in that section is still ours, though: an always-open channel changes what teachers are expected to absorb after hours, and that is a staffing policy the school has to set rather than something software decides. Worth agreeing internally before you switch it on, not after the first complaint about a message answered at eleven at night.

Keep reading

See it on your data

A demo walks through your structure, not a sample dataset.