Roadmap
What is planned, and the one thing that will not change
SnapBill will keep its shape: your bills stay on your phone, and the only way out is a package you send yourself. Everything below is built on that, not around it.
Shipped
- Capture with five quality checks, auto-straighten, long-bill sectioning, multi-page bills
- PDF invoice import
- On-device reading: amount paid, date, merchant and address, invoice number, GSTIN / TRN / VAT number, GST and VAT breakups
- Custom categories and payment types, learned merchant categories
- Duplicate warning by photo and by content
- Multiple currencies with a home currency and hand-entered rates; honest totals
- Month-wise export: ZIP with images grouped by payment type, Excel summary with totals sheet, verifiable manifest
- Explicit Pending → Submitted tracking, export history
- Insights, search, filters
- App lock (PIN), on-device feedback with “What SnapBill read”
Planned: hardening the personal tool
- Encrypted backup and restoreOne archive of everything, encrypted with a passphrase you choose, saved through the share sheet to your own drive or cloud, restored on a fresh install. Still no server of ours; the file goes where you put it.
- Better reading on hard billsOn-device AI models, where the phone’s hardware supports them, for the faint thermal receipts that today’s rules struggle with. Same privacy: on the phone.
- Optional cloud reading, off by defaultFor phones that cannot run the on-device model, an opt-in switch that sends the bill image to a stateless reading service and gets fields back. Nothing stored, nothing logged. The switch’s own label will say exactly that, and it stays off unless you turn it on.
- RemindersLocal notifications only, such as “3 bills pending export” at month-end.
- Share to SnapBillSending a photo or PDF straight from WhatsApp, mail or the gallery into the app, without opening it first.
Planned: getting bills into company systems
Every SnapBill export is already a versioned package with a manifest. Future integrations consume that same package. They differ only in where it is sent, never in what it contains, so the app you use today is already producing what these targets will accept.
Submit to TaskLive Ganav. A user-initiated push of an export package to a company’s Ganav submission inbox. Your app stays private; the company receives only what you explicitly submit. On the Ganav side: a review queue for accounts, duplicate detection by manifest hash, and employee-to-company linking by invite code.
Zoho Books, Tally, and custom endpoints. The same package delivered to third-party systems, built and supported as integration work for companies that want it.
Planned: a public product
- Public listings on Google Play and the App Store
- Localisation, starting with Hindi and major Indian languages
- Onboarding for first-time users, deeper category customisation, multi-currency polish
Not planned
Multi-device sync. Sync needs a server in the middle, and a server in the middle is exactly what SnapBill does not have. Backup and restore covers moving to a new phone.
Accounts. There is nothing on the other end to log into. That will stay true.
Want something not listed? Tell us.