Google says Play packages must be registered by this date to meet the verification requirement.
FREE SPREADSHEET · FICTIONAL ROWS · SOURCE-CHECKED 29 AUG 2026
Start with a spreadsheet.
Know when to outgrow it.
Inventory Android developer identity and Play package-name registration without mixing the two tasks—or putting credentials and proof material into a shared file.
A verified developer account does not by itself prove that every package name is registered.
Track decisions and owners here. Keep keys, identity evidence, and proof files in approved systems.
SPREADSHEET OR LOCAL APP?
Use the smallest tool that keeps the queue reviewable.
The free CSV is enough to find gaps and assign owners. The paid local kit is for portfolios that need repeatable filters, deterministic checks, exports, and a print-ready review packet.
One app or a first inventory
Free CSV: List the package name, separate identity and registration states, assign an owner, and record the next review date.
Several apps with different owners
Portfolio kit: Keep a deterministic queue, filtered views, evidence references, exports, and a printable review packet in one local browser workspace.
Identity or package action in progress
Official console: Complete verification, package registration, key selection, and proof steps only in the applicable Google console.
SAFE WORKING FIELDS
Record the decision trail.
Not the proof material.
These fields let a release or portfolio manager assign work without turning a spreadsheet into a second identity or signing system.
PRIMARY SOURCES
Confirm every status in the official console.
WHEN THE SPREADSHEET STOPS BEING ENOUGH
Move the same portfolio into a local review workspace.
The Android Verification Portfolio Kit adds owner queues, deterministic readiness checks, JSON and CSV exports, print output, source notes, and an internal-use licence. It does not submit anything to Google.