Skip to content
Draft

Windows App

Package an existing web deployment as a Windows desktop build.

Windows App packages an SPA, PWA, MPA or Embed deployment that already exists into a Windows desktop build: the screens ship inside the app, but every data and login call still goes to that web deployment. Unlike iOS, Android and macOS, there is no dashboard Configuration screen for Windows App yet, so the wizard has nothing to fill in beyond which build to package: the serving deployment is inferred automatically when the project has exactly one active web deployment.

Create a Windows App deployment

Open the project and click Deploy

Open the project, click Deploy, then select Windows App from the Native apps group.

Launch Settings

The wizard still shows a Launch Settings step here, asking you to pick a page or component, the same picker SPA and Embed use. The Windows build does not use that pick, only the serving deployment it infers matters.

Finalize Details

Name the deployment and check the price in the footer, then click Create Windows App.

There is no Datacenter or Performance Tier step: nothing is hosted for a Windows 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 installer.

Pricing

Windows App carries a flat $45/mo. There is no separate server or datacenter cost.