Send a revision
Push your tested project, then submit the revision ID returned by the CLI:app_submit_for_review tool.
Follow its progress
What reviewers look for
- The app renders reliably and stays within runtime limits.
- Its name, summary, description, and settings match what it does.
- External data has sensible refresh rates and useful failure states.
- Credentials and personal data use protected fields.
- Images, fonts, code, data, and brand assets have the required rights and attribution.
- Text and animation remain clear and safe on a physical display.
For an app’s first publication, approval does not publish it publicly. An explicit audited owner
publication is required after the applicable catalog, provider, security, and
release checks.
Check your app before submitting
Run the final behavior, privacy, reliability, and rights checks.
Updates after publication
Automatic update review is available in the hosted service. Use CLI v0.54.10 or later.
apps push submits its exact revision
for review. The approved version keeps running until approval. Approval makes
the new release available and updates compatible installed copies. Rejection
leaves the current release unchanged. Only one active review per project is
allowed; finish it before pushing another update.
Reviewers can test declared HTTPS requests in the isolated playground. Protected
account and provider credentials remain unavailable there, so credential-dependent
behavior needs separate review evidence. Network access itself does not require
public review for owner-private apps.