Delhi World Public School Dhar

The First Thing That Happens When You Open This App

You install the app, open it, and immediately hit a wall. The app asks for a login. No demo mode, no guest access, no preview of what the interface looks like without a school-provided credential. This is not a public utility app. This is a private communication tool built for one specific school in Dhar, Madhya Pradesh. The Play Store description makes this clear: "Other then demo mode, this app will only work with real data if your school is registered with MR Softwares."

For a parent at Delhi World Public School Dhar, this restriction makes perfect sense. The app is not meant for casual browsing. It is a direct pipeline between the school's administrative system and the parent's phone. The school runs on eSchool, a cloud-based education ERP that handles fees, attendance, library records, transport, and even online examinations. The app is the parent-facing slice of that system. Without a valid student ID and the school's registration with MR Softwares, the app stays locked. No data, no features, nothing to see.

This is a deliberate design choice. The developer, MR Softwares, based in Ujjain, has built this ERP for schools across India. The app is essentially a branded wrapper around the eSchool platform. Every feature — bus tracking, attendance alerts, homework assignments, fee payment schedules — depends on the school feeding data into the backend. The app is only as useful as the school's own data entry practices. And for a parent at DWPS Dhar, that is exactly the point.

Bus Tracking and Attendance: Two Features That Work Together

Bus tracking is the headline feature. The Play Store listing puts it first: "Know the exact location of the bus in which your child is travelling in real time on a map." This is GPS-based, pulling data from the school's transport fleet. A parent opening the app during school hours can see the bus moving along Mandu Road or approaching the Dharawara stop. The map updates in real time. The same data feeds into the attendance module. When the child steps off the bus and enters the school premises, the attendance system logs the arrival. The parent gets a notification almost immediately. Two features, one workflow: bus arrival confirms the child is on the way; attendance notification confirms the child has arrived safely.

This integration is not explicitly spelled out on the Play Store page, but the feature list implies it. The attendance module "inform[s] parents instantly about child absence." The bus tracking module shows "the exact location of the bus." Put them together and you have a safety net. A parent who sees the bus stuck in traffic and then receives an attendance notification ten minutes later knows the child made it inside. The same logic applies in reverse. If the bus arrives but no attendance notification appears, the parent has a reason to call the school.

Fees tracking adds another layer. The app shows fee schedules, paid amounts, upcoming installments, and pending dues. When the school sends a circular about fee changes or payment deadlines, it comes through the school diary module as a PDF attachment. The parent opens the attachment, reads the circular, and checks the fees section to verify the new amount. The diary and the fees module are separate but connected through the same data backend. The school enters the information once, and the parent sees it in two places.

What the Changelog Does Not Tell You

The Play Store listing has no published changelog. The "What's New" section is blank. This is unusual for an active school app. Most education apps at least mention bug fixes or performance improvements. Here, the developer has not bothered to document any changes. The version history on APK mirror sites shows a few releases: version 1.0.1, version v3modak dated April 2025, and an older v33 - Modak from July 2017. The gap between 2017 and 2025 suggests the app either went through a major rebuild or was dormant for years.

The eSchool website provides more context. The platform is described as "state of art cloud-based Educational Institution Management Software" that handles "Fees, Results, Attendance, Library, Stock, Timetable, Staff, Salary, Notifications, Scholar, Documents, Transport, online exam, Hostel." The app is one piece of a larger ecosystem. The website also mentions "Branded Apps" as a selling point: "Carry your brand into the digital world! App listing in Google Play Store with your school name and logo." This explains why the app exists under the school's name rather than as a generic eSchool parent app. MR Softwares white-labels the app for each school. Delhi World Public School Dhar gets its own branded version with its own package ID.

The changelog silence matters because it affects trust. A parent installing the app has no idea what changed between versions. Did the bus tracking get more accurate? Did the attendance notifications become more reliable? Did fees tracking break and get fixed? The developer does not say. The absence of a changelog is itself a signal: MR Softwares treats this as a mature, stable product that does not need public version notes. Whether that is confidence or neglect depends on your perspective.

The Demo Mode Restriction and What It Actually Means

Every feature list on every APK mirror site includes the same warning: "Other then demo mode, this app will only work with real data if your school is registered with MR Softwares." The demo mode exists but is not accessible from the login screen. There is no "Try Demo" button. To see the demo, a school administrator must contact MR Softwares directly. This is a sales tool, not a user feature. For a parent, the demo mode might as well not exist.

The implication is clear. This app is useless outside the DWPS Dhar ecosystem. A parent cannot download it and start using it without the school's backend integration. The school must register with MR Softwares, set up the ERP, input student data, and generate login credentials. Only then does the app become functional. This is not a criticism; it is a design constraint. The app is a custom tool for a specific community. It is not meant to scale beyond the school's own user base.

Permission requirements are not listed on the Play Store page. The app likely requests location access for bus tracking, camera access for photo uploads, and storage access for PDF attachments. But MR Softwares has not published a detailed permission list. This lack of transparency is consistent with the rest of the app's documentation: sparse, functional, and aimed at schools rather than end users. The app expects the parent to trust the school's IT setup. If the school uses eSchool, the app works. If not, the app does nothing.