How to deploy custom intents on Android devices?

Deploying custom intents via Hexnode UEM allows IT administrators to remotely initiate targeted actions, such as launching an activity or starting a service, on managed Android devices by sending structured messages to the system or specific applications.

What is an Intent on Android?

An Intent is a fundamental, structured messaging object in Android used to communicate between components like Activities, Services, and Broadcast Receivers, facilitating task flow and component communication, such as shifting from a camera app to a web browser.

• Function: Intents act as structured messages that instruct the Android system or a specific application component on the necessary action to take.
• Common Uses:
  • Opening a new user interface (Activity).
  • Starting a background task (Service).
  • Sending system-wide or app-specific notifications (Broadcasts).

Hexnode’s Deploy Intent: Primary Use

Hexnode’s Deploy Intent remote action enables IT administrators to send custom intents to managed Android devices, allowing for the remote execution of targeted actions, implicitly or explicitly, without user intervention at the device level.

Prerequisites for Deploying Custom Intents

• The target application must be installed on the Android device for the intent to execute successfully.
• The Hexnode UEM app on the device should be the latest version.

Step-by-Step Guide: Deploying custom intents from Hexnode

To deploy custom intents to an Android device using the Hexnode UEM console:

1. Log in to the Hexnode UEM console.
2. Navigate to Manage > Devices.
3. Select the Android device to which the custom intent will be deployed.
4. On the Device Details page, click Actions > Deployments > Deploy Intent.

Configuring the Intent options

The Deploy Intent action requires configuring several parameters based on the desired action.

1. Intent Type Selection

   The Intent type determines how the Android system resolves and handles the action.

   Intent Type	Targeting Mechanism	Outcome/User Interaction	Primary Use Case
   Implicit	Targets any app component capable of handling the requested action.	User is prompted to choose if multiple apps are suitable, unless a default is set.	General actions where the handler is not known or needs flexibility (e.g., viewing a web link).
   Explicit	Targets a specific app component using its Class name.	Direct execution on the specified component; no user choice is involved.	High-certainty actions where a specific app and component must execute the task (e.g., launching a configuration screen).

2. Required Parameters

   Parameter	Function	Example Value	Intent Type Applicability
   Action	Specifies the operation the intent performs.	android.intent.action.VIEW	Both Implicit and Explicit
   Class	The exact class name within the application to target.	com.example.app.TargetActivity	Only Explicit

3. Optional Parameters

   Parameter	Function	Example Value
   Data URI	The data associated with the intent.	https://www.hexnode.com/
   Data type	The general format or category of the data.	text/plain or image/jpeg
   Category	Provides additional context about the component.	CATEGORY_LAUNCHER
   Configure extras	Key-value pairs to pass additional data.	Key: username, Value: admin

4. Execution

   1. Configure all required fields.
   2. Click Execute.
   Note:

   
   If Explicit is selected, first click Select App to choose the target application before clicking Execute.
   

Device-End behavior and Troubleshooting

Example: Device action with Implicit Intent

• Configuration: Implicit Intent, Action set to android.intent.action.VIEW, and Data URI set to https://www.hexnode.com/.
• Result: The webpage https://www.hexnode.com/ opens on the device using the user’s default web browser, as no specific app was targeted.

Troubleshooting Failed “Deploy Intent” action

If the custom intent action appears as Failed in Action History, check for these common causes:

• The Hexnode UEM app on the device is an outdated version.
• An incorrect intent string was specified.
• The target app is not installed on the device.
• The application selected for an Explicit intent does not contain the required application component.

Frequently Asked Questions (FAQs)

1. Can custom intents be deployed to uninstalled applications?

   No, the deployment of Android custom intent fails if the target application is not currently installed on the device.

2. Will custom intent deployment work if multiple apps can handle the same action?

   Yes, but with an Implicit intent, the end-user may be prompted to select their preferred app if no default handler is configured. To ensure smooth, zero-touch deployment, use an Explicit intent to directly target a specific app and component.