Contact person: Business Client

Phone:Show

Email:Show

Location: Patna, India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I’m building a native Android app that silently handles both SMS and voice traffic, and I need a developer who has proven, in-market experience with Telephony APIs on Android 8.0 (API 26) and above. The core workflow is simple: whenever an SMS arrives, the app must pick it up automatically (no keyword or user tap), forward it to my back-end, mirror it in the local inbox, and keep the whole pipeline alive even after reboots or doze mode kicks in. Outgoing texts will originate from an HTTP/JSON endpoint you expose; the device then sends them through SmsManager as if they were typed locally.

On the voice side, the same installation should enable network-level call forwarding via TelephonyManager / MMI codes. Once activated, the setting should remain sticky until the back-end turns it off.

Because the service must feel invisible to the user, foreground notifications should be minimal yet compliant with Google Play policy, and all runtime permissions (SMS, Phone, Contact read, etc.) have to be requested gracefully and only once. Reliability is critical: if the OS kills the process, it should resurrect itself through a properly declared foreground service and boot-receiver.

Key APIs & patterns you’ll be working with include:
• SmsManager, BroadcastReceiver, JobScheduler/WorkManager for SMS capture and resend
• TelephonyManager, CallRedirectionService for call manipulation
• Runtime permission flow, manifest whitelisting, and background execution limits from Android 8+ onward

Deliverables I expect:
• Full Kotlin or mixed Kotlin/Java source in a clean Gradle project
• Signed release APK and debug build variant
• Postman collection (or curl commands) that exercise the send-SMS and call-forwarding endpoints
• Brief deployment notes explaining how to re-sign and publish

Acceptance criteria:
• An SMS received on any Android 8+ test device is forwarded to the back-end within two seconds and appears intact in the device’s default Messages thread.
• Outbound SMS triggered from the API is delivered and visible in the thread.
• Network-level call forwarding toggles on/off through the provided endpoint and survives device reboot.
• The background service runs continuously for 48 hours under normal conditions without manual relaunch.

If you’ve already shipped similar telephony-heavy apps and can demonstrate compliance with the latest Google Play policies, let’s talk—your expertise will be key to hitting production quickly and cleanly." (client-provided description)