Reading offline is a cache. Writing offline is a queue you have to design.
A change held in memory dies with the app. Retries without backoff flatten the battery and hand the outage back to your own server. A request in flight when the OS kills the app stays stuck, and one rejected change blocks every good one behind it. Four failures, four different fixes, and "try again later" is none of them. One of them probably bit you first. https://shipmindlabs.com/c/a7dd682a