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.

Push Notifications in Mobile App: APNs, FCM, Segmentation, Rich Push

We have implemented push notifications in mobile apps for 50+ projects — from startups to enterprise with audiences of 10M+ users. An irrelevant or technically broken notification is worse than none: the user disables push or deletes the app. According to a Localytics report, push permission rejection on iOS reaches 40% in the first week — the cause is almost always irrelevance, not mechanics. Within 2 weeks after implementing quality segmentation, open conversion increases by 25–30%. Contact us for an audit of your current implementation — we will evaluate the project and propose an optimal stack within one day.

How the Infrastructure Works: APNs and FCM

APNs is the only delivery channel on iOS. Everything else (OneSignal, Braze, Airship) is a wrapper on top of it. APNs accepts requests over HTTP/2, authentication via JWT token (p8 key) or certificate. JWT is preferable: one key for all apps in the account, doesn't expire annually unlike the certificate. For more details, see the official documentation.

A critical point: APNs distinguishes apns-push-type — alert, background, voip, complication, fileprovider, mdm. An incorrect type on iOS 13+ causes background notifications not to wake the app. We've seen projects where content-available: 1 was sent without apns-push-type: background — the app didn't receive silent push on some devices, and the team spent a month looking for an 'app bug'.

FCM on Android works through Google Play Services. For devices without GMS (Huawei, part of the Chinese market), Huawei Push Kit or a direct WebSocket is needed — a separate task. FCM supports data messages (handled in onMessageReceived) and notification messages (the system displays automatically if the app is in the background). Mixing them requires caution: if the notification block has a click_action but the deep link is not registered in the app, tapping the notification simply opens the main screen without navigation.

Why Segmentation Is the Foundation of Effective Push Notifications?

Sending to everyone indiscriminately quickly exhausts user loyalty. Personalized messages are clicked 3 times more often than bulk ones, and proper segmentation reduces churn by 25% (on one project it brought significant additional revenue per quarter). The cost of setting up segmentation in OneSignal or a custom backend depends on the complexity of filters.

Proper segmentation is built on several levels.

Topics are for broad categories: 'new promotions', 'order status updates'. User subscribes via FirebaseMessaging.getInstance().subscribeToTopic("orders"). Simple, but no flexible filtering.

Attribute-based segments — via OneSignal, Braze, or custom backend. We store in the user profile: language, device type, last activity, LTV segment. Notification goes only to those with last_active < 7_days and plan = premium. OneSignal allows building such filters in the interface without code.

Personalized — by specific device_token. It's important to store tokens correctly: the token updates on app reinstall, restoration from backup on a new phone, or resetting settings. On iOS, use UNUserNotificationCenter + didRegisterForRemoteNotificationsWithDeviceToken, save to backend on every launch, not just the first. Otherwise, after 3 months 30% of tokens in the database are outdated.

What Is Rich Push and How Does It Boost Conversion?

A standard notification with title and text is clicked less often than a rich push with image and action buttons — by 3 times. But implementing rich push is a separate task on each platform.

On iOS, rich content requires UNNotificationServiceExtension (to modify payload) and UNNotificationContentExtension (custom UI). The extension runs in a separate process with limited time and memory. If the extension crashes or exceeds the timeout, the system shows the original payload without media. A typical mistake is trying to load an image over HTTP (not HTTPS): ATS blocks the request, the extension silently fails, and the user sees a notification without an image.

On Android with API 26+, notifications are tied to NotificationChannel. If the channel is created with IMPORTANCE_LOW, sound and vibration are unavailable. Different notification types (transactional, marketing) should be in different channels so the user can disable marketing without losing order notifications. BigPictureStyle, MessagingStyle, InboxStyle are templates for expanded notifications. MessagingStyle with Person and avatars is the best choice for chats.

How to Track Delivery and Conversion of Push Notifications?

Sending a notification is half the work. It's important to know: was it delivered, opened, and did it lead to a target action.

FCM returns a MessageId on send, but does not guarantee a delivery callback — by design. For open tracking, custom logic is needed: on notification tap in onMessageReceived or via getInitialNotification() / onNotificationOpenedApp (OneSignal SDK), send an event to analytics with notification_id.

OneSignal provides built-in delivery and CTR analytics. For more detailed analysis — integrate with Amplitude or Mixpanel via webhook on open events. The budget for such a dashboard varies depending on event volume.

How We Implement Push Notifications: Typical Process

1. Audit current implementation — check token storage, update handling, notification types.
2. Design architecture — choose transport (FCM + APNs), segmentation layer (OneSignal/Braze/custom), personalization method.
3. Implementation — write registration code, inbound handling, rich push, deep linking.
4. Testing — send test campaigns, verify delivery on different devices, simulators, regions.
5. Monitoring and analytics — set up dashboard, open and conversion events.
6. Documentation and training — hand over operational materials to the team.

Typical stack: FCM + APNs at transport level, OneSignal or Firebase Notifications Composer for segmentation, custom backend for personalized event-based notifications. For large apps with >1M users, OneSignal has pricing limits — then we use Braze or a custom implementation on AWS SNS.

Timelines depend on complexity: basic FCM+APNs integration with transactional notifications — 1–2 weeks. A full system with segmentation, rich push, analytics, and A/B testing — 4–8 weeks. Order an audit of your current push infrastructure or get a consultation on implementing push notifications in your mobile app — we will contact you within a day and provide an accurate estimate.