hamsathumar/ai-powered-expense-tracker

Purpose and runtime

A local-first personal expense tracker for accounts, transactions, categories, people/shared expenses, recurring payments, reports, backup, and voice entry. It is an Expo/React Native TypeScript app, runnable on Android, iOS, web, and Expo Go. Primary startup/routing is Expo Router’s file-based route tree under src/app/, rooted at src/app/_layout.tsx.

Navigation and screen composition

The application shell establishes shared providers and navigation, while the tab layout is the primary user entry point. Main areas are dashboard, accounts, reports, and settings; stack routes cover create/detail/edit flows.

• src/app/_layout.tsx

• src/app/(tabs)/_layout.tsx

• src/app/(tabs)/index.tsx

• src/app/transaction/new.tsx

• src/app/account/[id].tsx

Persistence boundary

src/db/ is the persistence layer and should be the exclusive boundary between screens/services and stored financial data. Database initialization, migrations, seed data, and backup logic are separated from entity-specific query modules.

• src/db/client.ts

• src/db/migrations.ts

• src/db/queries/transactions.ts

• src/db/backup.ts

Financial domain logic

src/domain/ holds pure business rules and typed models, separate from React UI and database access. It covers money handling, transaction/account activity, recurring schedules, expense splitting, settlements, and backup-format validation—logic that must remain deterministic and reusable across screens and persistence operations.

• src/domain/types.ts

• src/domain/money.ts

• src/domain/billSplit.ts

• src/domain/recurring.ts

• src/domain/settlement.ts

Transaction and account workflows

Transaction creation/editing is composed from reusable financial input components and persists through transaction/account/category/people query boundaries. Account and category routes provide management/detail flows; account activity is calculated by domain logic rather than embedded in presentation.

• src/components/TransactionForm.tsx

• src/app/transaction/[id].tsx

• src/db/queries/accounts.ts

• src/db/queries/categories.ts

• src/db/queries/people.ts

Shared expenses, recurring items, and reporting

People, bill splitting, and settle-up form a shared-expense workflow. Recurring items have dedicated list, detail, edit, payment, display, and query layers. Reports obtain persisted aggregates through a distinct query module and render visual summaries such as donut charts.

• src/app/bill-split.tsx

• src/app/settle-up.tsx

• src/app/recurring/[id]/payments.tsx

• src/db/queries/recurring.ts

• src/db/queries/reports.ts

Voice AI, files, and app-wide presentation state

Voice capture routes through an AI boundary that builds prompts, calls Gemini, validates parsed output, and protects configuration; parsed results should feed normal transaction workflows rather than bypassing domain validation. Backup-file and profile-photo services isolate device/file operations. Theme and currency contexts provide app-wide display configuration, while pending-count state supports queued work indicators.

• src/app/voice.tsx

• src/ai/gemini.ts

• src/ai/parseVoice.ts

• src/ai/validate.ts

• src/services/backupFile.ts

• src/theme/CurrencyContext.tsx