School Techy
School Techy
Modules
AdmissionsStudent InformationFees & FinanceAttendanceExaminationsTimetableTransportHostelLibraryHR & Payroll
Solutions
Colleges Universities Coaching institutes Mobile app Integrations
Company
Pricing All features About Case studies Security Resources Blog Partners Contact Sign in
Start free trial
Mobile · Android & iOS

School mobile app: one app, four genuinely different jobs

Parents, students, teachers and administrators each get the app for their role — not one app with the other three roles greyed out. The same permission rules apply, because a phone is not a softer door.

Start a 14-day free trial
Included in every plan · Your school’s branding on Enterprise
The School Techy dashboard, which the mobile app reads the same data from
Built for Android iOS Low-bandwidth networks Shared family phones Regional languages

What ships on the phone

The same rules as the browser, enforced in the same place.
4
Role views: parent, student, teacher, administrator
2
Platforms: Android and iOS, from one codebase
0
Permissions relaxed for the phone
15s
For a teacher to mark a section’s attendance
Parents

The three things a parent opens an app for

Fees, attendance and results. Everything else in a parent app is secondary, and building it as though the notice board were the main feature is how school apps end up uninstalled.

  • 01 Fees due, and paid from the appBroken down by head and instalment with due dates, paid through the gateway, with a receipt they can download afterwards. This is what stops the office fielding the same call twice.
  • 02 Attendance, including this morningThe absence alert arrives as a notification and the register is there to check. Leave is applied for in the app, with dates and a reason, and approval comes back.
  • 03 Report card when it is publishedNot before — the school releases results on a date it chooses, and then every parent has it at once.
  • 04 Bus, notices and messagesWhere a tracker is fitted, the bus’s position and a stop-reached alert. School notices and messages from the class teacher.
  • 05 Two children, one appA guardian with children in different classes sees both, correctly attributed. Two guardians each have their own login rather than sharing a password.
School Techy mobile app School Techy mobile app
Students

Today, on a phone, between periods

A student’s app is a schedule and a to-do list, not a portal. The useful question is “what have I got now and what is due tomorrow”, and that is what the first screen answers.

  • 01 Today’s timetable with the next period highlighted Including a substitution arranged that morning, because the timetable and the app read the same grid.
  • 02 Homework and classwork Set by subject with a due date, with attachments where a teacher has added them, and submission where the school uses it.
  • 03 Marks and results Internal assessment as it is entered, and the term result when the school publishes it.
  • 04 Library and exams What they have issued and when it is due; the exam schedule and their seat.
The student view showing today’s timetable and homework
Teachers

Attendance in the classroom, not in the staff room afterwards

A teacher app justifies itself with one screen: the register, marked in fifteen seconds, in the room, at the start of the lesson. Everything else is a bonus. Marking attendance at lunch produces an absence alert nobody needs.

  • 01 Their own sections only Enforced in the query. A teacher cannot open another section’s register, so there is no version of the screen that shows the wrong class.
  • 02 Present by default, exceptions tapped The common case is one action. Absent, late and half day are one tap each with an optional remark.
  • 03 Mark entry for their own subjects Within the window the exam controller opened, with per-subject maximums enforced at the keyboard.
  • 04 Homework and a message to the class Set homework with a due date; message the parents of one section without an export and a broadcast tool.
  • 05 Their timetable and their substitutions Today’s periods, and a notification when they have been assigned a substitution this morning.
A teacher marking a section’s attendance on a phone
Administrators

The day’s numbers, and what is waiting for you

A principal or administrator wants two things on a phone: today’s figures, and the queue of approvals holding somebody else up. Both are on the first screen, and the figures are the same ones the browser shows because they come from the same query.

  • 01 Today: collection, attendance, absentees, admissions The four numbers that describe a school day, live rather than as of last night.
  • 02 Approvals in one queue Leave requests, gate passes, concessions and expense approvals — the things where a delay of a day is somebody else’s problem.
  • 03 Ask Buddy in plain words “Fee dues per class”, “which students have low attendance”, “top 10 students of class 5”. Answers come from your own data, with the window and campus stated.
  • 04 Campus switching for a group A group administrator moves between campuses; a branch administrator cannot, because the scope is in the query rather than in the picker.
