Finance systems

FinTrack

A finance platform that brings accounts, budgets, recurring bills, savings goals, imports, exports, and security history into one clear product surface.

SYSTEMPersonal finance operating surface

EVIDENCEPublic API repository · live app verified

SOURCEGitHub repository Live app

ARCHITECTURE / CONCEPTUAL VIEW

Derived from public repository documentation

01Finance UIinterface

02React Query Hooksservice

03FinTrack APIservice

04OpenAPI Typesdata

05Finance Domainsdata

06Vercel Runtimeinfrastructure

CHALLENGE

What the system needed to solve.

Personal finance products become hard to trust when daily transactions, budgets, recurring commitments, savings goals, imports, exports, and account security live in separate mental models. FinTrack needed to make the user’s financial state understandable without flattening the system into a simple dashboard.

CONSTRAINTS

The boundaries that shaped the build.

Cover real product routes across onboarding, dashboard, transactions, accounts, budgets, reports, savings, recurring bills, and settings.
Coordinate frontend state, API calls, generated OpenAPI types, auth hydration, and httpOnly refresh-token rotation.
Keep unfinished security-history UI and unapproved metrics clearly separated from completed product evidence.

ENGINEERING DECISIONS

Choices with consequences.

Finance is treated as an operating system

Accounts, budgets, bills, goals, and history are framed as connected workflows instead of isolated feature pages.

API contracts shape the frontend

Generated OpenAPI types, React Query hooks, Axios, and domain components keep the product interface aligned with the backend contract.

Operational states are designed in

Loading, empty, error, retry, dry-run import, export, and session-management states are treated as core UX rather than edge decoration.

RELIABILITY CONSIDERATIONS

Prepared for the operating reality.

Live application endpoint is publicly reachable
Frontend documents passing lint and production build checks
Unit, hook, and Playwright test surfaces exist for continued coverage
Refresh tokens remain in backend-set httpOnly cookies instead of localStorage

OUTCOMES / HONEST EVIDENCE

What can be stated today.

The local web app documents implemented routes for auth, onboarding, dashboard, transactions, accounts, budget goals, reports, savings, recurring bills, and settings.
Audit/security history UI, broader cross-browser coverage, screenshots, and user metrics are pending before launch.

TECHNOLOGY