Scheduled app auto-launch not supported: use Esper API or on-device alarm workaround for time-based kiosk app opening

Android

Esper doesn't offer native scheduled app launching on managed Android kiosk devices. This article explains why and provides three workarounds to automatically open an app at a specific time each day.

Understand the limitation

Esper's Apps & Configuration supports remote app launches, but these are manual, on-demand actions only. There's no built-in time-based scheduler (cron-style) to launch an app automatically at a set time every day. This is a platform-level feature gap, not a misconfiguration or bug.

The Remote Launch feature lets you launch an app manually from the Esper Console, but you cannot schedule it to repeat daily or at specific times.

Option 1: Use an on-device automation app (recommended for kiosk deployments)

Install an Android automation app on your devices that can schedule app launches. This approach keeps scheduling logic on the device itself.

1. Push an automation app (such as MacroDroid or Tasker) to your device group via Apps & Configuration → Add Apps.
2. Configure the automation app to launch your target app (for example, DreamMapper) at your required time on a daily recurring schedule.
3. In your Blueprint, navigate to Blueprints → [Blueprint Name] → Kiosk / Launcher Settings and ensure the automation app has permission to launch other apps and isn't blocked by kiosk mode restrictions.
4. Apply the updated Blueprint to your device group by going to Blueprints → [Blueprint Name] → Apply → Select Group/Devices → Confirm.
5. Verify the scheduled trigger fires correctly on your device at the set time the following day.

Option 2: Use the Esper API with an external scheduler

Call the Esper API on a schedule using an external cron service to trigger app launches at your desired time.

1. Retrieve your target app's package name from Devices & Groups → [Device] → Apps.
2. Set up an external scheduler (such as AWS Lambda + EventBridge, Azure Logic Apps, or a customer-managed cron server) to call the Esper Device API endpoint POST /v0/enterprise/{enterprise_id}/devices/{device_id}/commands/ with the command type LAUNCH_APP and your target package name.
3. Configure the external scheduler to fire at your desired time. Important: Account for time zone differences. For example, to launch at 7:00 AM SGT (UTC+8), schedule the API call for 23:00 UTC the previous day.
4. Authenticate the API call using your Esper API key from API Key Management in the Esper Console.
5. Verify that the API call returns HTTP 200 and your app appears in the foreground at the scheduled time.

Option 3: Manual remote launch (temporary workaround only)

Use manual app launching as a short-term solution while you implement one of the options above.

1. Navigate to Devices & Groups → [Device Name] → Apps.
2. Locate your app and select Launch.
3. Repeat this action each time you need to launch the app — this is not automated.

Troubleshooting

The automation app is blocked by kiosk mode:

If your automation app cannot launch other apps, check your Blueprint's kiosk and app permission settings. Navigate to Blueprints → [Blueprint Name] → App Permissions / Kiosk Settings and verify that your automation app is not restricted by an allow list.

The API call fails:

Confirm you're using the exact package name for your target app. Check Devices & Groups → [Device] → Apps to verify the package name is correct.

Time zone misalignment:

If using the API workaround, verify that your external scheduler and your device are set to the correct time zone. Device time zone can be configured in your Blueprint settings.

Still need help?

If none of these workarounds fit your use case or you'd like to request this as a native Esper feature, contact Esper Support.