AI app guides
How to check whether a generated app really saves your records
Distinguish a convincing browser demo from records that remain available to the right people across sessions.
Zocri · 2 min read · Sources checked
Write down who needs the record
MDN documents localStorage as browser storage associated with an origin that can persist across browser sessions. That can make a demo survive a refresh without proving the record is shared with the owner or available on another device. First define the requirement. A private scratchpad and a customer request queue need different kinds of persistence and access.
For a shared request app, create an invented record with a distinctive name. Note the account, address and environment. The customer should see a clear result, but that result is only the first observation. Keep the record identifier where the app exposes one so you can follow the same item.
Check beyond the original screen
Refresh the page and navigate away and back. Then sign out and return through the intended sign-in journey. If the app is meant to support multiple devices, open it in another appropriate session and check whether the record appears for the same authorized person.
Switch to the owner's account and find the record through the normal interface. Do not rely on a sample row that was already present before submission. Compare the distinctive details you entered, including a changed value if you edit the record, so you know you are observing the same work.
Test failure and access separately
Interrupt a safe test submission or use the app's supported failure simulation if available. Check whether the interface distinguishes saved, saving and failed. A confirmation that appears before the record is durably accepted can leave the user believing work is complete when it is not.
Use another customer's account to confirm that persistence does not become unintended sharing. Availability and privacy are different requirements. Ask the implementation reviewer to explain where records are stored and how access is enforced, especially if the observed behavior differs between the preview and published address.
Record the actual evidence
Write a short result for each step: refresh, return visit, second session, owner view and unauthorized view. Name any condition you did not test. If a record disappears, report the exact transition that loses it rather than assuming all storage is broken.
Accept the app against its intended use. A local-only tool can be perfectly suitable when that limitation is understood and recovery expectations are clear. A shared business workflow needs evidence that the right people can retrieve the same records later, with failures and permissions handled as part of the journey.