Composable page flows
Flows
Browse reference flows that show how RapidKit components, hooks, and local adapters fit together in full-page application screens.
Overview
Flows are implementation references for page-level composition. They stay outside the core package API while documenting how multiple primitives work together in realistic screens.
What flows are for
These pages show where validation, async state, navigation affordances, and supporting layout decisions should live when you build on top of the kit.
How to use the docs
Open a flow page to inspect the preview and switch to the code tab for a copyable example. Use the full-page preview when you need to assess the complete layout in context.
Composition boundaries
Flow examples document layout and interaction composition without turning page-level behavior into package-owned primitives. Business rules, routing, and host-specific data adapters should stay local to the consuming app.
What to expect on flow pages
Each flow page focuses on the assembled screen, the main interaction path, and the implementation shape behind it so teams can adapt the pattern without inheriting product-specific assumptions.