The Problem
Personal finance apps require trusting cloud services with your most sensitive data—bank balances, spending patterns, income details. For many users, that's a dealbreaker. They'd rather track finances manually (or not at all) than upload their financial life to someone else's servers.
The trust problem isn't just about security breaches. It's about control. Who has access to your data? How is it being used? Can you ever truly delete it? These questions create friction that prevents adoption, even when users acknowledge they need better financial tracking.
Meanwhile, manual tracking is tedious. Typing transactions is time-consuming. Categorizing expenses is repetitive. Users want intelligent insights—budgets, trends, recommendations—but not at the cost of privacy.
Key Decisions
- On-device processing—privacy by architecture: No cloud servers, no API calls, no data uploads. Financial data stays on the device, encrypted at rest using iOS security features.
- Photo-first data capture: Take a picture of a receipt, and Vision Framework + LLM extract the transaction details. Minimal typing required.
- Proactive insights and reminders: The LLM analyzes spending patterns and surfaces insights—"You've spent 30% more on dining this month" or "Rent payment due in 2 days."
- CoreML for on-device LLM inference: Leveraging Apple's CoreML framework to run language models directly on iPhone's Neural Engine—no internet required.
- Building in public: Documenting the entire build process on YouTube to show how product decisions, technical trade-offs, and user testing shape the final product.
PM Skill Being Developed
On-Device AI & Privacy-First Design: This project is teaching me how to design AI products where privacy isn't a feature—it's the foundation. It's forcing me to think about capability constraints (what can smaller models do well?) and user expectations (when do users want AI help vs. manual control?).
Building in Public: Documenting the journey publicly creates accountability and demonstrates product thinking in real-time—not the polished case study, but the messy process of building, testing, and iterating.