Android
Android: Implement an Android feature that respects lifecycle and device diversity. Review the target devices, OS versions, app lifecycle, permissions, navigation, and network behavior and produce an Android change with device matrix.
--- name: mobile-development-android description: Use for Android-specific feature work where lifecycle, API level, system permissions, or device variation can change the result. license: MIT metadata: author: Thrive category: mobile-development --- # Android ## When to use Use for Android-specific feature work where lifecycle, API level, system permissions, or device variation can change the result. ## Boundaries Use the Flutter or React Native skill for changes owned by those app layers. Use Mobile UI for a design review without Android implementation. ## Inputs Read the app module, build files, minimum and target SDK, navigation setup, UI toolkit, manifest permissions, and existing test approach. Identify the devices and OS versions the project supports. ## Method 1. Trace the user action through screen state, navigation, repository or service call, and the Android lifecycle. Find where state is restored after process death. 2. Implement the feature within the project's existing architecture. Request permissions at the point of need, handle denial and permanent denial, and avoid blocking the main thread. 3. Test configuration changes, background and foreground transitions, slow or absent network, and the smallest supported API level. Include large text and screen-reader behavior when UI changes. ## Decision rules - If an OS version changes permission or background behavior, branch on the documented API contract and test both paths. - If the app uses a cross-platform framework, keep platform-specific work in the native boundary and document the bridge contract. ## Verification - A normal user completes the task on a supported device. - State survives recreation or the user receives an explicit recovery path. - Permission denial and network failure do not trap the user or silently discard work. ## Stop and handoff If a required device, API contract, or permission flow cannot be tested, state the exact unverified path and the device or evidence needed before release. ## Output Return the changed files or implementation plan, supported-device matrix, permission and lifecycle decisions, and test results by device/API level. <!-- MIT License Copyright (c) 2026 Thrive Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -->