MightyDash
Product strategy, privacy, and native iOS delivery shaped around a real-world safety use case.
My Role in this Project
- Product strategy and feature planning
- User flows and interface design
- Privacy model and data decisions
- Native iOS implementation
- Field testing and launch planning
Technologies Used
- Swift and SwiftUI
- AVFoundation video capture
- Core Location
- On-device media storage
- Next.js and TypeScript
The Impact
- Repurposes an existing iPhone
- Keeps trip footage private
- Makes clip review effortless
- Guides sustainable recording
- Removes accounts and subscriptions
A closer look.
Explore the screens. Select an image to view it full size.
The rationale
Keep the footage. Skip the surveillance.
MightyDash started with a practical question: if an iPhone already has an excellent camera, fast storage, GPS, and a screen built for the car, why should someone need another expensive device just to remember what happened on the road? A mounted phone already has most of the hardware. It needed software focused on doing one job clearly and reliably.
Dashcam footage is unusually personal. A single drive can show where someone lives, when they leave, who rides with them, what was said in the car, and how different trips fit together. Uploading that footage for convenience changes who controls a readable copy of the story. I wanted MightyDash to provide the protection of a dashcam without turning everyday travel into another source of behavioral data.
That decision shaped the product from the foundation up. Recordings stay inside the app on the iPhone. There is no account, cloud video sync, analytics, telemetry, advertising, tracking, or third-party SDK quietly watching from the passenger seat. Audio, speed, location labels, and saving to Photos are choices instead of assumptions.
Simple does not have to mean limited. Drivers can begin with a deliberately light 720p and 24 fps setup, then move to 1080p, 4K, higher frame rates, ultra-wide capture, or simultaneous front and rear video when their iPhone supports it. Recording Health makes that flexibility understandable by showing how comfortably the current device and conditions are handling the workload.
The same restraint applies after the drive. MightyDash breaks footage into manageable clips, groups them by day, adds useful thumbnails and optional location context, and makes playback or export explicit. Automatic cleanup keeps local storage from becoming a second problem, while the driver decides how many days of history are actually worth keeping.
The goal is not to make a phone imitate every feature of an elaborate dashcam system. It is to make the camera someone already owns useful in the moments that matter, while respecting the boundaries that should have been standard all along. MightyDash remembers the road, then gets out of the way.
Keep exploring
Additional reading
More of the thinking that shaped MightyDash.