One build per school
The app is built and published once per school: its name, its colours, its mark, its launcher icon and its splash screen are baked into the build, and the listing on the store is under the school’s own name.
The app the family opens is the school’s own — its name, its icon, its colours — and the first thing it does is answer the question the office is rung about at 9.40 pm: is there a bill pending?
Mirrors: the school’s own mobile app → Home · pick a school and the whole app takes its mark, name and colours
The bill the finance office approves is the bill on the family’s phone: it announces itself in the app, sits on the home screen until it is paid, and is paid there — FPX through the bank’s own page, the wallet balance first if there is one.
Mirrors: the school’s own mobile app → Home → Billing → Bill → Payment · the bill announces itself in the app; the family pays it there
The card on the home screen counts the unsettled bills and the amount still to pay. Tap it and the bill is one screen away: the parts, if the school split it, and the one that is due — the second of two here — with its own date.
Pay opens the method list the school has switched on. FPX hands the family to their bank and the app waits for the bank’s confirmation; nobody in the finance office types anything. When the payment is confirmed the bill is marked Paid and the card on the home screen is gone.
Was she in school today? What’s on this week? When is Sports Day? How did he do last term? Can I ask the teacher? One phone answers all five — and the office answers none of them.
Mirrors: the school’s own mobile app → Calendar · Timetable · Report cards · Chat · Billing · More · one phone, the five calls the office used to take
Attendance is taken lesson by lesson by the teacher who taught it, and the day view shows exactly that — present, late, or not yet marked, lesson by lesson. The week is the timetable the office published, with the room and the teacher a tap away. The calendar carries the term dates, the holidays and the events the school keeps.
A report card reaches the family on the day the school releases it, on the school’s own template. A family with two children switches between them from the app bar, and every screen follows. Parent–teacher chat is an add-on: the family writes when it suits them, and the banner says when the teacher will answer.
The app is built and published once per school: its name, its colours, its mark, its launcher icon and its splash screen are baked into the build, and the listing on the store is under the school’s own name.
The app runs on the school’s own tenant. The bill on the phone is the bill on the Finance Manager’s screen; the report card is the one the school released; the timetable is the one the office published.
A notice reaches the family and the school sees that it was delivered. Nothing in the app tells a school that a parent has read a bill, a notice or a message, and the app never claims it.
English, Malay and 中文, chosen from the app’s own language switch. The tabs, the screens and the notices follow the family’s choice; three languages are part of Core.
Book a walkthrough and we configure it on the call — your mark, your colours and a bill of your own, on the phone in your hand.