One portfolio.
Five deadline rules.
Map sanitized App aliases before the August 31, 2026 target API deadline. Keep mobile, Wear, TV, Automotive and XR requirements—and new, update and existing-availability effects—separate from the real build and Console actions.
Target API deadline responsibility map
| App | Factor / release | Current / required | Deadline / extension | Test / availability | Evidence / owner | Decision / result |
|---|
Target, test and release queue
“Evidence recorded” means only that one abstract record is coherent. This page did not inspect targetSdkVersion, behavior changes, dependencies, tests, Play policy status or extension eligibility; submit or roll out a release; preserve discoverability; prove compatibility; or guarantee acceptance.
Project and release boundary: analysis stays in this browser. Enter only fictional aliases, API numbers, dates and safe evidence references. Never paste a real package name, manifest, Gradle/build file, source, dependency report, APK/AAB, Console export, account, credential, user or unpublished roadmap. This page does not read targetSdkVersion, evaluate behavior changes, test compatibility, determine exceptions/extensions, connect to Play, submit or roll out, or guarantee availability or acceptance. Authorized Android, product and release owners control every real action.
$12 Target API Deadline Evidence Pack
Export an editable portfolio matrix for up to 100 sanitized records: form-factor requirements, target gaps, behavior-test and extension queue, availability risk, version sign-off and usage and outcome review ledger.
- up to 100 sanitized App/form-factor records
- new, update and existing-availability deadline matrix
- mobile, Wear, TV, Automotive and XR responsibility
- behavior-change test and extension queue
- source-date, version and human sign-off
- use, purchase and outcome review ledger
Current 2026 requirements and strong native substitutes
先核对当前来源与工具边界Check current sources and tool limits first