Pages & Sites
Choosing V3 vs V4
Choose the right page builder version and plan migration between visual JSON pages and generated runtime code.
Choosing V3 vs V4
Antly supports two modern page builders. V3 is a visual component tree builder. V4 is an Iris-first runtime-code builder. Both render inside Sites pages, but they optimise for different authoring styles and maintenance needs.
Decision table
| Choose | When | Trade-off |
|---|---|---|
| V3 | Builders need drag-and-drop control, predictable component settings, filter bars, and low-code page assembly. | Complex app logic may require React blocks. |
| V4 | Builders want Iris to generate custom runtime pages, richer interactions, or app-like experiences. | Review generated code behaviour carefully before publishing. |
| V3 with React blocks | Most of the page is visual, but one component needs custom data or form logic. | React block code must follow the injected runtime rules. |
| V4 with history | The page will evolve through AI prompts and needs traceable versions. | Requires prompt discipline and preview testing. |
Migration notes
V3 stores a JSON node tree. V4 stores generated code and metadata. Treat migration as a rebuild, not a format conversion. Start by documenting the page goal, audience, data sources, filters, actions, and important visuals. Then recreate the page in the target builder and test it with the same user roles and sample records.