Contract-freeze · UX approval

Federated App Platform — Approval Frames

Click through the four frames below as a sequence. They demonstrate the UX the App Manifest contract produces. Approving these frames approves the model (the manifest schema + lifecycle) before any UI is implemented. Built in the fuse-seam design-system tokens.

Frame (a)

🕐 Application menu

The app menu + launcher with the built-in Clock app and a newly-registered Market app.

capability 1 + 4 · registration / built-in
Frame (b)

+ Register → Activate

The Add-application form (manifest fields) → registered → activate → visible.

capability 1 · lifecycle
Frame (c)

🎛️ Menu substitution

A federated app (Studio) that has substituted the portal side menu with its own.

capability 2 · chrome.menu = substitute
Frame (d)

🌐 Standalone app

A standalone non-portal landing page — FuzeFront infra, no portal chrome.

capability 3 · mode = standalone
Start the walkthrough →

Contract: services/app-registry-service/openapi.yaml · Manifest schema: components.schemas.AppManifest · Client: @fuzefront/app-registry-client · Events: shared/src/kafka/schemas/app.* · Design write-up: DESIGN.md

No flows declared in manifest.build.flows — nothing to approve.