FlowMoney

01 / Context

The problem to solve.

Income, expenses, subscriptions, and savings goals are difficult to understand when records are scattered or shown without useful summaries.

02 / Approach

From need to interface.

FlowMoney organizes transactions and goals in a responsive dashboard, presenting account summaries and charts before detailed records.

What I built

• Responsive finance dashboard
• Income and expense tracking
• Financial goals and data visualization
• Frontend-to-API integration

03 / Implementation

How it fits together.

A React and Vite frontend uses Firebase client services, Recharts, and Socket.IO integration. A separate Express and TypeScript API uses Better Auth, MongoDB, Socket.IO, Web Push, email, and an AI-service adapter. The frontend is deployed on Vercel.

Decisions that shaped the build

• Used summary-first dashboard views before transaction-level detail
• Kept frontend and backend concerns in separate repositories
• Applied backend middleware to authentication and joint-account access rules

Challenges

• Presenting several financial data types clearly on mobile screens
• Enforcing access to shared-account records
• Keeping dashboard data synchronized with API-backed changes

04 / Delivery & lessons

Built, tested, and still learning.

Testing

The deployed frontend and backend repositories do not currently expose automated test scripts. Available validation is linting and production build for the frontend plus TypeScript build for the backend. Unit tests for financial calculations and access rules, API integration tests, and end-to-end transaction flows remain priorities.

Deployment

The frontend is live on Vercel; backend setup and production build commands are documented separately.

What I took forward

• Financial dashboards need clear information hierarchy before added visual detail
• Shared accounts require explicit authorization checks on every record
• Testability should be planned early around calculations and ownership rules