Student Dashboard
One dashboard for demo and paid students — a Global Feed for what's happening, a Personal Feed for what's theirs, Learn for courses, Nano Skills for upskilling, and Rewards for the points that keep them coming back.
Why we were doing it
The dashboard had grown one feature at a time, and it showed. There was no shared design language across screens, so students kept relearning the interface instead of using it. Too much competed for attention at once, which made it hard to tell what actually needed action. And critical error messages looked exactly like routine notifications, so students scrolled right past the ones that mattered.
None of this was one bad screen. It was the absence of a system — no priority, no hierarchy, no consistent way to manage what the dashboard was asking of a student on any given day.
"If every message looks urgent, the student learns to ignore all of them."
One dashboard, two very different students
A demo student and a paying student land on the same platform with completely different stakes. The dashboard had to work for both without becoming two dashboards.
See what BrightChamps actually feels like before asking parents to pay.
Couldn't tell which features were locked until they clicked into them.
"Why does this look exactly like the paid version if half of it isn't mine?"
Keep momentum across Coding, Robotics, and Financial Literacy without losing track.
Home screen was so dense it was hard to tell what needed attention today.
"I just want to know: what's next for me right now?"
Needs large, visual, low-text navigation — reads slower, relies on icons and color more than labels.
Wants autonomy — streaks, rank, and course history — and has little patience for hand-holding UI built for younger siblings.