Cam IncollFieldwalker works offline on your phone — download your map, contours, and elevation data before heading out, and every field tool keeps working with no mobile signal. Pins you drop offline queue on your phone and sync automatically when you reconnect.
If you've spent any time on a rural property in Australia, you already know the reality: mobile signal is unreliable. It drops in the gully. It vanishes behind the hill. The paddock where you're doing your most important site analysis is invariably the one where your phone shows no bars.
This isn't a minor inconvenience for a field tool. It's a fundamental design constraint. If the tool only works with a live internet connection, it doesn't work where you need it most.
Offline isn't a feature — it's a requirement
When I thought about what a field companion for permaculture design actually needs to do, offline capability wasn't a nice-to-have on the roadmap. It was the foundation. Everything else — the Contour Walker, Field Walker, pin dropping, observation notes — had to work without signal. If it didn't, it wasn't a field tool. It was a desk tool that happened to run on a phone.
So Fieldwalker's offline system downloads everything the field tools need before you leave the farmhouse. The aerial image. The elevation data. The contour lines. Your existing pins and observations. All of it cached on your phone, ready to use in the paddock.
What works offline
Everything in the field toolkit.
Contour Walker reads the elevation data from the local cache and runs all guidance calculations on your phone. The arrow, the steering, the "on the line" / "drifting" / "off the line" indicators — all running locally. You can walk a contour line for an hour with no signal and the guidance never misses a beat. The walked-line recorder works offline too — your GPS breadcrumb trail saves locally and uploads when you reconnect.
Field Walker shows your live GPS position on the cached aerial map. Pins you drop are queued on the device with a clear "N pins waiting to sync" indicator. When signal returns, the queue flushes automatically. Every pin arrives on the server with its correct GPS coordinates, timestamp, and any notes or photos you attached.
The map view itself works offline — pan, zoom, toggle layers, check contours. You're looking at the same map you'd see online, because it's all on your phone.
The sync that doesn't lose data
The offline pin queue was one of the things we spent the most time getting right. On paper, it's simple: save pins locally, upload later. In practice, there are edge cases that can silently lose your work.
What happens if you drop two pins at almost the same moment? What happens if the sync starts while you're mid-drop? What happens if you're editing on desktop while pins are syncing in from the field? Each of these scenarios was tested and hardened. The queue is reliable because we specifically went looking for the ways it could fail and closed them.
This matters because field observations are the kind of data you can't recreate. You were standing in that spot, at that time, noticing that thing. If the tool loses that pin, that moment is gone. The queue has to be bulletproof, and we treated it that way.
Download before you go
The offline workflow is deliberate, not automatic. You choose to download a map for offline use before heading out. The download pulls everything the field tools need and shows you the status: "Ready offline," "Partially downloaded," or "Not available offline." You can resume a partial download, or clear the cached data when you're done.
This is intentional. Automatically caching everything would use significant storage on your phone, and you might have dozens of project maps. Choosing which one to download means you take what you need for today's site visit, and your phone isn't quietly filling up with cached elevation data from projects you haven't touched in months.
Why this matters for the design process
The observe step in permaculture design happens on the land. Not at a desk. Not in front of a laptop. On the land, in the weather, walking the terrain.
A tool that requires internet connectivity to support that observation step is asking you to observe where the signal is, not where the landscape is interesting. That's backwards.
Offline capability means you observe where the land tells you to observe. You follow the water. You walk the ridge. You investigate the shady gully. The tool works wherever you go, because the data is on your phone, not on a server.
The design process starts in the field. The tool should work there.