Forge App Quality Standard · v1.0

Native by design. Safe by default.

Every marketplace app must feel like part of one Growth OS. These rules are release requirements, not suggestions.

Interface

  • Use Space Grotesk and the published design tokens.
  • Use the blue-to-cyan action gradient only for primary actions.
  • Keep one clear primary action per surface.
  • Support 320px mobile through wide desktop without horizontal page scroll.
  • Minimum 44px touch targets, visible keyboard focus, semantic labels and WCAG AA contrast.
  • Ship real empty, loading, success, error and disabled states.

Integration

  • Use Forge SDK 1.x from a server process.
  • Request only scopes used by the customer-facing workflow.
  • Handle 429 with bounded exponential backoff and jitter.
  • Make writes idempotent and persist webhook event IDs.
  • Never ask a customer for Forge or provider secrets.
  • Revoke access and stop processing immediately after uninstall.

Security

  • No external executable JavaScript inside the Forge portal.
  • No hardcoded secrets, tokens, private keys or customer identifiers.
  • Verify webhook timestamp and HMAC before parsing the payload.
  • Use HTTPS, strict input bounds and deny-by-default authorization.
  • Publish support and privacy contacts and maintain a vulnerability channel.
  • Do not track, resell or repurpose customer data.

Release evidence

  • OpenAPI, SDK types and examples change together.
  • Test install, configure, upgrade, uninstall and revoked-access behavior.
  • Test permission denial, retry, timeout and provider outage paths.
  • Provide three accurate product screenshots without fabricated results.
  • Pass server auto-review at 90+, plus Forge runtime and security checks.
  • Monitor errors and provide a rollback-safe release.

Official UI foundation

Download the versioned JSON tokens or CSS custom properties. Apps may extend this system for their product needs, but must preserve typography, hierarchy, control states and accessibility.