All projects

Project case study

Ledgerly

Personal finance tracking reduced to the actions and signals people use every day.

Role
Full-Stack Developer & UI Designer
Status / year
Completed · 2026
Ledgerly personal finance dashboard landing page

Overview

Personal finance tools are often abandoned because recording activity takes too much effort or the dashboard demands accounting knowledge. Ledgerly explores how a tracker can remain genuinely useful while feeling calm and lightweight.

The product prioritizes quick interaction, restrained hierarchy, and a small set of meaningful summaries over feature quantity.

01

Balancing clarity and usefulness

Showing too little makes a financial dashboard unhelpful. Showing everything at once turns it into another intimidating system. Ledgerly places balance, monthly income, expenses, savings rate, cash flow, category spending, recent transactions, and budget status in a deliberate reading order.

02

The current product

Authenticated users can record income and expenses, manage categories, filter transaction history, keep USD and PHP records explicit, set monthly category budgets, and review spending patterns and alerts.

Auth0 protects the workspace, while server-side database operations scope records to the authenticated user ID. Financial calculations are separated into reusable utilities and charts support comprehension without dominating the interface.

  • Transactions, categories, and monthly budgets
  • Cash-flow and category-spending views
  • Budget progress and threshold warnings
  • Explicit handling of USD and PHP records
  • Server-side mutations and authenticated data scoping
03

Engineering for trust

Financial records demand stricter boundaries than a demonstration dashboard. Ledgerly keeps database access on the server, scopes operations by the Auth0 user identifier, and treats database-level Row Level Security as a requirement before a public production launch.

The interface also preserves standard form and keyboard interaction. Future enhancements cannot make voice input the only usable path.

04

A deliberate future direction

The planned evolution is natural-language voice entry. A user could describe an expense or income event, review the structured interpretation, and confirm it before anything is saved.

Voice and AI commands are not currently implemented. The intended system treats parsed commands as drafts, keeps manual controls available, and never silently writes ambiguous financial records.

Technology

  • Next.js
  • React
  • TypeScript
  • Auth0
  • Supabase
  • Recharts

Have a project in mind?

Let's build something useful.

Get in touch