DJI Enterprise App Guide 2026: One-Tap Dispatch, Mobile Drone & Dock Control, FlightHub 2 Integration & iOS/Android Differences

DJI's new Enterprise App closes a practical gap in the FlightHub 2 workflow: a field technician, security officer or incident commander can now create a location-based request, see available devices and work with a remotely connected aircraft without opening the desktop web platform.

What is the DJI Enterprise App?

DJI describes the Enterprise App as a lightweight drone-operations management platform designed to work with DJI FlightHub 2. Its current mobile functions include remote viewing and control of aircraft and dock devices, synchronized personnel/device/annotation locations, One-Tap Dispatch, and deployment or debugging for dock, ground-station and relay hardware.

The word lightweight matters. The App is an execution and collaboration surface for people in the field. It does not absorb all of FlightHub 2's organization setup, route libraries, automated-workflow design, data processing, reporting or cross-site governance. SpeedyDrone's FlightHub 2 multi-site operations guide remains the better starting point for the platform architecture.

The App extends a FlightHub 2 operation into the field. It should not be scoped as “FlightHub 2 Web, but on a smaller screen.”

Android vs iOS: the current difference that affects field teams

The core operating features are available on both platforms. The important exception is deployment and debugging: DJI currently includes it on Android but excludes it on iOS. That distinction affects device procurement for technicians who commission or troubleshoot dock infrastructure.

An operations manager can therefore use an iPhone for dispatch and monitoring while an Android device is assigned to the field-deployment kit. “Everyone installs the same app” is not yet a complete hardware plan if the same team must commission a Dock, Ground Station or relay.

How One-Tap Dispatch actually works

One-Tap Dispatch is not a blind “launch now” button. It is an incident-to-aircraft workflow. A user starts from an exception annotation, a person's current location or a searched map position, adds context and an alert level, and submits a request. An authorized dispatcher then chooses an available execution device and verifies flight parameters before launch.

Request and execution are different permissions

A field member may be able to report an issue or create a dispatch request, but DJI currently states that dispatching an aircraft requires Project Administrator permission. That separation supports a sensible command model: many people can surface an incident; a smaller group is authorized to commit an aircraft.

Role changes are handled in FlightHub 2's personnel and role-management settings. Advanced behaviour—recipients, assigned devices, flight parameters, aircraft actions, triggers and waypoint flight—also returns to the cloud platform under the DJI Enterprise App One-Tap Dispatch automated workflow.

What if several requests compete for the same aircraft?

DJI says the system prioritizes simultaneous dispatch requests by alert level. The higher-alert task is handled first; lower-priority tasks wait in the queue until the device becomes available. That makes the feature closer to a mobile incident-response queue than a standalone FlyTo control.

Remote viewing and immersive control from a phone

The App can open a live aircraft view, move into full-screen mode and request payload or aircraft control. With the required control, the operator can move the gimbal, pinch to zoom, switch supported lenses, focus or meter, capture photos/video, use virtual joysticks and command return-to-home.

Control is not assumed merely because video is visible. DJI separates payload control, which enables camera and gimbal actions, from aircraft control, which enables the virtual joysticks. After aircraft control is obtained, the phone user is directly controlling the aircraft. Exiting control releases the permission; the aircraft may hover or continue its mission depending on its current state and configuration.

Network and lost-link behaviour

DJI recommends a stable 4G, 5G or Wi-Fi connection. If the App stays in the background for more than five minutes, the livestream closes and control is released. If the App exits or the network connection is interrupted, the aircraft follows its configured lost-link action—typically hover or automatic return-to-home. The correct conclusion is not “a phone disconnect crashes the aircraft,” but also not “mobile control is risk-free.” The preset behaviour must be verified for the actual aircraft and mission.

Map collaboration: the field-to-cloud handoff

Map collaboration turns the App into more than a remote controller. Users can create point, line and polygon annotations; add a name, description and on-site photos; share the record with project members; and open the location in a supported third-party navigation app. DJI's current FAQ lists navigation options according to what is installed and available in the region, including Google Maps.

A utility workflow illustrates the value: a technician finds a damaged pole, creates a geo-referenced point with a photo, assigns the agreed alert level and submits a dispatch request. A project administrator selects a connected dock aircraft, verifies the parameters and launches. The team then uses live video and camera control to inspect the problem, while FlightHub 2 retains the shared operational context.

Device deployment and debugging: useful, but not universal

On supported Android devices, the Enterprise App can assist with deploying and debugging DJI Dock series hardware, Ground Stations and relay stations. DJI's device-management documentation describes a dual-head USB-C connection between the phone and the Dock or Ground Station. The deployment flow then requests the Organization ID, Device Binding Code and the relevant Ground Station, Dock and aircraft names.

A Dock or Ground Station can be bound to only one organization at a time. Switching organizations requires unbinding it first. The flow is therefore operationally significant; it is not a casual Bluetooth-style pairing step. Keep device identity, organization ownership and commissioning records under change control.

The on-premises caveat

DJI's Enterprise App overview says the features in the September 2026 update are not currently supported by the on-premises version. Separate FlightHub 2 device-management documentation still describes using the App to bind a Dock or Ground Station to an on-premises environment. These statements are not safely reduced to “the App works” or “the App does not work.” Treat app-assisted binding and the new mobile operating features as separate scopes, and confirm the exact supported workflow before an on-premises deployment.

DJI Pilot 2 vs Enterprise App vs FlightHub 2

These three tools overlap, but they occupy different points in the operating system. A team usually does not choose only one; it assigns each interface to the role it serves best.

FlightHub 2 currently lists Dock 3, Dock 2, the original Dock, Matrice 350 RTK, Matrice 30 Series, Matrice 300 RTK, Mavic 3E/3T/3T Advanced, Matrice 3D Series, Matrice 4 Series, Matrice 4D Series and Matrice 400 in its supported-device ecosystem. That list is not a promise that every model supports every App function. Payload, firmware, controller, dock relationship, operation mode and project configuration still determine the feature available.

Four workflows that fit the App

Does One-Tap Dispatch make a remote flight legal in Canada?

No. The App is an operating tool; it does not determine the legal category of a flight or grant airspace access. The Canadian answer must be based on the aircraft, location, population density, airspace, operating distance, people involved and the organization's certificates and procedures.

Since November 4, 2025, some lower-risk BVLOS operations can be conducted under Canada's Level 1 Complex framework without an SFOC-RPAS. Those operations require the appropriate Level 1 Complex pilot certificate, operation under an RPAS Operator Certificate (RPOC), an eligible registered aircraft with the applicable safety assurance, and compliance with the operating limits. Flights outside the basic, advanced or Level 1 Complex rules still require the applicable special permission, such as an SFOC-RPAS.

Transport Canada also requires site and airspace assessment; local, provincial and other federal obligations can still apply. Use the official Level 1 Complex operations guide and special drone operations guidance for the current rules. SpeedyDrone's BVLOS readiness guide for Canadian organizations covers the operational program around the software.

Current SpeedyDrone hardware path

The mobile App becomes most valuable when it is designed into a complete connected operation. These are the exact current SpeedyDrone listings for the Dock 3 and a controller-equipped Matrice 4D. Availability and final configuration should be confirmed for the intended public-cloud, remote-controller or dock workflow.

DJI Dock 3Remote and vehicle-mount-capable dock platform for Matrice 4D Series operations → DJI Matrice 4D (RC Plus 2)+Controller-equipped Matrice 4D listing for field and FlightHub-compatible workflows →