Article6 min readUpdated
School App Design: Parent App and School ERP Screens
School app design for India: parent app UI, teacher app, attendance and fee screens, and a school ERP admin, with the flows and mistakes that matter.
Suppose a school in Krishnanagar sends a message on WhatsApp every morning: holiday notice, fee reminder, homework photo, exam date. Parents scroll through 80 messages to find one line. Teachers copy attendance from a register into a spreadsheet at night. This is the problem that school app design solves. It means planning the screens for parents, teachers and the school office, so each person finds one thing quickly and does one task without help.
A school ERP (enterprise resource planning) is the office-side system that stores students, classes, fees, attendance and exams. The parent app and teacher app are the two faces that sit on top of it.
This article covers the users, the screens, the fee and attendance flows, and the mistakes that make a school app unused.
Who uses a school app?
A school app has four users, and each one has a different level of comfort with phones. Design for the least confident one first.
- Parent: often a working adult with one shared phone. May read Hindi or Bengali more easily than English. Has two minutes to spare.
- Teacher: has 5 minutes between periods. Needs speed, not features.
- Office staff or accountant: works on a computer all day. Needs tables, filters and receipts.
- Principal or owner: wants a one-page summary of attendance, fee collection and complaints.
A common mistake is to design for the principal, who buys the product, and forget the parent, who uses it every day. If parents do not open the app, the school goes back to WhatsApp.
What are the 6 screens of a parent app UI?
The six screens are home, attendance, fees, homework and timetable, report card, and messages. Together they answer the questions a parent asks daily.
1. Home
Show the child's name and class at the top. If a parent has two children, let them switch with one tap on a photo. Below, show today's items: attendance status, homework due, new notices and any fee due. Put the most urgent item first.
2. Attendance
A month calendar with colours and also letters: P for present, A for absent, L for leave. Do not rely on colour alone, as many users are colour blind or view the screen in bright sun. Tapping a day shows the note. Add a button to apply for leave.
3. Fees
Show the total due, the due date and a Pay now button in one card. Below, list past payments with receipts. The full flow is covered in the next section.
4. Homework and timetable
Group by subject and date. Let teachers attach a photo or PDF. Parents must be able to open the file without installing another app.
5. Report card
Show marks in a table by subject, with the term and the class average only if the school wants it. Add a downloadable PDF. Keep comments from teachers in plain, respectful language. In an edtech app I designed, StudySakha, progress reports and live classes sat in one place, and the same idea applies here: one report, easy to read.
6. Messages and notices
Separate official notices from chat. A notice has a title, date and a Read marker. Let parents reply with a short message to a teacher, and set office hours so teachers are not messaged at midnight.
How should the fee payment flow work?
The fee flow must let a parent see what is due, pay by UPI and get a receipt in under a minute. Fee screens are where trust is won or lost.
- The parent sees a banner "Term 2 fee due on 10 December" on the home screen.
- They tap it and see a breakdown: tuition, transport, exam fee, late fee if any.
- They tap Pay now and choose UPI, card or net banking. UPI comes first because most Indian parents use it.
- The app opens the UPI app and returns on completion.
- A success screen shows the amount, the reference number and a Download receipt button.
- The receipt is also saved under Fees, and a copy goes to the registered mobile number.
Allow part payment only if the school allows it, and show the remaining balance clearly. If a payment fails, show a plain message: "Payment not completed. Money, if cut, returns to your account in a few days." See my guide on UPI payment UX and checkout design for details.
How do you design attendance for a teacher app?
A teacher app should let a teacher mark a class of 40 students in under a minute. Speed matters more than anything else on this screen.
- Open the class from the timetable, with today's date already set.
- Show every student as present by default, with the roll number and name in a list.
- The teacher taps only the absent students.
- A Submit button shows a summary: "38 present, 2 absent".
- Allow edit within the same day, with a record of who changed it.
- Work offline, and sync when the network returns. School buildings often have weak signals.
When a student is marked absent, the parent should get a short notification. See my notes on notification UX for push, SMS and WhatsApp for when to use each channel.
What does a school ERP admin panel need?
A school ERP admin panel needs tables that are easy to search, filter and export, because office staff do repeat work all day. Style matters less than clarity.
- Student records: admission number, class, section, guardian, contact, documents.
- Fee management: fee heads, per-class structures, concessions, dues list and receipts.
- Attendance reports: by class, by date, with absent lists.
- Exams and results: mark entry, grade rules and report card generation.
- Notices: send to all, one class or one student.
- Roles and permissions: a teacher must not see fee data, and an accountant must not edit marks.
Roles are the part most often forgotten. Decide them before drawing screens. My article on admin dashboard UI/UX design explains table and filter patterns.
What mistakes make parents stop using a school app?
Parents stop when the app is slow, in the wrong language, or full of items that do not concern them. These are the mistakes I check first.
- Only English. Offer Hindi, Bengali and other local languages, as in my post on regional language app design in India.
- Too many menu items. Six main items are enough.
- Login by email. Use the parent's registered mobile number and OTP.
- Showing every child's data in one list. Let parents switch children clearly.
- Hidden fee receipts. Parents need them for tax and school records.
- Sharing student photos without consent. Ask the school for a clear policy, and design a way to hide photos.
- Heavy images. Compress homework photos so the app works on slow networks.
How long does a school app take to design?
A school app with a parent app, a teacher app and an admin panel usually takes 2 to 4 weeks of design for a first version. The number of user roles and screens sets the quote.
My process has five stages: understand the users, map the flow, wireframe, design the interface, and prototype and hand off. For schools, mapping the fee and attendance flows with the office staff first saves the most rework. If your school or coaching centre needs a website as well, read my post on coaching institute and school website design. To plan an app, see mobile app design or write to me through get in touch.
Frequently asked questions
What features should a parent app have?
+
Attendance, fees with UPI payment and receipts, homework, timetable, report cards, notices and messages to teachers. Support for more than one child is also needed.
What is a school ERP?
+
A school ERP is the office system that stores student records, classes, fees, attendance and exam results. Parent and teacher apps connect to it.
How should attendance work in a teacher app?
+
Show all students as present, let the teacher tap only the absent ones, then submit. It should take under a minute for 40 students and work offline.
Which language should a school app use?
+
English plus the local language of the parents, such as Hindi or Bengali. Let the parent choose the language on first launch.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.