Mobile, Payload and Cloud solve different problems
Mobile SDK supports applications that access functions of supported aircraft and cameras from compatible mobile environments. Payload SDK addresses payload integration; Cloud API addresses cloud integration for supported enterprise products. These are different integration layers. Decide whether you need a controller-side shooting interface, a custom payload or an operational cloud service before choosing one. A consumer aircraft’s first-party app feature cannot be assumed available merely because a similarly named capability appears in enterprise Cloud API documentation. Start from the required function and map it to the appropriate supported interface. If the requirement is only synchronized configuration and recording, do not add autonomous flight without a reason. Keep scope tied to the shot and document each function’s access and connection requirements.
Read compatibility as a complete combination
Compatibility is a combination of aircraft, controller, SDK version and firmware, with operating system, camera and connection details where relevant. The V5 material checked for this guide includes Mini 4 Pro support, illustrating why old blanket statements about the Mini family are unreliable. Inclusion in a product list still does not establish support for every mission or camera function. Read release notes, per-API support information and runtime capability results. Preserve the date and documentation links with the tested configuration so another developer can reproduce the result. Keep supported, unsupported and unverified as distinct states. Run the same bounded tests before and after an SDK update and identify behavioral changes explicitly.
A minimal aerial-filming integration test
Our original validation sequence is connection and telemetry, camera configuration, recording state, gimbal commands and only then flight missions. Separate successful command submission from confirmation that the requested state actually occurred. For waypoints, test altitude reference, coordinates, heading, gimbal behavior, arrival actions, interruption, resumption and connection loss. First-party waypoint features, SDK mission execution and an application driving virtual-stick commands are different implementations. Use supported simulation or ground validation before flight, and complete failure handling before adding a complex cinematic path. Design partial-failure reporting for grouped settings. Recording may start while a lens or framing change fails. Approve a take only after its required conditions are confirmed.
YOUR NEXT STEP
Put it into practice.
- Do not mix V4/V5 or Android/iOS compatibility claims.
- A supported product listing does not mean every API is supported.
Sources and editorial scope
Explanations and exercises are original editorial material. Verify product-specific conditions against the linked documentation version.
- DJI — Mobile SDK V5 release notes and supported products ↗
- DJI — Mobile-SDK-Android-V5 official repository ↗
- DJI — Cloud API documentation ↗
- DJI — Payload SDK official repository ↗
Research date: 21 October 2026. Check the linked version, supported hardware and applicable conditions. Evidence includes directly reviewed text and official search-index records.
Read the methodology and open questions →