Offline Android Billing App Build
Budget: ₹1,500 – ₹12,500 INR
I already mapped every screen and interaction in a Figma file; now I need a skilled Android developer to bring that design to life as an offline-first billing application.
Core scope
• Invoice generation – users must be able to create, edit, preview, and share invoices even with no internet connection. PDF export and sequential invoice numbers are part of the flow.
• Customer management – add, search, update, and view a customer’s past invoices locally.
Because the app must work reliably without connectivity, please plan on a lightweight local database (Room/SQLite or a comparable approach), careful state handling, and background sync hooks so I can later add cloud backup if I choose.
I will provide:
• Complete Figma design and UX specs.
• Field definitions, invoice numbering rules, and sample data.
You will deliver:
1. Production-ready APK plus full, well-commented source code.
2. Clear build/run instructions.
3. A brief hand-off call or video walkthrough.
Kotlin is preferred, but clean Java is acceptable if you outline the trade-offs. Follow Android best practices (MVVM or similar, Jetpack components, material guidelines) so the codebase is easy to maintain.
If this sounds straightforward to you, let me know your estimated timeline and any earlier examples of offline data-centric apps you’ve built.
Core scope
• Invoice generation – users must be able to create, edit, preview, and share invoices even with no internet connection. PDF export and sequential invoice numbers are part of the flow.
• Customer management – add, search, update, and view a customer’s past invoices locally.
Because the app must work reliably without connectivity, please plan on a lightweight local database (Room/SQLite or a comparable approach), careful state handling, and background sync hooks so I can later add cloud backup if I choose.
I will provide:
• Complete Figma design and UX specs.
• Field definitions, invoice numbering rules, and sample data.
You will deliver:
1. Production-ready APK plus full, well-commented source code.
2. Clear build/run instructions.
3. A brief hand-off call or video walkthrough.
Kotlin is preferred, but clean Java is acceptable if you outline the trade-offs. Follow Android best practices (MVVM or similar, Jetpack components, material guidelines) so the codebase is easy to maintain.
If this sounds straightforward to you, let me know your estimated timeline and any earlier examples of offline data-centric apps you’ve built.