Skip to main content

​
Checklist

  1. Charge the pilot tablet, phone, or drone controller and confirm aircraft/controller are ready.
  2. Install or update AlphaRelay Operator. Download the Android APK from alpha-relay.com/download.html; install the iOS app through the organization TestFlight invitation.
  3. Confirm the device license is active (scan QR, enter an ar-… key, or use a non-expiring one-installation pairing code).
  4. Sign in to the web app with the correct operator account. On shared Operator devices, refresh online and confirm the current pilot appears in the operator selector.
  5. Open Mission Overwatch once while online in each browser the team will use in the field. This saves the basic page so it can reopen during a connection problem; current mission information still needs internet.
  6. Run a test Start Mission flow and confirm remote live starts automatically when the pilot device is online.
  7. Confirm the Mission Overwatch browser can use its microphone if the team plans to use Dictate for manual events or Live Ask AI questions.
  8. If a second Android or iOS device will use Mission Viewer, activate its own license and test that it can see an active mission, remote video, timeline events, and alerts.
  9. If Operational Map will be used, select the correct person on every sharing device, allow precise location and background location when asked, test Share Location or Mission Viewer automatic sharing, and confirm the mission Map shows the correct person. Verify that the route finishes saving after stop.
  10. If live AI will be used, confirm your agency’s selected mode, allow alerts, and test the actual video source. For on-device checks, verify a completed check before flight. If Hybrid cloud review is offered, confirm whether it is selected. Test loss of internet using a video source that can continue offline.
  11. For Android drone controllers: install AlphaRelay Operator, activate the device license, run a test Controller Screen Capture mission, and confirm Android screen capture permission works. If the crew will use Pilot mode, also confirm the aircraft appears in the supported list and passes AlphaRelay’s live connection check.
  12. For Video Link, test the exact authorized QR code or web link, confirm video reaches Mission Viewer, and verify that closeout produces a playable recording. Keep the link available to paste if camera scanning fails.
  13. For Controller Livestream, test the intended Operator or Command Center New Livestream setup path. Confirm the controller accepts the displayed DJI RTMP or Skydio RTSP External Server values, can reconnect, and produces playable closeout footage. RTMP stream keys and RTSP stream names are separate six-digit values.
  14. For HDMI Capture Card, test the exact controller, USB HDMI capture card, cable or powered hub, Android device, USB-C iPad, or laptop. Verify the full picture, a sustained recording, and recovery after unplugging and reconnecting once.
  15. For laptop HDMI, test New HDMI mission, Mission sidebar → HDMI Input, browser camera permission, Connect & go live, Stop & upload, and Recover interrupted recording. Do not clear browser data before recovery.
  16. For iPhone or iPad: confirm iOS 26 and test Screen Recording, Video Link, Controller Livestream, or iPad HDMI as applicable. Allow microphone or speech access if needed. Allow Live Activities or Screen Sharing notifications, and verify alerts in the sideways flight-app view and completed recordings on the actual device.
  17. For a DJI Avata with compatible DJI Goggles: install DJI Fly and AlphaRelay Operator on the Android device, test the supported goggles live-view connection, and confirm remote live and post-mission upload.
  18. Check the Operator startup screen for older video waiting to upload and let it finish, or consciously choose Skip for now and start new mission.
  19. Plan for internet when you need remote viewing, Video Link, Controller Livestream, Mission Viewer, live map updates, online Live AI, uploads to the agency account, reports, or exports.
  20. If the mission uses an agency scenario, confirm it appears in mission setup and that its visible AI watch targets and Quick Events are current.
  21. Assign pilot, overwatch user, reviewer, and supervisor roles.

​
Connection quick reference

The current public Operator workflow does not show a Local Network mission button. If your agency’s Android build includes it, both devices must be on the same Wi-Fi. It remains separate from internet upload.
Pilots can hide on-screen drone controls and use the physical controller while keeping quick events and relay status visible. See Minimum requirements for device specs.