Why we built Manifold offline-first

Manifold is offline-first because the places gas engineers work, lofts, basements, plant rooms and the cupboard under the stairs, are exactly the places with no signal. So the whole job, opening a property, capturing a check, finishing a record, works with no bars, and everything syncs the moment you're back online. It's the difference between a tool that works on site and one that only works in theory.

The problem with cloud-first

Most field software assumes a connection. It's built for a desk, then handed to someone standing in a basement, and it falls over the moment the signal drops: a spinner, a lost form, a job you have to redo in the van. Engineers learn not to trust it, so they go back to paper and type it up later, which is the exact evening admin the software was supposed to remove.

What offline-first actually means here

• You can open your day, a property and a job, and capture the whole check, with no connection at all.
• Nothing you enter depends on a round-trip to a server, so there's no spinner and nothing to lose when the signal drops.
• The moment you're back online, it all syncs in the background, without you having to think about it.

Why it's a foundation, not a feature

You can't bolt reliable offline onto a cloud-first app at the end; it changes how the whole thing is built, from where data lives to how it syncs and how conflicts are resolved. We started there on purpose, because for a UK gas engineer works without signal isn't a nice-to-have. It's the difference between finishing the CP12 on the doorstep and writing it up at nine o'clock that night.