Specify what runs when your Progressive Web App deployment is accessed.

The Launch Settings step defines what happens when the Progressive Web App (PWA) deployment is accessed. Administrators can select a specific build version, choose between launching a single program or routing through multiple ones, and configure secure global variables that remain server-side. These settings ensure consistent execution behavior, controlled access to system resources, and a smooth user experience across environments.

Build & Launch Setup

Define the runtime build and control how the app starts when accessed by users.

Build Selection

Select the runtime build (e.g., Build Version 10) to ensure consistent release behavior.

Launch Method

Choose whether to start a single program or configure a router for multi-program handling.

Program Binding

Assign a program, such as 'dashboard', to execute when the PWA deployment is launched.

Program Parameters

Optionally define parameters to modify the program’s runtime behavior.

Global Variables

Define secure, server-side parameters that are inaccessible to the client for enhanced security.

Secure Server Variables

Store environment-specific data such as tokens, API keys, or flags securely.

Hidden from Client

Ensure critical configuration data remains protected and cannot be manipulated from the frontend.

FAQs

It defines how your PWA behaves when accessed, including which build version runs and how the app routes between programs.

Yes. Administrators can select a specific build version to ensure consistent performance and controlled version management.

Global variables store secure configuration values that remain server-side, providing dynamic functionality without exposing sensitive data.

Yes. You can configure the PWA to route through multiple programs, enabling modular app behavior within a single deployment.

By storing sensitive variables on the server and defining explicit access routes, Launch Settings prevent unauthorized data exposure.

Yes. You can update launch behavior, variable configurations, or program routes at any time and redeploy for immediate effect.

A single-program launch runs one main process, while multi-program routing lets you connect several modules under one deployment.

Defining environment variables at launch centralizes control, prevents client-side exposure, and supports consistent configuration management.

Yes. Launch Settings allow targeted builds and controlled routing, reducing overhead and improving load times across environments.

It ensures your PWA executes consistently, securely, and efficiently across devices by defining what happens at access time.

Develop. Deploy. Stay Productive.

Xuda is the platform for frontend developers, providing the speed and reliability innovators need to create at the moment of inspiration.

Schedule a demo