Work / Personal project
Fieldkit
Capture that survives a dropped network.
A React Native capture path. Writes go through a REST API to Node. A local outbox keeps the write when the network drops, then syncs.
- Problem
- A field capture needs a place to wait when the device loses the network.
- Role
- Independent engineer. Personal project, not an employer case study.
- Implemented scope
- On-device capture, a local outbox, a REST boundary, and a Node service that receives the sync.
Architecture
- 01
React Native client
Capture happens on the device. This is the mobile surface for Fieldkit.
- Responsibility
- Collect the field write
- Concern
- Usable while offline
- 02
Local outbox
Durable local writes wait here when the network is gone.
- Responsibility
- Keep the capture
- Concern
- No lost write
- 03
REST API
The client syncs through a typed HTTP boundary. It does not talk to the database directly.
- Responsibility
- Accept a sync
- Concern
- Validation at the edge
- 04
Node service
Node receives the synced write. Fieldkit does not include an agent runtime.
- Responsibility
- Store the synced record
- Concern
- Separate from retrieval demos
What holds
- Decision
- Hold the write on the device until the API can accept it, instead of treating the network as always available.
- Failure handling
- When the network drops, the outbox keeps the local write and syncs later through the API.
- Evidence
- This page describes that path. Fieldkit is not running as a live operations dashboard on this site, and no fleet metrics are published.
- Status
- Personal project
- Limits
- No App Store listing, employer team, or production fleet is claimed. There is no public product screenshot in this repository.