For years, managing expenses and tracking product warranties have lived in two completely disconnected worlds.
Expense tracker apps → basically a photo dump with categories
Physical receipts → stuffed in drawers, fading over time
And when you actually need them… they’re nowhere to be found.
💥 The Real Problem
Let’s take a simple (and painful) scenario:
Your 11-month-old washing machine starts making a strange noise.
You:
Try to find the receipt
Dig through drawers / old emails
Finally locate it… or worse, don’t
And then realize:
The 1-year warranty expired yesterday.
That’s an unexpected repair cost you could’ve avoided.
🤔 Why Existing Apps Don’t Help
Most expense trackers answer:
“Where did your money go?”
But they don’t answer:
“Is this product still under warranty?”
That missing link is exactly what I wanted to solve.
🚀 Introducing BillBox
BillBox is a mobile app designed to bridge that gap.
It acts as:
📊 A daily expense tracker
🧾 A receipt vault
⏳ A warranty monitoring system
All in one place.
🔄 How It Works
Scan Receipt / Upload PDF
↓
Auto Categorization
↓
Stored in Warranty Vault
↓
Expiry Tracking
↓
Proactive Notifications
No more guessing. No more last-day surprises.
🔐 Privacy First Approach
One of my core priorities while building this:
✔️ On-device data storage (your data never leaves your phone)
🔒 Biometric app lock
📤 Export to PDF/CSV anytime
No cloud dependency. No unnecessary data sharing.
🧩 Built With a Simple Goal
Make financial tracking actually useful in real life, not just analytical.
Because knowing you spent money is one thing…
But knowing you can still claim warranty is way more valuable.
📱 Current Status
The app is feature complete and currently in the final testing phase.
I'm opening up closed testing for Android users.
🙌 Looking for Testers
If you’ve ever:
Lost a receipt
Missed a warranty claim
Or just want a cleaner way to track expenses
👉 Drop a comment or reach out — I’ll share an invite link.
💬 Feedback Welcome
Would love to hear thoughts from fellow developers:
What features would you expect in something like this?
Would you trust fully on-device storage?
Any ideas to improve this workflow?
Top comments (0)