Should React Native apps rely on server-side idempotency keys or client-side deduplication to prevent duplicate writes on retry?
The goal is to guarantee that a network mutation (e.g., a payment or form submission) is processed exactly once on the server, even when the request is retried after a timeout, network failure, or app restart. Constraints include deciding where the idempotency key originates and how it is persisted (client‑side storage like AsyncStorage versus server‑side st