Autonomous vessels can navigate routes, execute survey patterns, and respond to changing conditions. But operators still need to understand what those vessels are doing and step in when necessary.
Inspired by Sea Machines’ autonomous marine systems, I designed and built an interface for planning missions, supervising vessels, and maintaining fleet awareness.
As an added challenge, I attempted to make the interface intuitive enough to manage from a mobile phone.
Links
Keeping context close
I wanted operators to access information and controls where they’re already focused, rather than constantly looking between vessels on the map and disconnected panels.
The map adapts to support this, pulling back to show full mission routes, moving closer when focusing on a vessel, and adjusting its framing as tasks change.
The goal was to keep operators oriented and the information they need within easy reach with as little cognitive load as possible.
Off-screen vessel tags make it easy to locate and focus on individual vessels, with the entire fleet just a tap away.
Understanding without investigating
Operators need to understand a vessel before assigning it a mission, not just while it’s underway.
At a glance, they can see where vessels are and what they’re doing. Selecting one reveals more details and available actions, while changing conditions bring relevant information forward without requiring operators to dig for it.
Selecting a vessel brings its status and key details into view.
Charting a mission
I wanted mission planning to feel as direct as possible. Operators can place and adjust waypoints on the map, with numbered markers, clear direction, and a live route preview.
Speed controls and a final review let operators understand exactly what they’re asking a vessel to do before deployment.
Click on the vessel to start a mission, then place and adjust waypoints to chart its course.
Designing with varied screen sizes in mind
On a laptop, there’s room to build the experience around the map, with contextual controls and vessel popovers. On mobile, those same interactions become cumbersome and obscure the very thing operators need to see.
So I introduced a multi-stage bottom drawer that progressively reveals controls and details while keeping the vessel and route in view.
The following interactions explore how that approach carries across vessel selection, mission planning, route review, and activity history.
SR-01
IdleStormrunner
- Speed
- 0.0 kn
- Heading
- 135°
Position
- Latitude
- 42.3100° N
- Longitude
- 70.8500° W
Fuel
- Port
- 84%
- StarboardLow
- 24%
The popover operators see when they click on a vessel.
SR-01
IdleStormrunner
- Speed
- 0.0 kn
- Heading
- 135°
Fuel
- Port
- 84%
- StarboardLow
- 24%
Starboard fuel low24%
A multi-stage drawer designed for mobile, progressively revealing vessel details and mission controls while keeping the map in view.
SR-01 · Stormrunner
Plan a mission
On a laptop, mission planning opens in a panel beside the map so operators can choose a mission type while keeping the vessel in view.
Animated connections make the route’s progression clear as waypoints are placed, with live coordinates providing precise location feedback when using a mouse or trackpad.
The route summary brings waypoint coordinates, distance, and estimated travel time together, with animated values keeping changes readable as the route grows.
A two-stage route drawer keeps the map and vessel visible during mission planning while giving operators access to more detailed information when needed.
The responsive activity drawer opens from the left on desktop and from the bottom on mobile for easy viewing of vessel activity.
Designing for trust and control
Autonomous systems introduce an interesting design challenge: helping operators understand what’s happening, anticipate what comes next, and recognize when their attention is needed.
Throughout this exploration, I kept returning to one question: What does an operator need to know right now, and what can wait?
That question guided the interface, from adaptive map framing to progressive vessel details and responsive mission controls.
The goal was to make complex operations feel intuitive by revealing the right information at the right time, without sacrificing operator awareness or control.
Help wanted
I enjoyed building this interface more than I expected. It’s the kind of work I’d love to do more of, and I’m looking for opportunities to help teams make complex systems easier for people to operate.
If you’re building autonomous systems, or know someone who is, I’d love to connect and learn more about the challenges operators face.