Generative UI vs static A/B testing
A/B testing splits traffic between a few pre-built variants and measures which wins. Generative UI composes the interface per visit from live data, so it is not limited to the handful of variants a team can build and maintain.
What A/B testing does
An A/B test ships two or more fixed variants and assigns each visitor to one, usually for the length of the test. It answers which variant performs better on average for the group. The experiences are built by hand, so the number of them is small.
What generative UI does
Generative UI does not choose between pre-built pages. It assembles one from data about the visit. The result is closer to one experience per visitor than a handful of variants. You are tuning the rules and the data that drive generation, not maintaining a set of static pages.
Using both
They are not exclusive. Teams often A/B test the rules behind a generated interface: does composing from live intent beat composing from the segment. The test measures the approach. Generation produces what each visitor sees.
See it on your own traffic
Add the SDK, define one attribute, and see an attribute updating against your own traffic in the first session. The free tier runs on the real engine: no card, no sales call.