Update a web app without losing work
Someone is halfway through an estimate when the app reloads to show a new logo. The update may be technically successful, but the work is gone. Avoid making a reader pay for an improvement with an interrupted task.
Separate records from release files
Treat app code, cached guides, preferences, and user records as different things. Replacing old pages should not delete a checklist or reset a saved choice.
Keep the names and ownership of app caches clear. If several apps share an origin, a cleanup routine must not delete every cache it sees. Test this with an unrelated cache present.
Let an active session finish
Use a visible message when an update is ready. Do not force a page reload while someone is entering work. For a read-only guide, asking readers to close all its tabs and reopen is a simple option.
This knowledge base uses that conservative approach. An updated release waits for the old controlled pages to close. It does not offer a button that silently reloads another open tab.
Plan changes to saved record formats
Adding a field is different from renaming or deleting one. Before changing a record format, keep a restorable export and test the migration on a copy. Decide whether older app versions can still read the result.
If going back to old code cannot read new records, “roll back the deployment” is not a complete recovery plan. Document the data recovery step too.
Run an update rehearsal
Start with the current version and a sample saved record. Deploy the next version to a test location. Leave an old tab open, use the new version after closing it, and compare the record.
Also test a failed download. Keep the previous complete release usable when the new one cannot finish. Write the tested versions and any limits in the handoff guide before releasing to staff.
Sources & verification
Documentation checked October 25, 2026. Platform instructions are documented guidance; physical-device behavior has not been verified for this article.
Your choice stays on this device. It is not sent to the site owner.