Waitwhile Launcher MDM Configuration

The Waitwhile Launcher is an Android kiosk application designed to display Waitwhile guest registration flows on tablets in commercial environments. This guide explains how to deploy and configure the app using Mobile Device Management (MDM) platforms.

Key features include:

Full-screen WebView display of Waitwhile locations
Kiosk mode support for locked-down deployments
Flexible location ID configuration
Debug mode for troubleshooting
Automatic configuration updates without app restart

MDM Configuration Parameters

The app supports the following managed configuration parameters:

Required Configuration

`locationId` (String)

Description: The Waitwhile location identifier or short name
Required: Yes
Example: "store123", "nyc-flagship", "clinic-west"
Note: This is the primary configuration that determines which Waitwhile location to display

Optional Configurations

`environment` (Choice)

Description: Selects the Waitwhile environment
Options:
- "production" (default) - Uses https://waitwhile.com
- "development" - Uses https://ww-static-public-dev.web.app
Default: "production"

`kioskMode` (Boolean)

Description: Enables kiosk mode interface
Default: true

`locale` (String)

Description: Sets the language/locale for the interface
Examples: "en-US", "es-ES", "fr-FR", "de-DE"
Default: Device locale

`debug` (Boolean)

Description: Enables debug overlay with device and configuration information
Default: false
Use Case: Troubleshooting deployment issues

Location ID Processing

These parameters allow dynamic transformation of location IDs:

`locationIdStripPrefix` (String)

Description: Removes specified prefix from the location ID
Example: If locationId is "PROD-store123" and stripPrefix is "PROD-", result is "store123"

`locationIdStripSuffix` (String)

Description: Removes specified suffix from the location ID
Example: If locationId is "store123-OLD" and stripSuffix is "-OLD", result is "store123"

`locationIdPrefix` (String)

Description: Adds prefix to the processed location ID
Example: Adding "US-" prefix to "store123" results in "US-store123"

`locationIdSuffix` (String)

Description: Adds suffix to the processed location ID
Example: Adding "-KIOSK" suffix to "store123" results in "store123-KIOSK"

Deployment Examples

App Installation

The Waitwhile Launcher is available on the Google Play Store. You can deploy it through:

Managed Google Play (recommended for enterprise deployments)
Direct APK/AAB upload to your MDM platform
Public Google Play Store for testing

Microsoft Intune

Add the app to Intune:
- Search for "Waitwhile Launcher" in Managed Google Play
- Or add via Google Play Store URL: https://play.google.com/store/apps/details?id=com.waitwhile.launcher
- Alternatively, upload the APK/AAB directly

Configure app settings:

{
  "kind": "androidenterprise#managedConfiguration",
  "productId": "com.waitwhile.launcher",
  "managedProperty": [
    {
      "key": "locationId",
      "valueString": "store123"
    },
    {
      "key": "environment",
      "valueString": "production"
    },
    {
      "key": "kioskMode",
      "valueBool": true
    },
    {
      "key": "locale",
      "valueString": "en-US"
    }
  ]
}

VMware Workspace ONE

Add the app from Google Play Store or upload to Workspace ONE console
Create an assignment with Application Configuration:
- Key: locationId, Value: "store123"
- Key: environment, Value: "production"
- Key: kioskMode, Value: true
- Key: locale, Value: "en-US"

Google Workspace (Android Enterprise)

Add app from managed Google Play
- Search for "Waitwhile Launcher" or use app ID: com.waitwhile.launcher
Configure managed configuration:
- Navigate to Devices > Mobile & endpoints > Apps > Manage apps
- Select the Waitwhile Launcher app
- Configure settings:
```
locationId: store123
environment: production
kioskMode: true
locale: en-US
```

MobileIron

Add Android Enterprise app
- Import from Google Play using app ID: com.waitwhile.launcher
- Or upload APK/AAB directly

Configure App Configuration:

<managedAppConfiguration>
  <bundleId>com.waitwhile.launcher</bundleId>
  <configuration>
    <string keyName="locationId">
      <defaultValue>store123</defaultValue>
    </string>
    <choice keyName="environment">
      <defaultValue>production</defaultValue>
    </choice>
    <boolean keyName="kioskMode">
      <defaultValue>true</defaultValue>
    </boolean>
  </configuration>
</managedAppConfiguration>

Use Case Examples

Multi-Store Retail Chain

For a retail chain with stores using IDs like "RETAIL-NYC-001", "RETAIL-LA-002":

{
  "locationId": "RETAIL-NYC-001",
  "locationIdStripPrefix": "RETAIL-",
  "locationIdPrefix": "US-",
  "environment": "production",
  "kioskMode": true,
  "locale": "en-US"
}

Result: Displays https://waitwhile.com/locations/US-NYC-001?kiosk=true

Healthcare Clinics

For clinics transitioning from old to new location IDs:

{
  "locationId": "clinic-west-old",
  "locationIdStripSuffix": "-old",
  "locationIdSuffix": "-kiosk",
  "environment": "production",
  "kioskMode": true,
  "locale": "es-ES"
}

Result: Displays https://waitwhile.com/locations/clinic-west-kiosk?kiosk=true&locale=es-ES

Development Testing

For testing new features before production:

{
  "locationId": "test-location",
  "environment": "development",
  "kioskMode": true,
  "debug": true
}

Result: Displays https://ww-static-public-dev.web.app/locations/test-location?kiosk=true with debug overlay

Kiosk Mode Setup

Android Lock Task Mode

Set device owner via ADB or MDM enrollment
Configure lock task packages to include com.waitwhile.launcher
Set as home app for dedicated devices
Configure allowed features:
- Disable status bar
- Disable navigation buttons
- Prevent app switching

Single App Mode (Samsung Knox)

{
  "packageName": "com.waitwhile.launcher",
  "mode": "SINGLE_APP",
  "allowedApps": ["com.waitwhile.launcher"]
}

Troubleshooting

Debug Mode

Enable debug mode to see:

Current configuration values
Location ID processing steps
Network connectivity status
Device information
App version

{
  "debug": true
}

Common Issues

"Location ID not configured" error
- Ensure locationId is set in MDM configuration
- Verify MDM policies are applied to device
- Check debug mode for configuration values
Wrong location displayed
- Verify location ID transformations
- Check prefix/suffix stripping and addition
- Enable debug mode to see final URL
Language not changing
- Confirm locale parameter format (e.g., "en-US")
- Verify Waitwhile location supports the locale
Configuration not updating
- Force sync MDM policies
- The app listens for configuration changes automatically
- No app restart required for updates

Testing Configuration

Deploy to test device with debug enabled
Verify configuration in debug overlay
Test location ID transformations
Confirm correct URL generation
Disable debug for production deployment

Security Considerations

The app only allows navigation to *.waitwhile.com and *.web.app domains
WebView file access is disabled
JavaScript is required and enabled
DOM storage is enabled for app functionality
No local data is stored permanently

Support

For technical issues with:

App deployment: Contact your MDM vendor support
Waitwhile functionality: Contact Waitwhile support
App bugs: Report to the app development team

Version Information

Check app version in debug mode or through MDM app inventory reporting.