Contact person: Tenant Payment & Maintenance mobile App and back end ERP Next property management system.

Phone:Show

Email:Show

Location: Dar es Salaam, Tanzania, United Republic of

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I run our property portfolio on ERPNext and now need a companion mobile app so tenants can handle everything from their phones. The same build has to run smoothly on both iOS and Android and plug directly into my existing ERPNext instance (latest stable version).

Core flow
• Secure login that authenticates against ERPNext’s tenant records.
• Real-time rent and service-charge balances pulled via the REST API.
• In-app payment screen that supports Credit/Debit Cards, Bank Transfer rails, and the major Digital Wallets, with all transactions instantly posted back to ERPNext and a PDF receipt generated.

Notifications
Every successful payment, new invoice, expiring lease or maintenance-ticket update should trigger a push notification first and a fallback email if the message isn’t opened within a set time. I already have SMTP configured; you’ll wire push through Firebase (or another proven service you prefer) and expose the settings so I can swap keys later.

Maintenance tickets
Tenants can create, view and comment on tickets. New photos or voice notes have to sync to the “Issues” doctype in ERPNext, respecting existing status workflows.

Contract vault
Lease agreements stored in ERPNext should be downloadable from the app and viewable offline once cached.

Admin console
A light, web-based panel (could be bundled in the same codebase) lets me toggle notifications, view logs, and push announcements.

Deliverables
1. Source code with clear README and environment files for staging and production.
2. Two signed builds ready for App Store and Google Play submission.
3. Post-deployment support to squash any critical bugs found in the first month.

I’m happy with Flutter, React Native or another cross-platform stack as long as performance is solid and the codebase is cleanly structured for future features." (client-provided description)