Wappler documentation

State management

Keep UI state in URL and browser storage (Query/Cookie/Session/Local).

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.

Tours

Choose where page state belongsChoose URL, cookie, tab-session or local-browser storage according to the user’s goal and the data’s lifetime.View guide Put a preference in the URL with Query ManagerMake a small piece of page state visible in the query string.View guide Passing Values Between your PagesSometimes you need to pass values between different pages of your site. You can easily do this in Wappler using the State Management Component. There are several ways of doing this - for example usingView guide Remember a preference with Cookie ManagerStore and read a small browser-visible preference cookie.View guide Keep a draft preference in Session ManagerKeep temporary page-session state through reloads in the current tab.View guide Save a browser preference with Local ManagerRemember a non-sensitive preference across page reloads on the same origin.View guide Working with ArraysThe Array component in Wappler allows you to store items in arrays and manage them. Here we will show you a simple example of how to use an array in order to create a tags input, where you enter tags View guide Data StoreClient-side collections in App Connect: define a schema, store records, and perform record actions like insert/update/delete.View guide