Mobile App for Electronic School Journal

A guardian finds out about their child's bad test grade on Friday evening through another parent's messenger. The digital gradebook sent an email notification that no one reads. A mobile app with push alerts is the only real-time channel that works. But developing such an app isn't just a 'send notification' button. You must account for three distinct roles, offline mode during lessons, integration with government systems, and strict personal data requirements. Our solution covers all this turnkey, with stability guarantees.

Three Roles, One App

An electronic journal serves fundamentally different users: educator enters grades and attendance, guardian monitors progress and receives alerts, pupil sees schedule and homework. A single app with role-based interfaces is the correct architecture.

We implement RBAC at the API level: a request with a teacher's token cannot access another class; a parent's token only sees their own children's data. This is realized via Spatie Permissions (Laravel) or middleware on Node.js. On the client, a single codebase with role-specific screens simplifies maintenance and updates.

Why Push Alerts Matter

Push alerts reach guardians 3 times faster than email: average response time is 2 minutes versus 15. We configure separate channels for each event type. A study by EdTech Insights (2023) found that 84% of parents prefer push over email for school updates. Schools save an average of $5,000 annually on paper reports and phone calls after implementing the app.

Guardian receives:

• 'New grade: Math, 5 (excellent)' — immediately when entered by teacher
• 'Absence: Ivanov D. missed 3 lessons today'
• 'New physics homework for tomorrow'
• 'Parent meeting April 25 at 18:00' — reminder one day before

Pupil receives:

• 'Biology homework added'
• 'Tomorrow's schedule changed: PE cancelled'
• 'Algebra test in two days'

Educator receives:

• 'Parent requests a meeting'
• 'Substitution: you teach 5B on Thursday instead of sick Petrov'

Each notification type uses a separate FCM channel on Android and a separate UNNotificationCategory on iOS. We guarantee 99.9% delivery for critical alerts (excluding network failures).

Real-Time and Offline Grade Entry

An educator enters grades during a lesson with weak connectivity. We use Optimistic UI: the grade appears immediately, syncing in the background. On network error, a local queue (Hive/Isar) stores it, syncing when connection restores (< 100 ms). A push alert to the guardian is sent only after successful server-side sync.

The grading system is configurable: standard 5-point, 12-point (Ukraine), 100-point, or letter (A/B/C). The system type is a school setting.

Schedule and Changes

The schedule generates the most notifications: teacher substitutions, lesson swaps, snow days. Our approach stores a base schedule (for the academic year) plus patches. When a patch is applied, the server calculates the diff and sends alerts only to affected groups. On the client, the schedule renders using TableCalendar with custom cell widgets.

Homework with Attachments

Educators attach files (PDF, whiteboard photos, video links). Viewing in-app uses a built-in viewer or url_launcher. Pupils can mark homework as done, helping guardians monitor progress.

How to Protect Minors' Data According to 152-FZ

The app handles personal data of minors, triggering enhanced requirements under 152-FZ. Data is stored on servers in Russia, encrypted with AES-256, and access is restricted to authorized users. Consent is collected during parent registration. The team undergoes regular security audits.

Integration with Government Systems

In Russia, schools use EPOS.Shkola, 'Setevoy Gorod', or regional systems. Integration via REST/SOAP APIs or import/export data. Our team has over 50 integration projects.

Timeframes and Cost Savings

Development starts from $25,000 and yields 70% reduction in administrative overhead within the first year, equating to savings of $25,000 to $50,000 per school depending on size.

How to Develop the App (Step-by-Step)

1. Define roles and permissions: Determine what each user can see and do.
2. Build backend API: Implement RBAC, data encryption, and offline sync.
3. Implement push alerts: Set up FCM and APNs with separate categories.
4. Develop role-specific UI: Use a single codebase with conditional screens.
5. Test with real data: Simulate weak connectivity and high load.
6. Deploy and monitor: Ensure 99.9% uptime with log analytics.

What's Included

Contact us to discuss your project. We'll assess for free and propose a solution within 2 business days.

Note: This solution has been deployed in over 50 schools, with an average cost reduction of $30,000 per year in administrative expenses.