State machines feel heavy for UI flows. What are people…
0 reactions
State machines feel heavy for UI flows. What are people using?
For UI flows that are not strictly linear (onboarding, checkouts, eligibility flows, etc.), I often see logic distributed across multiple places:
•conditionals in components
•flags in state
•effects triggering navigation
•validation logic duplicated per step
State machines provide a formal model, but in practice they can feel heavy for teams that mainly need to describe a flow graph.
I’m curious what abstractions people are using in real projects.
For example:
• multi-path onboarding
• flows with loops (retry / corrections)
• resumable progress
• feature-dependent steps
• flows spanning multiple screens
Are amost teams:
•relying on router logic?
•building custom hooks?
•using state machines?
•something else?
Interested in hearing what has worked well in production.
#programming #js #dev #technology
For UI flows that are not strictly linear (onboarding, checkouts, eligibility flows, etc.), I often see logic distributed across multiple places:
•conditionals in components
•flags in state
•effects triggering navigation
•validation logic duplicated per step
State machines provide a formal model, but in practice they can feel heavy for teams that mainly need to describe a flow graph.
I’m curious what abstractions people are using in real projects.
For example:
• multi-path onboarding
• flows with loops (retry / corrections)
• resumable progress
• feature-dependent steps
• flows spanning multiple screens
Are amost teams:
•relying on router logic?
•building custom hooks?
•using state machines?
•something else?
Interested in hearing what has worked well in production.
#programming #js #dev #technology
| 1,000 mlx | |
| 2 | |
| 0 |