Since all previous posts have showcased the red nightmode of the interface, it is about time to visualise it in day mode. I tried different shades of green, and the a combination of white text, bright green elements and another darker green background shade.
I used red in the previous interfaces because it is one of few colors that do not disturb night vision. It is argued that red might be confused with alarms. That might be true, but I believe this interface manages to separate itself from alarms.
Layered scenario video from Hanne Morstad on Vimeo.
A clip of how the captain works with the different interface modes and what interactions he utilises during different stages of a mission to collect a sample from an iceberg. As he gets close to where the operation is most intense, the part of the communication interface the captain actually needs is only the widget showing the name of the person addressing him. Prior to complex operations at sea is when you set up groups and manage them, test connections and such. Closer in time to the operation is when you need some fast choices from the menu, like calling the head engineer and deliver the message that you are taking over power control to enter DP mode.
Interface click-through from Hanne Morstad on Vimeo.
A video of how to get through the menu of the bridge communication interface. I examplified some of the actions you can do. Note that this video does not have sound.
Where I have decided to position the communication interface has been decided with the help of Gustav and Chris’ UX architecture, and is also according to the elements it is built of. The main points are that:
Continue reading “Interface positioning”
How I have built the communications interface is based on the level of complexity the user needs at a given time. When the captain has a lot to do and can not focus on communication other than talking, the interface will be as minimal as possible, showing only the name of the one talking to him. If the captain has some communication needs that needs to be done quick, the next layer, the radial menu, gives quick access to the most useful features. When the captain is calm, has a cup of coffee and can focus more on complex actions in the communication menu, the next layer is naturally more detailed.
The interface I built in Adobe Muse shows how the menu is built up:
Here is a snippet of the interface design for communication in AR:
Video test interface (Converted)
The menu button to get into the communication interface is not just a button, but will also react to and show you who is communicating with you or in the group you are broadcasting in.
To test the different ways for the crew to work, interactions and interfaces, I drew some smaller scenarios. These are some of the rules I stick to:
The captain and second officer are the main users
I have gone away from thinking that there will be radio channels in the future, and gone over to groups instead.
Continue reading “Scenarios”
The research period for this project was long, and will probably not stop until it is all over. Starting to apply all the knowledge and insights meant going into a different mode, and at first I just continued mapping scenarios, but I had to start drawing actual designs.
Continue reading “How to apply all the research?”
In this post, I sum up my insight by making claims, asking questions and answering them, and finally setting some specifications my design should follow
Continue reading “Guidelines for communication”