Menu

Five Android permissions, five different checks: building a setup gate that re-checks on resume
📰

Five Android permissions, five different checks: building a setup gate that re-checks on resume

DEV Community: android·ReClaim·11 days ago
#JYkg9Men
#devtoandroid#devto#dev#context#settings
Reading 0:00
15s threshold

We're building ReClaim , a minimalist Android launcher that's on Google Play . To do its job it needs five things from the user: to be the default Home app, to post notifications, Usage access, an accessibility service for system-wide blocking, and an exemption from battery optimization.

That sounds like one "permissions" problem. It isn't. Each of the five is granted in a different place, and each is checked through a different API. Only one of them is a normal runtime permission. This post walks through the screen that asks for all five: how it checks each one, why it re-checks every time the app comes back to the front, and why it never traps you.

Stack: Kotlin, Jetpack Compose, Hilt, minSdk 26 , targetSdk 36 . Snippets are trimmed from the real code; // ... marks cuts. Our first post on building the launcher touched on the Home role and Usage access in passing.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.