Improve Flow Continuity & Context Awareness

[martineckardt]

Context

Console flows (e.g., Deploy Token Home, Deploy Remote Token, Register With Home, Add Collateral) currently operate in isolation. After completing one flow, users lose context on where they are in the overall lifecycle and what the next main action should be.

Even though a flow map exists, the experience doesn’t carry the user forward. Devs have to manually decide and navigate to the next tool. This disrupts flow continuity and increases cognitive load.

Problems

- Context Loss:
After completing a flow, users don’t know the next main flow they should run (especially in branching scenarios like ERC20 vs Native).
- Manual Navigation:
Users must return to the main console and pick the next flow manually, breaking the sense of continuity.
- No State Persistence:
If the user refreshes or closes the console, the flow progress is lost. They can’t easily resume where they left off.

Proposal

1. Context-Aware “Next Flows” Modal

After each flow successfully completes, show a context-aware modal that summarizes what was done and lists the next relevant main flows (not granular actions).

Example:

✅ Wrapped Native Token Deployed on Fuji
Next possible flows:
• Register With Home
• Add Collateral
• Deploy Remote Token

[➡️ Continue] [Stay Here] [View on Explorer]

• The next-flow list adapts to the completed flow type (home, remote, register, etc.).
• Should be dismissible and optionally skippable.
• Light confetti or success animation can be added for positive feedback.

2. Auto-Move with Cancel Option

Offer an optional auto-transition to the next suggested flow after a 3–5 second countdown.
Include a “Cancel Auto-Move” button for manual control.

3. Full-Page Summary View

After the entire sequence is completed, route to a dedicated Summary page.

Contents:

• All produced artifacts (contract addresses, node endpoints, chain IDs), copy buttons, explorer links.
• Environment config snippet (JSON/YAML) for reuse.
• Next main flows section (e.g., “Setup Bridge”).

4. Persistent Flow State

Store flow progress locally (localStorage/session).
If the user refreshes or returns later, display:

“You were mid-way through setting up a Remote Token for Wrapped AVAX. Continue where you left off?”
[Continue] [Start Over]

5. Quick “Repeat Flow” Shortcut

Add a “Run Again” or “Deploy Another” button in the success modal.

6. “Learn More” Link in Header

Add a subtle Learn More button in the header, next to Edit on GitHub / Report Issue, linking to contextual docs for the current flow.

7. Confetti on Completion 🎉

Confetti (or light animation) should trigger on:

• Successful tool completion
• Full sequence completion (e.g., Create Chain → Convert to L1)

8. Save & Share Setup Summary

Let users copy/export their setup (JSON or text):

{
  "token": "Wrapped AVAX",
  "home": "Fuji",
  "remote": "Echo",
  "addresses": {
    "home": "0xabc...",
    "remote": "0xdef..."
  },
  "status": ["homeDeployed", "registered", "collateralAdded"]
}