04—Personal product · Systems · 2024
Personal Dashboard
A productivity and personal management system.
RoleProduct, architecture, full implementation
Year2024
StackNext.js · Supabase · TypeScript
Today
08
Open loops
Focus
Personal Dashboard
Problem
Personal tooling fragments quickly: tasks in one place, notes in another, calendars somewhere else. Most dashboards look organized and still ask you to remember the system.
Idea
Build one place that is boring in the right ways — fast, private, structured — and flexible where life is not. A dashboard for the operator, not for an audience.
Role
I designed the information architecture and built the system end to end: Next.js frontend, Supabase data layer, and the daily workflows I actually needed.
Architecture / engineering
A Next.js application with typed data access to Supabase. Views are split by job — today, projects, notes — rather than by database table. The system is private by default.
Technology
Next.js and TypeScript on the surface. Supabase for auth, Postgres and persistence. The stack is intentionally ordinary so the product can stay maintainable.
Challenges
The temptation is to add every widget. The work is deciding what deserves a permanent place on the screen, and what should stay a click away.
Solution
Start from the morning view. Surface only what changes a decision today. Keep the rest structured, searchable and quiet.
Result
A personal system I can maintain. It is not a public product — it is a reminder that the best way to understand product quality is to live in the software.
What I learned
If you would not open it on a messy Tuesday, it is not a productivity tool. It is a prototype of one.
Visuals
Interface study. Production screenshots can replace these compositions through the project media fields.
Today
08
Open loops
Focus
Personal Dashboard
Product
Personal Dashboard
A private operating system for work, notes and the parts of life that usually live in too many tabs.