Decide between DJI Mobile SDK V5 (on-aircraft app control) and Cloud API (server-side integration)
domain: developer.dji.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Clarify the integration point: Mobile SDK V5 controls the aircraft directly from a companion mobile app, while Cloud API integrates DJI Pilot 2 / Dock with a third-party backend over MQTT/HTTPS
For direct flight control, gimbal/camera control, or a custom ground-control mobile app, use Mobile SDK V5 (Android/iOS) which handles flight stabilization and low-level device management
For fleet dashboards, remote mission dispatch, or cross-device server integrations, use Cloud API instead of trying to proxy Mobile SDK calls through a server
Confirm aircraft/dock model compatibility separately for each SDK track, since not every enterprise model is supported by both
Prototype against the official sample apps (Mobile-SDK-Android-V5 / Cloud-API-Doc GitHub repos) before committing to production architecture
Known gotchas
Mobile SDK V5 requires native mobile development experience; Cloud API assumes front-end/back-end web development skills — picking the wrong track wastes ramp-up time
The two SDKs are not interchangeable at the API level — migrating a Mobile SDK app to a Cloud API backend is effectively a rewrite, not a port
Enterprise dock automation (unattended missions) is only exposed through Cloud API, not Mobile SDK V5
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?