Version mobile APIs before fields multiply past recovery
Silent additive fields feel safe until clients deserialize differently. Contract discipline starts earlier than most teams expect.
Notes
Practical writing from mobile backend advisory — versioning, conflict states, token refresh, and payload budgets.
Offline writes need visible conflict states, not silent last-write wins
Users forgive delayed sync. They rarely forgive disappearing edits. Surface merge decisions in the product, not only in logs.
Token refresh that protects sessions without trapping users
Aggressive expiry looks secure until legitimate refresh storms lock people out during peak commute hours.
Set payload budgets before you celebrate another nested JSON tree
Nested graphs that feel tidy on office Wi-Fi punish users on congested mobile networks across Taipei commute corridors.