Flow

Purpose

A flow is the onboarding experience you author in the flow builder. It is a directed story users follow inside your app—screens, branches, and optional integration steps such as a subscription paywall.

What a flow contains

• Screens — Steps users see, built from layers (text, buttons, carousels, auth rows, and more).
• Decision nodes — Branch on answers, user attributes, or experiment context.
• External surfaces — Integration steps such as a RevenueCat paywall outside normal screen chrome.

While you edit, Rheo keeps a working draft. Publishing creates an immutable version—a snapshot that clients receive when a channel points at it.

Publishing is not the same as going live. Publishing alone does not change what users see until a channel or experiment pins that version.

Lifecycle

Create flow → edit draft (autosave) → publish version → assign channel or experiment arm

Each flow keeps a version history with labels. Analytics can filter by a specific published version or aggregate across versions.

How to publish

1. Open the flow in the flow builder.
2. Resolve any validation warnings (missing required fields, broken connections).
3. Choose Publish and add an optional version label.
4. Assign the new version to a channel or experiment arm.

Plan limits

Indie workspaces cannot use translations, Lottie animations, AI authoring assists, or integration layers on publish. Grow+ unlocks the full palette, subject to per-app editor settings you configure under App settings. See Plans & entitlements.

Related

• Flows — Catalog, versioning, publish dialog.
• Flow builder — Canvas, layers, validation.
• Channel — How versions reach users.