What problem are we solving?
Thunder currently segregates flows by type (e.g., authentication, registration) and does not allow switching between flows at runtime. This limits the ability to create seamless user journeys (e.g., switching from login to signup without re-entering data).
Who are we solving this for?
End users and developers who need flexible, seamless authentication and registration experiences.
Why should we solve this now?
Supporting runtime flow switching enables smoother user journeys and aligns with modern UX expectations for identity systems.
Proposed solution
Introduce a new node (call node or similar) that can switch the flow graph at runtime. At the end of the call node, it can be wired back to the same flow. The solution should consider UX and context passing between flows.
Alternatives
Discussion
What problem are we solving?
Thunder currently segregates flows by type (e.g., authentication, registration) and does not allow switching between flows at runtime. This limits the ability to create seamless user journeys (e.g., switching from login to signup without re-entering data).
Who are we solving this for?
End users and developers who need flexible, seamless authentication and registration experiences.
Why should we solve this now?
Supporting runtime flow switching enables smoother user journeys and aligns with modern UX expectations for identity systems.
Proposed solution
Introduce a new node (call node or similar) that can switch the flow graph at runtime. At the end of the call node, it can be wired back to the same flow. The solution should consider UX and context passing between flows.
Alternatives
Discussion