Peer Robotics

Peer's brand colour is red, and in an interface, red already means something: error, stop, danger. Using it as an accent could have been a trap. Instead we let it play both parts, carrying error and emergency states where the meaning is real, and marking the primary action on any screen where nothing should be missed. We built the rest of the system on the brand's warmer tones, achieving an identity that looks like nothing else in the category.

The most useful thing we built may be the thing we left unfinished. In addition to a fixed dashboard interface, our team also designed a kit of components for creating custom interfaces. This could be used by any user to create custom screens for simple actions such as sending a robot to its charging station.

The robots build their own map of the factory as they move through it. Our job was to make that map legible for operators that reads at a glance. We worked through a lot of versions before landing on one that stays simple without hiding information. A technician glancing at it mid-task should know where everything is, and where the robot isn't allowed to go, before they've consciously read a thing.

Every setting and workflow used to live in one long list down the left panel. We grouped them into three: Control Center, Administration, Configuration. Control Center is everything to do with driving robots and fleets; Administration holds the admin-level settings; Configuration handles the specific properties and behaviours of individual robots. Most operators only ever need the Control Center. So the moment they open the app, the noise falls away and the thing they came to do is right in front of them.