How mohitsingh2002/location_permission_android_11 works
Project type and purpose
• This is a single-module Android application (app/) written in Java, whose sole purpose is to demonstrate how to request and obtain the “Allow all the time” background location permission on Android 11 and above.
• The README simply references a Medium article that describes the background‐location permission flow.
File structure
• Top-level:
– build.gradle, settings.gradle, gradlew*: build system and wrapper
– app/: the Android application module
• app/ contains:
– src/main/java/com/example/blog_1_location_permissions/MainActivity.java: UI and permission-request logic
– src/main/res/: layouts, drawables, themes, strings
– src/androidTest/: instrumentation tests
– src/test/: local unit tests
– AndroidManifest.xml, proguard-rules.pro, Gradle build files
• No backend or network code, no external microservices—this is purely a client-side mobile sample.
README for additional insights
• The README confirms the focus is on handling runtime permissions for background location in Android 11+.
• There are no further architectural details or external dependencies.
a. Main Components:
– User (Actor)
– UI Layer: MainActivity + layout XML
– Permission Manager: logic in MainActivity invoking AndroidX or platform APIs
– Android Framework:
• ActivityManager, Context, Permissions API
• LocationManager / FusedLocationProviderClient (if used)
– Device Hardware: GPS chip, cellular/Wi-Fi radios
– Build & Test Pipeline: Gradle, local unit tests, instrumentation tests
b. Relationships & Interactions:
– User taps “Allow” → MainActivity calls requestPermissions()
– Permission Manager queries Android Framework → OS displays permission dialog
– On grant, MainActivity registers for location updates via LocationManager
– LocationManager ↔ Hardware providers (GPS, network)
– Tests drive MainActivity or mock the permission flow
c. Architectural Patterns / Principles:
– Single-Activity pattern for demo simplicity
– Separation of concerns: UI code vs. permission/business logic vs. OS services
– Resource organization (res/ for UI, java/ for code, tests separated)
d. Key Technologies & Frameworks:
– Android SDK (API 30+), AndroidX Permission library (if included)
– Gradle build system, ProGuard (for release rules)
– JUnit (src/test) and Espresso/AndroidJUnit (src/androidTest)