- Home
- Skills
- Mobile Development
- Android Target SDK 36 Upgrade: Play Requirement, Android 15/16 Changes and 16 KB Pages
Works with the AI Agents you already use
Android Target SDK 36 Upgrade: Play Requirement, Android 15/16 Changes and 16 KB Pages
Move an Android app to targetSdk 36 for Google Play, fixing every Android 15 and 16 behavior change and verifying 16 KB page-size support.
$3
Android Target SDK 36 Upgrade: Play Requirement, Android 15/16 Changes and 16 KB Pages
Example session with this skill installed
Our Play Console says the app must target API 36. It's a Kotlin app on targetSdk 34 with AGP 8.5 and one native video SDK. Upgrade it and tell me what will break.
- Read your context and instructions
- Compiled the android target sdk
A target SDK 36 upgrade report: toolchain bump plan (AGP 8.9.1+, Gradle 8.11.1+, NDK r28), scanner findings with file:line (status-bar color calls, onBackPressed override, portrait lock on the main activity, dataSync service without onTimeout), the fix applied for each, a 16 KB alignment result for the video SDK, the remaining temporary opt-outs and a device test matrix.
Connects securely to your tools. The creator never sees your data.
About this skill
Google Play requires new apps and updates for phones and tablets to target Android 16 (API 36). Raising targetSdk turns on every Android 15 and 16 behavior change at once: enforced edge-to-edge, predictive back, ignored orientation locks on tablets and foldables, foreground service time limits and more.
This skill makes that upgrade controlled and verifiable:
- Scan the project with a bundled read-only Python script that reports SDK levels, toolchain versions, native libraries and every line matching a known API 35 or 36 risk.
- Upgrade the toolchain (AGP, Gradle, NDK), then compileSdk and targetSdk, with exact config for native Gradle, Flutter, React Native, Expo and Capacitor.
- Fix each finding with tested patterns for insets, back handling, large screens, foreground services and OpenJDK API changes.
- Verify 16 KB page-size alignment for NDK and third-party
.sofiles ahead of the 1 February 2027 Play cutoff. - Report findings, temporary opt-outs and a device test matrix in a ready-to-share Markdown format.
Requirements and dates are taken from Google's official pages (cited inside the skill) as of October 2026.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.
Covers phone and tablet apps targeting API 36. Wear OS, Android TV, Android XR and Automotive apps have different targets and are only summarized. API 34 (Android 14) changes are listed at a high level and link to the official page. The scanner flags candidate lines by pattern; each match still needs human review. Deadlines reflect Google's published pages as of October 2026.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 19 days ago
- Software
- expo
Node.js
- Optional
Python 3Android SDK build tools
Python 3 only runs the bundled read-only scanner. Android SDK build tools are only for alignment checks on native apps.
Permissions
File Scopes
The bundled scanner is read-only, uses only the Python standard library and makes no network calls.