TIMESDevelopers
v1.0.0

Review guidelines

What reviewers check before an AIP goes live.

Most reviews finish within two business days. You can track progress with times aip status or on the AIP detail page.

Reviewers check

  1. Manifest: valid schema, correct kind, semver bump, a changelog entry for the version.
  2. Scopes: every requested scope is used. No :admin scopes without a clear reason in the submission notes.
  3. i18n: all four catalogs exist and contain real translations.
  4. Theme: the UI uses TIMES tokens and works in light and dark mode.
  5. Behavior: no crashes, no blank screens, ready() is called, errors are shown to the user.
  6. Privacy: no tracking scripts, no data sent to hosts the listing does not disclose.
  7. Listing: accurate description, screenshots from the real AIP, support contact.

Common reasons for changes requested

  • English text pasted into am, om or ti.
  • Hard coded colors that break dark mode.
  • Requesting invoices:write when the AIP only reads invoices.
  • Missing privacy policy URL for integrations that send data outside TIMES.

After approval

The bundle is copied to the CDN and the version becomes published. Installed merchants move to the new version on their next load unless the new version asks for more scopes. In that case they are prompted to approve.