App memory
The app’s memory for the session: the chosen category, the tapped card, the cart.

App memory is what the app remembers while someone is using it: the chosen tab, the tapped card, the cart. Data tab → App memory; each remembered thing has its own name, such as cart. Types: Text, Number, Yes / no, Choice, Multiple choice, Row from a table and JSON. The value you type when creating it is the initial one: what the app starts with.
- Things are remembered by the Remember action, or by a block itself — an input, filter chips or a slider remember their value under the name in their field-name property.
- It is read as a substitution:
{{category}},{{cart}}. - A JSON item starting as
[]is a list: a cart, favorites, chosen seats. - The Row from a table type is for the tapped card: name the table and the sample comes from its first row. No hand-written JSON, and
{{selectedEvent.…}}offers exactly the columns the table has right now.
Every named form field is already a variable. Whatever someone typed or picked sits in memory under the field name straight away, before sending: {{title}} shows the title being typed, {{poster}} the address of the attached poster. The data picker gathers these under Form fields, so there is no variable to create by hand.
During preview the same panel shows live state — what the app remembers right now. That is the first place to look when a filter refuses to filter.