A canvassing web app built for dead zones, apartment basements, and rural routes. It saves the walk list (the addresses each canvasser will visit) on the phone, and it stores every disposition (door result), note, and survey response in the browser's storage (IndexedDB). When signal returns, the saved records upload in the background.
Capabilities
Most canvassing tools assume the phone has a connection. Beacon was designed to work without one. Every screen the canvasser uses works without cell service, and the data uploads when a connection returns.
/01, CACHE
The app, walk list, contact details, and survey questions are all saved to the phone the first time it connects, so the canvasser can open the app at the door without waiting on a network.
/02, QUEUE
Every disposition, note, and survey response is saved to the phone first. The saved records stay through browser closes and phone restarts, so nothing is lost if the battery dies.
/03, UPLOAD
When the phone finds a connection, the saved records upload together in the background. If two canvassers visit the same contact, Beacon keeps both visits as separate records.
At the door, without signal
Disposition buttons, survey forms, and AI talking points saved during the last connection load directly from the phone. The "Online" label at the top of the walk list turns red when the signal drops, but the rest of the app keeps working as before.
See the canvasser app →
How an offline shift runs
/01
Open the app on wifi and tap sync. The walk list, contact details, survey questions, and territory boundaries are saved to the phone.
/02
Walk the list, record dispositions, complete surveys, and leave notes. Every action is saved directly on the phone. The "Online" label turns red, but nothing else changes.
/03
When the phone has signal again, the saved records upload in the background and the pending count returns to zero.
/04
Knocks appear in the activity feed and the map updates as the records arrive, so there is no spreadsheet to hand off and nothing to reconcile at the end of the day.
FAQ
Q / 01
Every offline interaction is saved in the phone's browser storage (IndexedDB). When the phone has a connection again, the saved interactions upload to Beacon together. If two canvassers visited the same contact, Beacon keeps both visits as separate records.
Q / 02
The data stays saved on the phone through browser closes, app restarts, and phone reboots. Open the app again once you have a connection, and the saved records upload normally.
Q / 03
No. Beacon is a Progressive Web App, a website that installs like an app. On Android, Chrome offers "Add to Home Screen," and on iOS you tap the Safari share button and choose "Add to Home Screen." You get the app icon and a full-screen view without an app store account.
Q / 04
The app is under 2MB on first load, and a typical 500-contact walk list is under 1MB. Once saved, the app uses no data until it uploads, and a busy day of door knocks (100+ records) usually uploads in well under 500KB.
Start walking
Open an account, install the app on your team's phones, and connect once to save the data. The walk list then works with or without cell signal.