Picture the tenth of the month in a school office. Parents are lined up at the counter with vouchers in their hands, the cashier is taking fees as fast as they can, and then the power goes. The UPS keeps the computer alive, but the router is off, or the mobile signal drops, and a lot of school software simply stops. The parents wait, then some of them leave, and a few won't come back this month.
Most of the schools we work with are outside the big cities, and for them this isn't a rare bad day. Load-shedding and weak internet are part of the timetable. So when we started building Skoolyte, working without internet wasn't something we planned to add later. It was one of the first things we built.
Why online-only isn't enough, and why desktop isn't the answer
A lot of school software in Pakistan is still desktop software, installed on one computer in the office. It works without internet, which is exactly why schools like it. But the records live on that one computer. The owner can't see today's collection from home, a second campus can't share the same records, and if that computer's hard disk dies, the school's backup is only as good as the last time someone remembered to take one.
Online software fixes those problems. The records are on a server, backed up, and the owner can see them from anywhere. But plain online software needs the internet for every click. When the connection goes, the counter goes with it.
What a school in Pakistan actually needs is both: records on a server where they're safe and shared, and a copy on the counter computer so the work carries on when the connection doesn't.
What to ask any software company about offline work
"It works offline" can mean almost anything. Some software only shows you old pages without internet and won't let you save. Before you choose, ask these questions, of us or anyone else, and ask to see the answers in a demo with the Wi-Fi switched off.
Which jobs actually work offline? Looking things up is easy. Taking a fee, marking attendance and entering marks are what matter.
What happens to the receipt number? A receipt printed offline can't know the next number on the server yet, so ask how that's handled and when the final number appears.
What if two counters take the same fee while both are offline? One of those payments has to be caught, not quietly counted twice.
What if the power goes while a payment is being sent? It must never be recorded twice when it's sent again.
And when something fails to send, where do you see it? If the answer is "it won't fail", be careful. Things do fail, and someone in the office needs to see it and fix it.
How we built it in Skoolyte
Skoolyte keeps a copy of your school's records in a database on the device itself, not just on our server. In the morning, or before a power cut you know is coming, the office presses Prefetch All Data, and the device has what it needs.
When the internet goes, pages show that they're in offline mode, and staff carry on. The cashier can take fees, including one payment for a whole family. Teachers can mark attendance and enter marks. Everyone can look up students, fees, classes, the timetable and results.
Each change is saved on the device's disk the moment it's made, so a power cut or a restart doesn't lose it. When the connection comes back, the device sends only what changed, which is quick even on a slow mobile connection. Every payment carries its own label, so if it's sent twice, after a dropped connection for example, the server still records it once. If two people changed the same record in the meantime, Skoolyte asks which version to keep instead of overwriting one of them. And anything the server refuses, such as a fee that was already paid on another computer, is listed on the Offline & Sync page with a choice to retry or discard it.
What doesn't work offline
I'd rather you hear this from us than find out on a busy morning.
A receipt printed offline has a temporary number that starts with PROV. The final number is given when the payment reaches the server, and only then can the receipt be sent on WhatsApp. Offline totals come from the dues as they were at the last sync, and late fees aren't added, so collect online when you can.
Some things need a connection: importing from Excel, changing settings, staff chat, sending SMS or WhatsApp messages, and the PDFs the server builds. And a device can keep working offline for up to seven days after it last signed in online. After that it still shows your records, but it needs to connect once before it saves anything new.
A few habits that help
None of this replaces a UPS for the counter computer and, if you can, for the router too. Software can carry on without internet, but it can't carry on without a computer.
Prefetch on the counter computer every morning, before the first parent arrives. Let the device sync before anyone clears the browser or hands the computer over for repair, because unsent changes live only on that device until they're sent. And have one person look at the Offline & Sync page once a day. Most days it's empty. On the day it isn't, you'll be glad someone looked.
If you'd like to see this for yourself, ask us for a demo and switch the Wi-Fi off halfway through. That's the only test that really counts.