Skip to content
Back

Stepper FormPro

A multi-step setup flow: steps that fill and check off, sliding steps, inline validation, chip and plan fields, a review with Edit links and a success state.

oxyn add stepper-form
Name your workspace

You can change both later in Settings.

acme.app/
Lowercase letters and dashes
Step 1 of 4: Workspace
The code is part of Oxyn Pro

The preview stays free for everyone. Pro opens the code of every Pro component, screen, agent-app template, block and kit, plus the Pro CLI.

Get Pro

Rendered from Rust at build time · goes live when visible

When to use

  • Onboarding and setup: name a workspace, invite the team, pick a plan, review, create.
  • The user wants to know where they are, fix mistakes in place and go back without losing anything.

When not to use

  • One decision at a time with a rolling step count, a progress bar, sliding steps and a submit button whose width follows its label: use Multi-step form instead.
  • Several values in one field as chips: use Tag Input instead.
  • On or off for things that apply right away: use Switch instead.

Installation

Stepper Form is part of Oxyn Pro; the preview is free. Pro items install with the oxyn CLI once your licence is signed in; until then Pro members copy the code from this page.

Terminal
oxyn add stepper-form

Usage

Dioxus · rust
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Examples

Stepper

Numbered steps.

Name your workspace

You can change both later in Settings.

acme.app/
Lowercase letters and dashes
Step 1 of 4: Workspace
Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Review

At the review.

Check everything
Workspace name
Acme
URL
acme.app/acme
Invite by email
sam@acme.dev, ari@acme.dev
Plan
Team
Step 4 of 4: Review
Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Vertical

A vertical rail (Oxyn plus).

Name your workspace

You can change both later in Settings.

acme.app/
Lowercase letters and dashes
Step 1 of 4: Workspace
Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Conditional

A step that shows only for one plan (Oxyn plus).

Name your workspace

You can change both later in Settings.

acme.app/
Lowercase letters and dashes
Step 1 of 3: Workspace
Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Error

The submit fails next to the button.

Check everything
Workspace name
Acme
URL
acme.app/acme
Invite by email
sam@acme.dev, ari@acme.dev
Plan
Team
Step 4 of 4: Review
Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

API reference

StepperForm

PropTypeDefaultDescription
stepsrequiredVec<Step>—Steps.
styleString"stepper"`stepper` · `minimal` · `vertical`.
initial_stepusizeDefault::default()First step shown.
submit_labelString"Finish"Last step's button.
submitting_labelString"Creating…"While submitting.
success_titleString"Workspace ready"Success heading.
latency_msu32900Simulated submit time (the host's promise).
failboolDefault::default()The submit fails once (demo of the error next to the button).
draftsboolDefault::default()Oxyn plus: Save draft.
initial_valuesVec<(String, String)>Default::default()Values to start with: `(name, value)`; lists are comma-separated.
on_step_changeEventHandler<usize>—Step changed.
on_completeEventHandler<Vec<(String, String)>>—Completed: every `(name, value)`.

Read from the Rust signature and doc comments.

Keyboard interactions

KeyAction
↵Continue (in a chip field: add the entry first)
TabFields, then Back and Continue
←or→In the plan cards: move and select; ↵ picks and continues
or/ ⌫In a chip field: comma adds, Backspace removes the last chip

Accessibility

  • The steps are an ordered list with aria-current=step; finished steps are buttons that jump back.
  • Below 420 px the list stays for screen readers while “Step 2 of 4” shows.
  • After a failed Continue the first invalid field shakes; errors are announced politely.
  • Continue looks dimmed while invalid but still answers, so everyone hears what's missing.
From the spec

The steps are an ordered list with aria-current=step; finished steps are buttons. Each step is a fieldset with a legend. Errors are linked to fields and announced ("2 fields need attention"); Continue stays operable while dimmed so the reason is always heard. Submitting and success go to a status region.

Motion & interaction

Steps fill and check off along the top. The card slides in from the side you're heading to and its height animates. The primary button's label crossfades and its width follows (Continue → Finish → Creating…). The first invalid field shakes once.

Timing
TransitionDurationEasingReduced motion
Step slide260 ms, 20 pxease.out1 ms
Card height280 msease.outinstant
Step fill / tick260 ms drawease.outdrawn
Field shake360 msdampednone
Label swapox-baseease.outswap
Success check320 ms popease.outinstant

Responsive behaviour

  • Up to 520 px wide, down to 320 px; plan cards stack and review rows wrap below 420 px.
  • Touch: 16 px fields and 40 px buttons.
Edge cases (spec)

Below 420 px the step list collapses to "Step 2 of 4 · Team" (kept for screen readers), plan cards stack and review rows wrap. Optional fields skip the required check. Values survive Back and Edit. Very long values wrap in review. Touch: 16 px fields and 40 px buttons.

Notes for AI

  • Import StepperForm from oxyn_dioxus and include PRIMITIVES_CSS plus the token stylesheet once.
  • A GPUI version exists: StepperEl in oxyn_gpui.
  • Props to set first: steps.
  • Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.

Guides

Oxyn · 74 free components · 264 Pro components · 96 screens · 20 blocks · Dioxus and GPUI