Use App Connect on purpose
Add it because the page needs reactive behavior, not because every page should automatically become reactive.
Add App Connect to Your Pages
Understand when a page needs App Connect and how to introduce reactive behavior without turning a simple page into unnecessary complexity.
Introduction
Section titled “Introduction”Not every page needs App Connect. Static content, simple layout, and purely server-rendered output often do not benefit from adding a reactive layer. But the moment a page needs live expressions, client-side state, conditional UI, dynamic attributes, or event-driven behavior, App Connect becomes the right tool.
This tour helps you decide when to add it and how to think about that choice in current Wappler projects.
Typical signals
You need expressions in the UI, a data component on the page, dynamic show/hide behavior, reactive form state, or client-side events that update the interface.
Keep simple pages simple.
Add App Connect when the page needs live client-side behavior.
Use the App Connect panel as a workflow surface, not as an afterthought.
Start with one reactive goal, then expand only if the page benefits.
Know when the page has crossed the line
Section titled “Know when the page has crossed the line”These are the common moments where a regular page becomes an App Connect page.
Expressions and bindings
Section titled “Expressions and bindings”If the page needs to display computed or formatted client-side values, App Connect gives you the binding model to do it cleanly.
Reactive display logic
Bindings are the signal that a plain page has started becoming a reactive page.
Reactive state
Section titled “Reactive state”If filters, toggles, counters, or browser state should update the interface without a full page reload, you are in App Connect territory.
State lives on the page
Once the interface responds to client-side state, App Connect is part of the architecture.
Action-driven UI
Section titled “Action-driven UI”If buttons, inputs, or component events need to update data or trigger interface changes, App Connect becomes part of the page architecture.
Events need a model
Interactive UI stays easier to reason about when events and updates live in the App Connect workflow.
Next steps
Section titled “Next steps”Once you know why App Connect belongs on a page, move into a small reactive example or the broader App Connect index.