Android App Development Skill

Detailed Guide

Read [the detailed guide](references/detailed-guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use This Skill

• Use when deciding on a tech stack (see §1 Stack Selection)
• Use when setting up project architecture (see §2 Architecture)
• Use when designing UI, screens, or a design system (see §3 UI & Design)
• Use when ensuring code quality, patterns, or APIs (see Best Practices)
• Use when implementing error handling or debugging crashes (see §5 Error Handling)
• Use when planning testing strategy (see §6 Testing)
• Use when configuring build, CI/CD, or release pipelines (see §7 Build & Release)
• Use when optimizing performance or memory (see §8 Performance)
• Use when debugging or fixing bugs (see §9 Debugging)
• Use when following the full development roadmap (see §10 Development Roadmap)
• Use when needing deep reference for a stack (see references/ directory)

Limitations

• This skill is scoped to Android and Android-adjacent delivery paths; it does not cover iOS-only architecture, App Store release operations, or Apple platform UI guidance.
• Version numbers, Play Console policy thresholds, and recommended libraries can change; verify release-critical details against current Android, Google Play, and library documentation before shipping.
• Code snippets are architecture patterns, not complete applications; adapt package names, dependency versions, permissions, privacy disclosures, and security controls to the actual project.
• The guidance does not replace device QA, accessibility review, security review, legal/privacy review, or store compliance checks for a production release.