A private field-ops app for tandem pilots delivering GoPro footage
The challenge behind the build
Right after landing, a tandem pilot has minutes, not hours: connect to the camera over Wi-Fi and Bluetooth, pull full-quality footage, show the client, hand off files to their device, and clean up the camera safely — all before the next flight.
The implementation goal
Build a SwiftUI app with Media, Flight Book, GoPro Labs, and App Settings modules covering GoPro camera profiles, connection checks, the import workflow, Apple Photos album export, Android QR transfer, daily backup, and support diagnostics.
One guided sequence from camera to client
Media Sync Desk turns a fragile, manual sequence into an app-guided one: connect to the camera, import full-quality media into a flight-named Apple Photos album, review it with the client, transfer it to Android devices over the local network, back it up, and only then unlock cleanup — with recovery prompts if a flight's media was already imported.
Our other projects
The brief was to support the real landing workflow for tandem pilots: connect to the camera, import full-quality media, show the client, deliver files, and clean up safely.
Field media delivery is messy because camera Wi-Fi, Bluetooth wake, Apple Photos, Android clients, ZIP exports, and post-flight cleanup all happen under time pressure.
The app is private and field-tested in stages, not broadly released. Public content has to avoid implying an App Store launch or unverified support across every GoPro model.
SoFlow built a SwiftUI app with Media, Flight Book, GoPro Labs, and App Settings modules, including GoPro camera profiles, connection checks, the import workflow, Apple Photos album export, Android QR transfer, daily backup, and support diagnostics.
SwiftUI and AVFoundation drive the on-device experience; GoPro cameras are reached over local Wi-Fi/BLE and HTTP for connection and import; a local HTTP server handles resumable Android QR transfer; and Apple Photos, ZIP export, and optional Flight Book/Google Drive handoff cover storage, delivery, and backup.
- GoPro camera library with per-model connection profiles and health checks
- Full-quality media import into flight-named Apple Photos albums
- Already-imported detection with recovery prompts
- Android QR transfer with resumable HTTP range requests
- Client album and daily backup ZIP exports
- Flight Book handoff and built-in diagnostics
Media Sync Desk shows SoFlow's ability to design native operational software for real field constraints — not just websites and browser tools, but apps that hold up under time pressure and hardware quirks.
- Working Media, Flight Book, GoPro Labs, and App Settings modules confirmed in the app's experimental catalog
- Debug simulator build and launch passed release-readiness checks
- Real-device GoPro behavior still requires per-model smoke testing before broader claims
Who is this app actually built for?
Tandem pilots — people who land, and within minutes need to show a client their flight footage, hand off files, and get ready for the next flight. Every screen in the app is built around that specific time-pressured sequence, not a generic media gallery.
Why put this in Webflow if external code is involved?
Webflow is the public storytelling and CMS layer. External code should stay in the app, Worker, or integration layer where it can be versioned, secured, and tested.
What is needed before publishing?
Non-private media screenshots, and clear language that GoPro model support and device behavior still need to be verified per model and release branch before any broad public claims.
This proves SoFlow can turn a fragile, time-pressured real-world workflow into a guided native app with built-in safety checks and delivery fallbacks — a level of operational software beyond typical web work.
Who is this app actually built for?
Tandem pilots — people who land, and within minutes need to show a client their flight footage, hand off files, and get ready for the next flight. Every screen in the app is built around that specific time-pressured sequence, not a generic media gallery.
Why put this in Webflow if external code is involved?
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Post-flight media handling depended on manual camera operation, ad hoc file transfer decisions, and individual pilot discipline around cleanup — all under time pressure in the field.
The workflow is now an app-guided sequence where import, client review, delivery, backup, and cleanup are explicit steps with built-in safety checks, instead of memory and manual judgment calls.
This workflow needs native device permissions, direct Apple Photos access, local network transfer, camera Wi-Fi/BLE handling, and background-safe import state — none of which a Webflow site or embed can provide.
