# How can saved app records be verified after reload?

Canonical: https://uvilno.com/answers/do-generated-app-records-survive-reload
Updated: 2026-10-27

A saved record should be retrieved from the hosted service after navigation or reload, using the same authorized app identity. Uvilno.db provides that persistence for declared collections. A toast, optimistic update or localStorage mirror alone is insufficient evidence; inspect App Data and test a retrieval.

Use a unique, non-sensitive test value so the record cannot be confused with demonstration data. Create it, change one field, leave the route and return. Reload the iframe, sign back into the same app identity if needed, and check the value again.

Then exercise failure behavior. A rejected write should leave the previous saved state intact and explain what the user can retry. Uvilno's local media storage and collection records have different persistence boundaries, so verify them separately instead of treating every browser cache as a backend.

## What to verify

| Check | Published behavior | Verification |
| --- | --- | --- |
| Acknowledgment | The service response must confirm the write. | Inspect the resulting record ID and saved fields. |
| Reload | The same visitor should retrieve the record again. | Navigate, reload and read the hosted list. |
| Independent view | The owner App Data manager reads actual rows. | Compare its fields with the generated interface. |

## Steps

1. Create one uniquely named disposable record.
2. Edit it, navigate away and reload.
3. Confirm the same row and revision in App Data.

## Editable starting brief

Build a private reading list with title, author and reading status. Wire add, edit, remove and filters to Uvilno.db and show saved/failed states. Include a small verification checklist for creating a uniquely named book, changing its status and confirming the record survives navigation and iframe reload. Do not present a browser cache as server persistence.

## Sources

- [Uvilno public SDK documentation](https://uvilno.com/docs)