SOURCE-CHECKED 19 AUGUST 2026 · OFFLINE WEB APP
One deadline.
Every package accounted for.
Coordinate developer identity, package-name registration, distribution paths, rollout markets, owners, and evidence references across a multi-app Android portfolio.
PORTFOLIO CONTROL4 apps · 3 need action
30 SEP 2026Fictional Field Notes
com.example.fieldnotesREADYFictional Warehouse Scan
io.example.warehouseIDENTITYFictional Managed Kiosk
org.example.kioskSCOPEProtections start in the first four announced markets.
Brazil, Indonesia, Singapore, and Thailand.
Verify the developer and register package names.
WHY THIS WORKSPACE
The official console handles one record. Your team still needs the portfolio.
- Play and outside-Play distribution can require different paths
- Identity completion does not by itself prove every package is registered
- Existing package names may surface different signing-key scenarios
- Owners and evidence can be scattered across release teams and clients
7 ACTION STATES · 4 EXPORT PATHS
Built around the work between inventories and consoles.
The ZIP includes the offline HTML app, source logic, deterministic tests, fictional sample data, quick start, official source notes, change log, sales copy, and one-organisation internal-use licence.
Multi-app inventory
Track package names, Play and outside-Play paths, initial markets, owners, and target dates.
Two-gate readiness
Keep developer identity and package-name registration separate instead of treating one as proof of the other.
Key-scenario queue
Record an operator-confirmed majority, 50-plus, under-50, new-package, or unknown scenario without deciding eligibility.
Honest action states
Separate ready, identity action, manual registration, package request, console check, scope review, and inventory gap.
Portable review packet
Export JSON and CSV, copy a decision summary, or print a portfolio packet from the local browser.
Source and privacy controls
Use fictional samples, official links, explicit product boundaries, tests, and evidence references instead of secrets.
NON-NEGOTIABLE BOUNDARY
A portfolio desk is not the official verification system.
No identity verification, D-U-N-S or website verification, package registration, key eligibility decision, APK signing or upload, exception determination, policy advice, or installability guarantee.
FAQ
Keep the official boundary visible.
Does the kit verify a developer identity?
No. Identity verification happens only in the applicable official console and may require personal or organisation evidence.
Does it register a package name or prove key ownership?
No. It does not sign or upload an APK, handle certificates or private keys, create a package claim, or send a package-name request.
Does it decide which key is eligible?
No. The operator records the scenario visible in approved evidence, and the official console determines the available path.
Are managed enterprise apps automatically exempt?
The workspace deliberately marks that path for an official scope check. Confirm the organisation-store and managed-device conditions in current guidance.
What does the licence cover?
One legal organisation may use and modify the files for its own internal portfolio and client work. Resale, redistribution, and competing products are not allowed.
LAUNCH EDITION
Bring the next release review onto one screen.
Offline app, source, tests, fictional portfolio, JSON and CSV portability, print packet, source notes, quick start, and internal-use licence.