Learnoverse
[One line that frames the problem Learnoverse solves.]
Draft case study. The structure is real, but the copy in brackets and the Figma exports still need filling in. Everything lives in data/projects.ts.
- Role
- UI/UX Designer
- Timeline
- [Add duration]
- Platform
- Mobile App + Website
- Tools
- Figma
[Add a short paragraph: who Learnoverse is for and what it does. Alongside the marketing site, the work included product screens, like a Practice World flow with marked-answer review, so there's a real product story here worth telling.]
The problem
[What was broken, missing or slow before Learnoverse existed, and who felt that problem most?]
The approach
[How did the problem turn into flows and screens? Call out anything unusual about the information architecture or the interaction model.]
Key screens
[Pick two or three screens worth explaining, and say why each is built the way it is.]
The outcome
[What shipped? What changed for the people using it, or for the business behind it?]
Practice World
Tell me what you're building. I'll ask why.
© 2026 Parth Sikka · built at my desk in India, mostly at night
Say hi anytime