Repository navigation
docs(architecture): commit to a capture-first field client - #2
Merged
Merged
Conversation
The app path listed a native client as "direction, unspecified", which left the one question that decides its shape unanswered: is capture the client's primary job, or a feature of a client that mostly edits reports. It is the primary job. Photos, findings and voice notes are written to device storage at the moment of capture with no server round trip; report editing, templates and admin stay on the web surface. Local storage, sync ordering, de-duplication and conflict resolution are that client's architecture rather than later additions to it. Recorded here because both driving requirements — capture with no signal, and sync that lands offline work in order and without duplicates — are structural, cheap to design in and expensive to retrofit. `useOfflineQueue` is today's light version of the second, a fallback around a server-first data path. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The "Future app path" section listed a native client as "direction, unspecified", leaving the one question that decides its shape unanswered: is capture the client's primary job, or a feature of a client that mostly edits reports?
This records the answer — capture is the primary job — and the reasoning that makes it a decision rather than a preference.
What changes
Documentation only. No code, no behavior.
useOfflineQueueis named as today's light version of the second, a fallback around a server-first data path.Type of change
Test plan
verifyreports on this PRFollow-up (not in this PR)
The next step is a spike under
docs/develop/spikes/answering only the two structural questions before any client code exists: the on-device store, and the sync/conflict model. Both are decisionsuseOfflineQueuecurrently makes implicitly as a fallback.Per the maintainer note in the PR template: merge, do not squash.
🤖 Generated with Claude Code