pending review ## Confirmed landing-to-active-user journey Canonical current journey: 1. User lands on the Mode landing page. 2. User starts signup. 3. User enters email, password, and standard signup details. 4. User answers normal onboarding questions. 5. User completes signup. 6. User lands on an interactive demo canvas. 7. User goes through the demo to learn Mode inside the product. 8. User learns the canvas feels like a Figma-style design surface. 9. User learns the canvas can contain frames, layers, elements, components, and portal nodes. 10. User learns that a portal node is the live app/dev-server view inside the canvas. 11. User learns they can click elements inside the portal. 12. User learns they can move items between the portal and the canvas. 13. User learns they can edit items on the canvas. 14. User learns they can build edited canvas work back into the live app/codebase. 15. User completes the interactive demo. 16. User returns to the dashboard. 17. User sees a prompt to import a codebase. 18. User imports via codebase upload or GitHub connection. 19. User waits while Mode sets up the imported project. 20. User opens the canvas for their own project. 21. User explores the portal/live app, uses canvas and components, and attempts meaningful product/design changes. 22. User reaches a product/design change they want to share or ship. 23. User creates a share link or pushes/exports through GitHub, including creating a PR where applicable. ## Activation definition A user is activated when they have: - completed signup; - completed the guided demo/onboarding; - imported or connected their own codebase; - opened their own project canvas; - used the portal/canvas workflow on their own project; - made a useful product or design change; - and shared it or moved it toward GitHub output. Analytics note: the AAARRR map defines activated users as signing up, completing onboarding by finishing the guided demo project, importing or connecting their own project, opening their own project canvas, using the portal/canvas workflow on their own project, and completing a useful own-project edit/build or output action. Share link creation and GitHub PR/export are separate referral/revenue-adjacent signals unless Alex approves a stricter active-user threshold. ## Product activation assumptions The launch motion should bring users into self-serve and help them experience Mode through real product UI work rather than generic exploration. Strong first-use beliefs to create: - “This works against my actual product context.” - “I can identify one visible UI issue and make progress toward a reviewable change.” - “The workflow feels familiar enough because the canvas resembles a design surface.” - “Engineering review remains part of the process.”