Secure Android Social Media Permissions -- 2
Budget: ₹12,500 – ₹37,500 INR
I’m finishing a social-media app that targets recent Android releases and I now need a specialist to wire up the sensitive permissions that Google guards most closely:
• PACKAGE_USAGE_STATS – to analyse how often users open certain screens
• SYSTEM_ALERT_WINDOW – to float chat heads and quick-reply bubbles over other apps
• FOREGROUND_SERVICE – to keep audio rooms alive even when the UI is backgrounded
• BIND_ACCESSIBILITY_SERVICE – to offer in-app captioning for hearing-impaired users
• POST_NOTIFICATIONS – to alert followers in real time
The core screens are already coded; what’s missing is a clean, policy-compliant implementation of these rights plus the runtime flows that persuade users (and Google Play reviewers) that each permission is essential.
What I’m looking for:
1. Updated AndroidManifest and gradle setup ready for API 34.
2. Kotlin or Java snippets that demonstrate each permission in action, wrapped in clear, modular classes.
3. User-facing rationale dialogs that meet Play Console guidelines.
4. A short README explaining testing steps so I can reproduce the flows in Android Studio.
We are on a one-month timeline, so momentum is important. If you have shipped an app through the Play review process with any of the above permissions, I’d love to tap into that experience.
• PACKAGE_USAGE_STATS – to analyse how often users open certain screens
• SYSTEM_ALERT_WINDOW – to float chat heads and quick-reply bubbles over other apps
• FOREGROUND_SERVICE – to keep audio rooms alive even when the UI is backgrounded
• BIND_ACCESSIBILITY_SERVICE – to offer in-app captioning for hearing-impaired users
• POST_NOTIFICATIONS – to alert followers in real time
The core screens are already coded; what’s missing is a clean, policy-compliant implementation of these rights plus the runtime flows that persuade users (and Google Play reviewers) that each permission is essential.
What I’m looking for:
1. Updated AndroidManifest and gradle setup ready for API 34.
2. Kotlin or Java snippets that demonstrate each permission in action, wrapped in clear, modular classes.
3. User-facing rationale dialogs that meet Play Console guidelines.
4. A short README explaining testing steps so I can reproduce the flows in Android Studio.
We are on a one-month timeline, so momentum is important. If you have shipped an app through the Play review process with any of the above permissions, I’d love to tap into that experience.