Native Android EMI Device Management App

# Android EMI Device Management & Remote Device Locking Application ## Project Overview We are looking for an experienced **Native Android developer or Android development company** to develop a mobile application for a **mobile-device financing/EMI business**. The application will be installed on mobile devices that are financed through EMI. The system should allow authorized administrators to remotely manage the financed device based on the customer's EMI/payment status. If a customer fails to make the required payment according to the agreed financing terms, the backend should be able to send an authorized command to **restrict/lock the financed device**. Once the payment is received and verified, the device should be restored/unlocked according to the configured business rules. The solution must use **official Android device-management capabilities** and should be secure, reliable, and suitable for production use. We are **not looking for rooting, exploits, malware, or methods that bypass Android security**. --- # Strong Preference — Previous Similar Experience **Developers or companies who have already developed a similar EMI/mobile-financing device-locking or Android device-management solution will be strongly preferred.** If you have previously developed a similar application, please share: * Previous project name * Live application/website, if available * Google Play Store link, if applicable * Demo video/screenshots * Your role in the project * Android Device Owner / DPC implementation details * Remote lock/unlock functionality * Device enrollment mechanism * Backend/API architecture * Supported Android versions * Any relevant client/project references you are permitted to share ### Relevant previous experience includes: * Mobile phone EMI financing * Financed-device locking * Android MDM * Android Enterprise * Device Owner / DPC * DevicePolicyManager * Kiosk applications * Remote Android device management * Loan/EMI applications * Retail/mobile financing platforms **Please share your previous work examples in your proposal.** Generic Android application experience alone will not be sufficient. We specifically want someone who understands **native Android device management**. --- # Technology Requirements The application should be developed using **native Android technology**. ### Preferred stack * Kotlin * Android SDK * Android Jetpack where appropriate * DevicePolicyManager * Android Device Owner / DPC * Android Enterprise APIs * Firebase Cloud Messaging (FCM) * REST APIs * HTTPS * JSON * MySQL/backend API integration **No Flutter, React Native, or other cross-platform framework is required.** --- # Core Features ## 1. Device Registration Each financed device should be registered with our backend and associated with: * Customer * Finance/loan account * Device information * Device identifier/IMEI where legally and technically appropriate * EMI schedule * Device status * Registration date The device should have a unique and securely authenticated relationship with our backend. --- ## 2. Device Management The backend should be able to maintain device statuses such as: * Active * Payment Pending * Restricted * Locked * Unlocked * Offline * Suspended --- ## 3. Remote Device Lock / Restriction An authorized administrator should be able to initiate a device lock/restriction from the backend. Expected communication: **Backend → FCM → Native Android Application → Android Device Management → Lock/Restriction** The command must be securely authenticated and validated. --- ## 4. Remote Unlock After successful EMI/payment verification: **Backend → FCM → Native Android Application → Android Device Management → Restore Device Access** Unlock commands must only be accepted from an authorized backend. --- # 5. Device Owner / DPC The developer must evaluate and implement the appropriate Android **Device Owner / Device Policy Controller (DPC)** architecture. The proposal should clearly explain: * How Device Owner will be established * How device enrollment will work * Whether provisioning is required during initial device setup * How the application will survive device reboot * How device policies will be maintained * What restrictions can be applied * What happens after factory reset * How supported Android versions will behave --- # 6. Background Operation The application should be capable of receiving authorized backend commands even when the user is not actively using the application, subject to Android's supported device-management architecture. We do **not** want a solution that simply depends on a normal background service running continuously. The developer should use the appropriate combination of: * Android Device Management APIs * FCM * WorkManager where appropriate * Device Owner/DPC mechanisms * Native Android services where genuinely required --- # 7. Device Reboot & Offline Handling The solution must properly handle: * Device reboot * Internet disconnection * FCM delivery delays * Application restart * Backend/API downtime * Device temporarily offline * Network reconnection * Device status synchronization --- # 8. Security Security is extremely important. The application should implement: * HTTPS * Secure API authentication * Device authentication * Customer/device binding * Secure FCM command validation * Server-side authorization * Lock/unlock command verification * Audit logs * Protection against unauthorized commands * Appropriate application tamper protection The developer must not use: * Root access * Exploits * Malware * Security bypasses * Unauthorized system modifications The solution should use legitimate Android-supported device-management capabilities. --- # 9. Backend Integration The Android application will communicate with our backend using REST APIs. Expected APIs include: * Device registration * Device verification * Customer/device mapping * EMI/payment status * Lock command * Unlock command * Device status * Heartbeat/synchronization * Command acknowledgement *