Editing Stepper Pages Freely

Steppers are useful when an app needs to guide users through a process one step at a time.

For end-users, stepper tabs are often part of the app navigation. They help users move between steps, understand where they are in the process, and complete information in the right order.

Many times, steppers also enforce a sequence. Users may need to complete step one before moving to step two, fill required fields, upload documents, or pass validations before continuing.

That makes sense for the end-user experience.

It makes much less sense when someone is still building the app.

Building Is Not the Same as Using

When a builder is working on a stepper-based app, they are not trying to submit the process.

They may want to jump directly to step three, edit a field on the final page, adjust the layout of the second step, or preview the full flow without filling in fake data just to move forward.

Validations are important for end-users. They protect the process and help make sure the submitted data is complete.

But inside the builder, those same validations can become unnecessary friction.

The builder should be able to access every stepper page freely, regardless of required fields, validation rules, or the sequence that will later apply to real users.

Free Access to Every Step

When editing a stepper, builders need full access to each part of the app.

They should be able to open any step, review it, configure it, and make changes without being blocked by rules meant for the live user journey.

This makes it easier to:

• Preview each step
• Edit fields and sections
• Adjust layout and spacing
• Review buttons and actions
• Check the user flow
• Work on later steps without completing earlier ones

The end-user still gets a guided process. The builder gets a flexible editing experience.

That separation matters.

Validations Belong in the Live Flow

A required field should stop an end-user from submitting incomplete information.

It should not stop a builder from editing the next page.

A validation rule should help protect business data when the app is being used.

It should not force someone configuring the app to enter fake values just to reach another step.

In other words: validations should do their job in the right context. Very ambitious, apparently.

Better Editing for Multi-Step Apps

Stepper-based apps are often used for real business processes: onboarding, applications, approvals, registrations, document collection, service requests, and internal workflows.

These apps usually include multiple pages, required inputs, conditional sections, file uploads, and process rules.

That is exactly why builders need freedom while editing.

The more structured the end-user journey is, the more flexible the builder experience needs to be.

A Smoother Way to Build

Editing stepper pages freely makes app building faster and less frustrating.

Builders can move directly to the part they want to configure, make changes, preview the result, and continue working without unnecessary interruptions.

The live app can still guide users step by step.

The builder just does not need to suffer through the same journey while building it.

A small difference, but a very welcome one.