App ComposerLoftwah’s instance

Save the stack, not just the settings.

A stack is a named, saved composition of reviewed mini-apps. Add an app, give it a label and a caption, reorder it, save it as a draft, preview it and publish one shareable page. The apps keep their own records, media and source.

Open creator stacksBrowse the app library

The workspace is behind the same invited administrator sign-in as mini-app management. There is no public signup, and a visitor cannot reach a draft.

The whole loop.

  1. Discover. The library shows each app's purpose, real screen and source.
  2. Add and configure. A stack holds up to twelve instances with their own labels, captions and order.
  3. Save and reopen. Drafts are revision-guarded: a save from a stale tab is refused instead of overwriting newer work.
  4. Preview. The preview renders the draft in the admin. It never publishes and never leaks a private record.
  5. Publish and share. Publishing stores a revision and gives the stack a public address. Later edits stay private until you publish again.
  6. Return and edit. Reopen the stack, change it, unpublish, duplicate or archive it.

What the first slice does.

  • One personal workspace per invited creator, with owner, editor and viewer capabilities checked on every request.
  • Two or more named stacks with independent drafts, immutable published revisions and share addresses.
  • Instances configured on their own from the settings each app declares, or reusing an existing instance so one set of records stays authoritative.
  • Publish, unpublish, archive, restore, duplicate, roll a publication back, export and delete with distinct semantics.
  • An export that contains configuration only — no app records, media or credentials.
  • A share card and a QR code drawn from the published revision you are looking at.

Still open, and labelled as such: inviting other creators, custom domains for a stack, scheduled publishing and private creator analytics. The creator dashboard epic owns those.

See it working.

Open two fictional stacks created, saved and published through the creator studio. Trail Notes has its own visitor book and an intentional second view of that same book. Launch Board uses a separate book, with separate settings and records. Each published page includes its share card and QR download.

See the connected pair · Read what is verified · Follow the stack work