For the complete documentation index, see llms.txt. This page is also available as Markdown.

Custom Intents

This Launcher feature invokes Android Intents during certain device or user actions.

The BlueFletch Launcher's Custom Intent capability is a means of triggering actions that will repeat when a certain device state is true. Custom Intents eases the efforts of administrators and users alike by automating app activities to occur at a predictable time, such as login, logout, boot, or cradle. Launcher can invoke Android intents to do anything from opening a particular app each time a certain user group logs in, to muting the audio ten seconds after a device is cradled.

Device Events

Custom Intents can be invoked on these device events/state changes:

  • Pre Login

  • Login

  • Logout

  • Post Logout

  • Boot

  • Device Uncradled

  • Device Cradled

  • Device Screen On

  • Device Screen Off

  • Motion Lock Enter

  • Motion Lock Exit

  • Site Changed

Custom Intent Contents

When a device event occurs, its array of intents can be made up of:

  • Standard Android Intents - Intents directly provided by Android, such as starting an application or sending a broadcast.

  • Platform Actions - Intents customized by BlueFletch to build off of Android's standard intents.

  • Replacement Variables - Custom Intents support replacement variables so the intent can dynamically respond to data from the device.

  • Filters - Custom Intents can be filtered to only run in a subset of scenarios, based on criteria.

For configuration details and examples, consult the Technical Guide for this feature.

Last updated