Problem
Students know they have work to do, but the plan is scattered across notes, chats, and memory.
Study Buddy
Goals
- Make the next study action visible.
- Avoid becoming project-management overhead.
Solution
A Next.js app shell with task, resource, and progress surfaces built as independent modules so a backend can be added without a rewrite.
Key features
- Task planning
- Resource organisation
- Progress view
- Responsive app shell
Architecture
App shell with independent task, resource, and progress modules; Framer Motion for transitions between views; structure ready for persistence.
Technical decisions
- The shell is calm and repeatable so it can be opened every day.
- Progress is a workflow signal, not a decorative chart.
- Motion is limited to view transitions.
Tech stack
- Next.js
- TypeScript
- Tailwind CSS
- Framer Motion
- Vercel
Hardest part
Enough structure to help, not so much that students abandon it.
What I learned
Productivity tools should protect momentum. Every extra field has to earn its place.
Result
A deployed MVP of the interface layer.