· · Daniel A
The Case for Offline-First Apps
Why we built SimplyBoard with offline support as a core feature, not an afterthought.
The internet is not as reliable as we pretend it is.
You're on an airplane. In a subway tunnel. At a coffee shop with spotty WiFi. In a developing country with intermittent connectivity. In a meeting room where your laptop refuses to connect to the corporate network.
In all these situations, most modern web apps become completely useless. They show spinners, error messages, or just blank screens. Your productivity grinds to a halt because some server somewhere didn't respond fast enough.
This is absurd. Your notes are already on your device. Why can't you see them?
The Cloud-First Trap
Most apps are built "cloud-first," which really means "cloud-only." Every action requires a round trip to a server. Open the app? Fetch data. Edit something? POST to an API. Search? Send query, wait for response.
This architecture made sense when storage was expensive and browsers were limited. But in 2025, your phone has more computing power than the servers that originally ran Gmail, and IndexedDB can store gigabytes of data locally.
Yet we still build apps like it's 2010.
Offline-First Principles
- Data is stored locally first, synced to cloud second
- All reads happen from local storage (instant)
- Writes happen locally, then sync when online
- The app works identically with or without internet
How SimplyBoard Does It
When you open SimplyBoard, we don't wait for our servers. Your entries are already cached locally, encrypted and ready to decrypt. Search happens against local data. Creating new entries writes to local storage immediately.
In the background, we sync. New entries get pushed up. Updates from other devices get pulled down. Conflicts get resolved. But you never have to wait for any of this.
The result? SimplyBoard feels instant. There's no loading state when you open it. Search results appear as you type. Saving an entry takes milliseconds, not seconds.
The Technical Bits
We use a combination of technologies to make this work:
- IndexedDB · For storing encrypted entries locally with good performance
- Service Workers · For caching the app shell and handling background sync
- Optimistic Updates · UI reflects changes immediately, sync happens in background
- Last-Write-Wins Conflict Resolution · Simple but effective for personal data
The tricky part is handling conflicts. What happens if you edit an entry on your laptop while offline, and also edit it on your phone? We use a "last-write-wins" strategy based on timestamps. It's not perfect, but for personal notes it's usually fine·and it's simple enough to be reliable.
Sync Status
SimplyBoard shows a subtle offline indicator when you're disconnected, so you always know your sync status. When you reconnect, changes sync automatically·no manual action needed.
Why Don't More Apps Do This?
Offline-first is harder to build. You need to think about data consistency, conflict resolution, and storage limits. It's easier to just require internet and call it a day.
But we think the user experience is worth the engineering effort. Nobody should lose access to their notes because they're on a plane or in a basement.
The Speed Bonus
Here's the thing people don't talk about: offline-first apps are also FASTER when you're online. Because reads come from local storage, there's no network latency. The speed improvement is dramatic·instead of 200ms round trips, you get 2ms local reads.
Users describe SimplyBoard as "snappy" or "instant." That's not because our servers are fast (though they are). It's because we're not hitting the servers for every action.
Build for offline, and online gets better too.
· The SimplyBoard Team
