Skip to main content
Use this checklist after the app works locally and before you send a revision for review.

App and preview

  • manifest.yaml has a stable lowercase app handle and accurately describes the app.
  • The project has exactly one top-level .star file.
  • niblet apps validate . passes.
  • niblet apps preview . -o preview.webp produces the result you intend to submit.

Experience and reliability

  • The app is easy to read at its actual display size.
  • Animations loop cleanly and avoid unsafe flashing.
  • Every setting has a useful default or handles a missing value.
  • Network and provider failures show a clear fallback.
  • You checked the result on a physical display when color, brightness, or motion matters.

Security and privacy

  • Source, metadata, and review notes contain no credentials or personal data.
  • Secrets use credential fields or OAuth connections.
  • Logs exclude tokens, locations, full responses, and user-entered content.
  • HTTP requests contact only required hosts and use a sensible cache lifetime.

Content and support

  • You have permission to distribute every image, font, logo, character, and dependency.
  • External service terms allow your intended use, display, and request volume.
  • Required attribution is included and accurate.
  • People have a way to get support when the app or its data source changes.

Submit the checked revision

If you changed anything during this check, render and push a new revision. Submit only the revision ID that matches the preview you inspected.

Submit your app for review

Upload the tested revision and follow it through review.
Last modified on September 2, 2026