State management
Keep UI state in URL and browser storage (Query/Cookie/Session/Local).
Choose a Browser State Strategy
Use this hub when UI state needs to survive interaction, reloads, or navigation. Start with the storage strategy, then move into Query Manager, cookies, session, local storage, and array state.
Choose a state path
Section titled “Choose a state path”Start with storage strategy, then move into URL state, cookies, session, local storage, and array state.
Tours
State management (Query/Cookie/Session/Local)
A practical guide to App Connect storage strategy in Wappler, comparing URL state, cookies, session storage, and local storage through real UI scenarios.
Query Manager (URL-driven state)
Use Query Manager to make page state URL-driven in Wappler, so searches, filters, sorting, paging, and selected records can survive reloads and be shared safely.
Pass Values Between Pages
Learn when page context should travel in the URL, stay per-tab, or persist in browser storage so Wappler navigation remains predictable.
Cookie Manager (persist preferences)
Persist lightweight preferences across sessions with Cookie Manager, including optional expiration and cookie options.
Session Manager (per-tab state)
Store temporary workflow state for the current tab using Session Manager; cleared when the tab closes.
Local Manager (persistent settings)
Learn when Local Manager is the right persistence layer for Wappler UI state, and how to store settings that should survive reloads without going to the server.
Working with Arrays in Browser State
Use App Connect Data Store and browser state patterns when you need lists, selections, and batch-friendly client-side data in Wappler.
Data Store
Client-side collections in App Connect: define a schema, store records, and perform record actions like insert/update/delete.