PocketGuard
A personal finance planning platform designed to help users organize, understand and plan their money.
- Next.js
- TypeScript
- Prisma
- Recharts
- JWT
- Zod
- Tailwind CSS
01 · Context & Product
The Problem & Product Solution
Personal money information is scattered across notes, spreadsheets and memory, which makes it hard to answer a simple question: where do I stand financially right now?
Most finance tools are either too heavy for an individual or too shallow to be trusted with real planning.
PocketGuard is a personal finance planning platform built to help users organise, understand and plan their money from a single dashboard.
Users sign in securely, record their financial data through structured forms, and see it summarised visually so decisions are based on something more than a hunch.
My Role & Ownership
Product thinking, frontend architecture, dashboard UI, authentication and data handling.
02 · Technical Architecture
How It's Engineered
Next.js and TypeScript with a component-driven structure, styled in Tailwind CSS. Charts are rendered with Recharts inside focused client components while the surrounding page stays server-rendered.
Prisma models the financial records and user data, with migrations keeping the schema in step with the product as it evolves.
Stateless JWT authentication using jose for token handling, with bcrypt password hashing on stored credentials.
Zod validates every financial entry before it touches the database — malformed or missing data is rejected at the boundary.
03 · Problem Solving
Engineering Challenges & Solutions
Financial data is easy to enter badly: missing fields, wrong types and inconsistent values quietly corrupt the whole picture.
Shared Zod schemas validate on both the form and the API route, so users get immediate feedback while the server stays authoritative.
Dashboards get slow and cluttered as records grow.
Aggregation happens on the server and charts receive only the summary they need, keeping the client light and the UI responsive.
04 · Scope
Shipped Features
Implemented and working in the codebase today.
- Account creation and secure sign in
- Financial dashboard summarising the user's data
- Charts and data visualisation of financial information
- Structured forms with server-side validation
- Persisted user data across sessions
- Responsive dashboard usable on phone, tablet and desktop
05 · Craft & Quality
Interface, Responsiveness & Performance
Interface Design
The dashboard leads with clarity: the most important numbers are readable at a glance, and everything else supports them instead of competing for attention.
Charts are used only where they genuinely explain data better than a list would — visualisation earns its place rather than decorating the screen.
Dense financial information is broken into cards and sections so the layout stays calm on small screens.
Responsive Behaviour
The dashboard is designed mobile-first: chart cards stack vertically, tables simplify, and primary actions stay within thumb reach.
Layouts are verified from 320px up so financial summaries never introduce horizontal scrolling.
Performance & Accessibility
Charts are client-only islands, leaving the rest of the page server-rendered.
Only necessary data is sent to the browser, keeping payloads small as the record count grows.
06 · Result & Reflection
Outcome & Takeaways
PocketGuard is currently in active development; the public repository reflects the work in progress.
It is my strongest example of product thinking applied to a data-heavy interface.
Key Engineering Lessons
- In finance products, trust is a design feature — clear validation, honest states and readable numbers matter as much as visuals.
- Validating at the boundary instead of inside components keeps forms and APIs consistent without duplicated logic.
- Designing the dashboard before the entry forms clarifies exactly which data the product actually needs.