Connectivity is a Privilege

In Metro Manila, it's easy to design for high-speed internet. But in Samar, Maguindanao, or Palawan, a 3G signal is a luxury. Many public schools still rely on a single shared connection. Any EdTech product that assumes consistent connectivity is a product built for the few.

Service Workers and the Sync Queue

Our offline-first architecture relies on a battle-tested pattern:

// Service Worker: Cache-first for assets, network-first for data
self.addEventListener("fetch", (event) => {
  if (event.request.url.includes("/api/")) {
    event.respondWith(networkFirst(event.request));
  } else {
    event.respondWith(cacheFirst(event.request));
  }
});

When a teacher logs attendance or inputs grades without a connection, the action is stored in an IndexedDB sync queue. The moment connectivity is restored, all queued operations are flushed to the server in order, with conflict resolution handled automatically.

What Never Leaves the Device

Student data is never cached on the device in plaintext. Our service worker layer encrypts all locally stored data using a per-device key derived from the teacher's credentials, ensuring that even if a device is lost, student PII remains protected.