Publish my App

In the design, publishing releases your App on your own Domain, and every Customer runs the newest build. The last build stays, so one call puts it back.

What you getCopy Anchor Link

In the design, one App.publish puts every set of screens on leaseclock.com live at once, over the one API.

A Customer sees leaseclock.com and its Brand on every screen, and never the platform's name.

Your agent doesCopy Anchor Link

In the design, your agent finds the App, shows you the change, and calls App.publish once you say yes.

Publish my app.
Put the new lease screens live.
Ship the app to every customer.

{
  "api": "https://api.sb/leaseclock.com",
  "app": {
    "$id": "https://api.sb/leaseclock.com/apps/app_1",
    "$type": "App",
    "kind": "app"
  },
  "action": {
    "$id": "https://api.sb/leaseclock.com/actions/action_7",
    "operation": "App.publish",
    "status": "done"
  },
  "links": {
    "self": "https://api.sb/leaseclock.com/actions/action_7"
  }
}

1. Your agent reads the App with Interface.list.
2. It shows you each screen that changed since the last build, such as a new deposit field on the Lease forms.
3. Once you approve, it calls App.publish, and the Action waits out its delay window.
4. The new build serves at leaseclock.com/app, and each Customer's Tenant runs it on its next request.
5. The previous Version stays, and App.published fires.

A call without the scope to publish ends forbidden. A call on an App in a state that cannot publish ends refused, and the Action says why.

Change itCopy Anchor Link

Under the hoodCopy Anchor Link