macOS App
Package an existing web deployment as a downloadable macOS desktop build.
macOS App packages an SPA, PWA, MPA or Embed deployment that already exists into a downloadable macOS build: the screens ship inside the app, but every data and login call still goes to that web deployment. If the project has no active web deployment yet, the Configuration step says so and asks for one first.
Create a macOS App deployment
Open the project and click Deploy
Open the project, click Deploy, then select macOS App from the Native apps group.
Configuration
Fill in:
- Serving deployment, the existing SPA, PWA, MPA or Embed deployment this app calls for data and login. Preselected automatically when the project has exactly one; you choose when it has more than one.
- Bundle Id, reverse-DNS (
com.example.myapp). Not required for macOS, but it cannot be renamed after the first release if you set one. - Build type: Development, which installs locally and needs no Apple account, or Ad hoc.
Finalize Details
Name the deployment and check the price in the footer, then click Create macOS App.
There is no Datacenter or Performance Tier step: nothing is hosted for a macOS App, it is a build artifact.
Once it exists
The deployment carries a Publish tab alongside the usual Overview, Usage, Logs and Advanced, for the built app and its download link.
Pricing
macOS App carries a flat $45/mo. There is no separate server or datacenter cost.