Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Design and implement offline changes for [record and operation]. The promised behavior is [what works offline and when success is confirmed].
Inspect the local and network data layers. Define the durable local representation, pending-operation identity, synchronization trigger, retry behavior, and policy for conflicting edits. Distinguish a saved local draft from a change confirmed by the server.
Verify offline creation or editing, app restart, reconnection, repeated delivery, expired authentication, and a conflicting remote edit. Check how permanent rejection is shown without losing user work. Report the observed local and server states, relevant tests, and any unresolved product decision affecting reconciliation.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- Android — Building an offline-first app
- Android — Data layer and repositories
- Android — Persistent background task scheduling
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original, unexecuted synchronization template. Android supports queueing, retries, local state, and explicit conflicts; no generic conflict-free merge is claimed.