The administrator view with the day’s figures and the approval queue
Permissions

The phone is not a softer door

This is the part of a school mobile app most worth asking about, because it is where the mistakes are. Permissions here are checked in the same place for the API as for the browser — one rule, not two implementations that drift.

One permission model
The mobile API gates on the same {module}.{verb} permissions the browser does. There is no separate mobile role list to fall out of step — there used to be three copies of one, and consolidating them closed six privilege escalations.
Scope in the query
A teacher’s sections, a parent’s children and a branch admin’s campus narrow the query itself. There is no request that returns the wider set and relies on the app to hide it.
Token abilities
App logins issue scoped tokens rather than a session that can do anything. A parent’s token cannot call a staff endpoint even if the request is hand-crafted.
Two-factor where required
If your school requires 2FA for staff, the app requires it too — including enrolment before a token with staff abilities is issued.
Audited the same way
An action taken on a phone lands in the same audit log with the same actor, so “who marked this attendance” has one answer regardless of device.
Built for real networks
Designed for patchy mobile data: small payloads, cached lists, and a marking screen that does not lose a register because a lift had no signal.
Rollout

Turn the parent app on last

The most common rollout mistake is publishing the parent app first, because it is the most visible part. Do it the other way round.

Staff first, for a week. Let teachers mark attendance and the office take fees while the data settles. In that week you will find the three classes whose student list was wrong in the import, the fee head somebody mis-assigned, and the two teachers who need a second walkthrough. All of those are ordinary. All of them are much less ordinary once four hundred parents can see them.

Then one class of parents. Pick a class whose parents will tell you honestly what was confusing. Give them a week. Fix the wording, not the software.

Then everybody. By this point the absence alert is arriving at the right time, the fee balances are right, and the app is doing the thing it is good at, which is making the school look organised. A rollout that goes the other way round gets a reputation in a WhatsApp group before it has had a chance to work, and that reputation is much harder to fix than any of the underlying problems were.

Questions

Mobile app questions

Something not answered here?

Is the app included or charged separately?
Included in every plan, for every role, with no per-user or per-parent charge. On Enterprise the app can carry your school’s own name, icon and colours and be published under your own developer account, which is a one-time build we quote in advance.
Do parents need to install anything to pay fees?
No — the web portal does everything the app does, on any browser, including online payment. The app exists because notifications are what make absence alerts and fee reminders work, and a browser cannot deliver those reliably.
What if two parents share one phone?
Each guardian has their own login and both can be signed in on different devices; on a shared phone they switch accounts. We deliberately do not use one shared family password, because a guardian’s login is also how consent for a gate pass or a leave request is attributed to a person.
Does it work on an older Android phone?
Yes, and it is built for that rather than for a flagship. Payloads are small, lists are cached, and the attendance screen holds a marked register through a network drop rather than losing it. This matters because the teacher marking attendance is often the person with the oldest phone in the building.
Can a teacher see students who are not theirs?
No. Section scope is applied in the query, so a request for another section returns nothing rather than returning data the app then hides. The same rule covers marks, remarks and parent contact details.
Are there separate apps to install for each role?
One app. It recognises the account and shows the right view, which matters for a teacher who is also a parent at the same school — they see both, correctly separated, without two installs and two passwords.
Do you support regional languages?
A regional language UI pack is available, and the parent-facing text is the part that matters most for adoption. Tell us which languages you need on the call, because coverage varies by language and we would rather be specific than say “yes, all of them”.
What happens to the app if we stop subscribing?
It stops working, like the web application does — but your data is still yours and exportable in open formats at any time, by you, without asking us. Access pauses; nothing is deleted.
Next step

Put the app in a real teacher’s hand

The fastest honest test is one class, one register marked on a phone, and one absence alert arriving. Twenty minutes, and you will know whether teachers will use it.

  • No card required
  • Your data stays yours — export any time
  • Setup help included

No card required. We reply within one working day and never share your details.