Overview

2026-11-04Loading rating…

DJI Pilot Plugin

DJI Pilot Plugin extends MSDK into the DJI Pilot operating environment. Developers can package enterprise tasks, data, and workflows as an Android plugin, install it on a remote controller with a screen, and run it alongside Pilot.

Pilot handles foundational operations such as flight, video, and maps, while the plugin handles industry-specific logic. Through MSDK, the plugin reuses Pilot's hardware and open capabilities and provides business interactions within the plugin floating window and the scope of Pilot's open UI capabilities.

DJI Pilot Plugin capability panorama

Why Use DJI Pilot Plugin?

When developing a standalone app with traditional MSDK, teams usually need to build foundational capabilities such as device connectivity, video display, map rendering, flight interaction, and operational UI.

For teams with mature industry systems that are extending their workflows to drone operations for the first time, this means not only integrating their own tasks, data, and processes, but also building the foundation of a flight app. That leads to longer development cycles and higher ongoing maintenance costs.

DJI Pilot Plugin does more than reduce duplicate development. It lets industry applications directly use professional capabilities already available in Pilot:

  • Video and AR: Display targets, defects, risk areas, and operational guidance over the camera view.
  • Map capabilities: Show task points, inspection routes, restricted areas, and industry geospatial data.
  • Local modeling: Monitor modeling status, obtain modeling results, and integrate them into enterprise result-management workflows.
  • Business interaction: Use the plugin floating window, custom components, dialogs, and page navigation for task confirmation, information entry, and workflow guidance.

Teams can therefore focus development on industry tasks, data, and workflows instead of rebuilding a complete flight application.

Note: DJI Pilot Plugin is suitable for adding industry capabilities to existing Pilot workflows. If the entire product experience and interaction model of the flight app must be customized, a standalone MSDK application remains the better choice.

What Does It Bring to Industry Operations?

DJI Pilot Plugin extends existing industry systems to the remote controller, helping operators access task information and complete required confirmation, recording, and response actions during flight operations.

Operational stageHow it helpsExample capabilities
Before operationPresent task areas, target locations, operating rules, and resource readinessMap widgets, plugin floating window, custom UI components
During operationHighlight targets, risk areas, and response steps in open map or camera-view areasAR projection, camera-view drawing, map widgets, dialogs
After operationExport results, confirm outcomes, and connect them with business systemsFile transfer, local modeling, native MSDK capabilities
Industry scenarioHow DJI Pilot Plugin can help
Power-line and wind-turbine inspectionMark towers, equipment, and defects; display inspection routes and task points
Public safety, firefighting, and emergency responseDisplay target locations, restricted zones, and on-site response guidance
Surveying and modelingPresent operating areas, monitor modeling status, and obtain modeling results
Security and site patrolDisplay patrol tasks, incident locations, and response rules
Construction and miningDisplay site elements, area boundaries, and operational data

Available Capabilities

Capability categoryIncluded capabilitiesPurpose
Pilot open UI capabilitiesPlugin floating window, custom UI components, map widgets, AR projection, camera-view drawing, dialogs, and page navigationPresent business information and handle interactions within Pilot's open scope
Pilot platform capabilitiesPlugin connection status, service configuration, Pilot actions, local modeling, and file transferSupport runtime collaboration between the plugin and Pilot
Native MSDK capabilitiesKey operations, wayline missions, video streams, and moreAccess aircraft capabilities through Pilot

For the complete capability list, interface descriptions, and examples, see the Capability Map.

How Does It Differ from a Standalone MSDK App?

ComparisonStandalone MSDK appDJI Pilot Plugin
Application modelA standalone flight applicationAn industry plugin that runs alongside Pilot
Flight and operational foundationBuilt or integrated by the developerReuses Pilot's open flight, video, map, AR, and modeling capabilities
Development focusBuild both flight and industry capabilitiesFocus on industry tasks, data, and workflows
Relationship with PilotConnects and runs independentlyAccesses hardware through Pilot and provides business interaction through the plugin floating window and within Pilot's open UI capabilities
Best suited forA fully customized flight applicationExtending industry capabilities within Pilot workflows

How Do Pilot and the Plugin Work Together?

The plugin is an independent Android application installed on a remote controller with a screen. It runs in a separate process from Pilot and collaborates with Pilot through MSDK's inter-process mechanism.

ComponentResponsibility
Plugin processRuns industry logic, including task processing, data integration, and business workflows
Pilot processMaintains the aircraft connection and provides flight, video, map, and other operational capabilities
MSDKHandles communication between the plugin and Pilot, hiding inter-process details from developers

When MSDK is initialized with SDKLinkMode.REMOTE_PILOT, the application runs in Pilot plugin mode. Except for the link mode and the additional Pilot open capabilities, MSDK Keys, callbacks, error codes, and registration follow the same development model as a standalone MSDK app.

Note: A plugin cannot freely modify or take over Pilot's existing UI. UI interaction must use the capabilities Pilot makes available, such as the plugin floating window, custom UI components, map widgets, AR projection, camera-view drawing, dialogs, and page navigation.

Local mode: Pilot and the MSDK app run independently

Remote mode: Pilot exposes capabilities; the MSDK plugin app calls them across processes

How Is a Plugin Used in Pilot?

After installation on the remote controller, a plugin is automatically recognized and managed by Pilot. Once the user enables it and the connection is established, the plugin can call open capabilities and be opened from the plugin floating window.

  1. Install the plugin APK.
  2. Enable the plugin on Pilot's plugin management page.
  3. Wait for the plugin to connect to Pilot.
  4. Open the plugin from the floating window and use its industry features.
  5. Disable the plugin on the management page when it is no longer needed.

Note: The plugin interface contract must be compatible with the Pilot version. MSDK checks compatibility automatically when connecting.

Next Steps

Last Updated: