Split Bill — Multi-Currency Group Expense Splitting PWA
Product, Design & Full-Stack Engineering (End-to-End) · Live Production PWA · splitbill.liefisca.com
Personal AI Product · 2026
Designed, architected, and shipped a live mobile-first PWA end-to-end—combining a debt-simplification engine, 20+ currency support, and AI receipt scanning for real-world group expenses.
- Currencies supported
- 20+
- End-to-end product & code
- 0→1
- Mobile-first installable
- PWA
- Shipped in production
- Live
The Problem
Most expense splitters break on real-world group meals and trips: multiple people paying portions of a bill, uneven line-item splits, taxes, service charges, tips, mixed currencies, and paper receipts in local languages.
Product Tradeoffs & Decisions
- Centered the UX around minimal-transfer debt simplification rather than raw pair-by-pair ledgers, reducing settlement friction after multi-day trips.
- Modeled tax, service charge, and tip allocation explicitly alongside equal/exact/percentage/share splits instead of forcing manual math.
- Built as an installable mobile-first PWA rather than separate native iOS/Android apps so anyone in a group can join immediately via browser link.
Technical Approach
- Built full-stack with React, TypeScript, and PostgreSQL with support for multi-payer transactions and 20+ currencies.
- Implemented a debt-simplification engine that collapses complex who-owes-whom graphs into the minimum number of settlement transfers.
- Integrated AI/LLM receipt scanning to parse photos—including local-language receipts—into itemized, auto-categorized expenses.
Cross-functional Execution
- Owned the full product lifecycle end-to-end: user workflows, UI design, database schema, AI parsing pipeline, deployment, and versioned post-launch iterations.
Measured Outcomes
- Shipped and maintained a live production web application at splitbill.liefisca.com.
- Demonstrates full-stack ownership from product sense and UX edge cases through AI integration and deployment.