Filed from a read-only UX/product audit of main. Not urgent — batching under nice-to-have.
What's there
A brand-new user's first screen (web/app/(workspace)/home) is a logo and "What would you like to learn?" above an empty composer — no example prompts, no capability cards. Two real capabilities, Solve and Mastery Path, are tucked behind a secondary hover flyout (ChatComposer.tsx:917-987) that a first-time user has no reason to open. The composer itself is well engineered once found (clean state machine, upfront file-type/size limits on drag-drop) and holds up fine on mobile behind a hamburger menu — the gap is purely the first-run experience.
The interesting part
A genuinely sophisticated 10-step guided tour component already exists in the codebase — SettingsTourOverlay.tsx — but it's wired only into Settings, a page that (see the companion "Appearance settings unreachable" issue) almost nobody but admins can even open. The onboarding investment already happened; it's just pointed at the page fewest people ever see.
Suggested fix
- Point the existing tour component at the home screen for first-time users (in addition to, or instead of, Settings).
- Add 3-4 clickable example prompts to the empty state, one per major capability (ask a question, build a book, visualize a concept, upload course material).
- Surface Solve/Mastery Path as visible options rather than hover-only.
Filed from a read-only UX/product audit of
main. Not urgent — batching undernice-to-have.What's there
A brand-new user's first screen (
web/app/(workspace)/home) is a logo and "What would you like to learn?" above an empty composer — no example prompts, no capability cards. Two real capabilities, Solve and Mastery Path, are tucked behind a secondary hover flyout (ChatComposer.tsx:917-987) that a first-time user has no reason to open. The composer itself is well engineered once found (clean state machine, upfront file-type/size limits on drag-drop) and holds up fine on mobile behind a hamburger menu — the gap is purely the first-run experience.The interesting part
A genuinely sophisticated 10-step guided tour component already exists in the codebase —
SettingsTourOverlay.tsx— but it's wired only into Settings, a page that (see the companion "Appearance settings unreachable" issue) almost nobody but admins can even open. The onboarding investment already happened; it's just pointed at the page fewest people ever see.Suggested fix