Why Sunday shouldn’t depend on your Wi-Fi

Most presentation software was built for a world where the network is always there. That world isn’t Sunday morning. The router in the AV booth reboots after a power blip; the upstairs lounge sucks the bandwidth dry; the conference centre Wi-Fi captive-portal silently signs you out an hour into setup. None of these things should change what’s on the screen behind the worship team.

We built Verse around that constraint first, and the product followed.

The constraint

When we sketched the first version of Verse, we wrote one rule on the whiteboard:

Everything a presenter needs during the service must already be on the machine before the service starts.

That’s it. Every other decision came after.

It sounds obvious. In practice it ruled out almost every off-the-shelf approach we considered — cloud-rendered slides, server-side scripture lookups, streaming lyric overlays, even auto-updating themes. The instant the renderer reaches across the network mid-service, the whole product fails its first promise.

What that changed

A few concrete things flow from that one rule:

• Scripture lives locally. Every public-domain translation Verse supports ships pre-bundled, and licensed translations cache on first download. The verse picker doesn’t hit an API.
• Service plans are files, not records. A service plan is a local file the desktop app owns. Sync is a separate, opt-in layer. If the network is gone, the plan still opens.
• Activation has a grace window. The licensing server can be unreachable for 30 days without the desktop app shutting you out mid-sermon. We treat the activation token as a 90-day lease, not a per-request check.
• Rehearsal uses the same renderer as Sunday. No “preview mode” that diverges from live. The thing you saw on Thursday is the thing the projector shows on Sunday.

What it doesn’t mean

Offline-first isn’t offline-only. The web portal, the admin console, billing, content sync — those all happen online. We just made sure none of them are in the path between a presenter and the next slide.

That distinction matters because every church we’ve talked to in beta has a mix: someone needs the cloud (to manage seats, to update the catalog), and someone — usually a volunteer running the booth on Sunday — really, really doesn’t.

What we’re still figuring out

A few honest open questions, in case you’re considering Verse and want to know where the rough edges are:

• Sync conflicts. Edit a service plan offline on two machines, reconnect — how does Verse resolve it? Right now: last-writer-wins, with a warning. We want better.
• Catalog updates. Lyrics get added to the catalog all week. We pull updates lazily; if you’re curating for Sunday on Friday and a new song lands Saturday night, you need to manually refresh. Background sync is on the roadmap.
• Commercial translations. Publisher licensing for NIV / ESV / NLT is in progress. Until then the offline guarantee only covers public-domain translations.

We’ll write about each of those as we close them out.

If you’re in a church running Sunday

If your service depends on a stable network and you’ve had at least one Sunday where the network let you down — we’d like to talk. We’re still in private beta and onboarding partner churches one at a time. Send us a note.