iOS App
Package an existing web deployment as a Simulator or App Store build for iPhone and iPad.
iOS App packages an SPA, PWA, MPA or Embed deployment that already exists into an iOS 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 an iOS App deployment
Open the project and click Deploy
Open the project, click Deploy, then select iOS 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, required, reverse-DNS (
com.example.myapp). It cannot be renamed after the first release, and it must be unique, no other project's iOS deployment can already use it. - Build type: Development (Simulator), which needs no Apple account, or App Store (signed), which needs your Apple credentials.
- If App Store (signed): Apple Team ID (the ten-character ID from your Apple Developer account) and Signing credentials (the name of the environment group holding your App Store Connect key), both required.
Finalize Details
Name the deployment and check the price in the footer, then click Create iOS App.
There is no Datacenter or Performance Tier step: nothing is hosted for an iOS 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 IPA and its publishing status.
Pricing
iOS App carries a flat $45/mo. There is no separate server or datacenter cost.