2021 – 2023
WLTR
A unique project using autonomous robots for bricklaying, one of the first of its kind in the world. It represents a perfect collaboration between the startup ecosystem and corporations, working together on groundbreaking, innovative products.
My role
My role in the project was to oversee the complete delivery of the user interface for this unique bricklaying robot. I developed the initial concepts for the ideal flow from the perspective of the construction operator, ensuring that all potential critical states during operation were addressed.
I also designed the first UI screens, covering the most common use cases. Additionally, I organized the initial user research, conducted on-site visits to test the first control interface prototypes, and took responsibility for continuous user testing and design iterations.
In the later stages of the project, I provided constructive feedback on the work of the UX and UI designers and the developers involved.
The challenge
The biggest challenge of the project was the fact that such a project had never really existed in the world before, meaning all participants were building something unique together. There was no competition to analyze, no opportunity to see how others approached the problem, or what a standard interface between a robot and a human should look like in this case.
Another major challenge was designing the interface for highly diverse use cases. On a real construction site, there can be dust, noise, poor lighting, freezing temperatures, or the operator may be wearing gloves, for example.
Finally, but no less important, the construction and robotics industry is heavily regulated by numerous safety protocols aimed at protecting human health and property. These limitations often required us to modify the initial ideal interface designs and the processes that drove them.
The solution
We focused on understanding the needs and limitations directly from the perspective of construction workers who either operated the robot or worked near it. The interface was constantly changed and adjusted based on feedback from users, as well as from developers, who sent data through the API about what the robot was currently doing.
The interface designs also considered practical aspects, such as how the robot would be transported to the construction site, how it would move around, its maintenance requirements, potential malfunctions, and the possibility of critical safety situations arising around it so we were sure we are delivering a complete solution to the client.
The process
Initial meeting with the client
As always, I started by listening to the client and noting all of their initial wishes and requirements. From our discussion, it became clear that the client would handle the backend and API interface, and they needed help with the complete design and development of the user interface between the robot and the operator.
In addition to the client’s requests, I asked further questions that are crucial for my work. I was interested in aspects such as the type of device the interface would run on, whether we would have the opportunity to speak with real users of the new interface, whether we could test and iterate on prototypes, the project’s completion deadline, if they had a preference for a specific frontend framework that might set limitations for the UI, and whether we would track any specific metrics or collect data during the project.
From the client’s initial email.
Understanding the problem really in depth
From the initial conversations with the client, we understood their perspective and goals, but we still needed to map out other important aspects of the project. The client explained all the key aspects of construction site safety, something we, as digital designers, had never dealt with before.
In addition, we conducted desk research on standard industrial user interfaces currently available on the market. We also explored how to manage the authorization process to ensure only certain people can operate the robot, how the onboarding or user education process should be designed to ensure safety, and what corner cases or critical situations could arise on a real construction site.
They also introduced us to the Zebra device, on which the entire control system would run.
Screenshots from the existing industrial GUIs.
Understanding the physical characteristics of the project
For designers accustomed to creating purely virtual interfaces in a browser, it’s a significant challenge to shift their thinking and focus on the physical world where the final product will operate. I first had to map out the interactions between humans and machines in the physical realm to better design the virtual processes and corresponding digital interfaces.
Together with the client, we delved into the details of how the control tablet should function in both the physical and digital worlds. The tablet itself has numerous control buttons and several safety switches, including an authorization USB key, which the user must operate to perform any actions. The robot, and the entire construction environment around it, are interwoven with dozens of sensors, switches, and cables that must function correctly during construction, and the operator needs to always be aware of their current status or mode.
The robot is capable of moving around the construction site, so the operator needs to know several minutes in advance what will happen, where the arm will move, and the current phase of the construction process. The operator must also be able to easily handle emergency stops and restarts of the robot, as well as its regular maintenance and relocation to other sites.
An early app prototype in the cosntruction lab.
Flows and processes
Once we absorbed the initial information, we began designing the ideal structure for all the processes the operator should be able to control via the robot's tablet interface on the construction site.
Since the robot was not yet fully operational during the development of the interface and was still in rapid development, and there were no similar projects on the market from which we could draw inspiration, we decided to design all flows and processes based on a few key criteria.
The first was simplicity of operation for ordinary users, eliminating the need for complex and lengthy training. The second was ensuring maximum operational safety, where human health and life always take precedence over property or damage to the robot itself. Finally, we aimed to cover all possible real-world scenarios while adhering to all building regulations and standards related to working with robotic equipment.
One of many diagrams mapping the specific process states.
Functions mapping and GUI concepts
Two other designers and I each prepared several different versions of the interface during a joint workshop. This allowed us to compare our ideas and discover hidden potential for the solution that a single designer might not have been able to achieve alone.
From previous stages of the project, we had enough information about what the control interface needed to do and how all the background processes worked, but we still had to figure out how to simplify everything into an easy-to-use interface.
A key aspect was also striking the right balance between providing all the essential information at hand while avoiding overwhelming the user with too much data.
Initial UI concepts.
User testing
Since this was a highly innovative solution that was constantly evolving, our ability to conduct initial user research was quite limited. Therefore, I emphasized focusing more on testing the first functional interface concepts in a simulated construction environment.
The first testing sessions with the client and representatives from the construction industry—those who would ultimately interact with the robot—were conducted in our office using prepared props that simulated a real construction site.
I prepared the testing scenarios and then evaluated the critical findings from the report to guide further iterations of the interface we had designed.
Photos from the very first user testing.
Final UI
Based on several internal and user tests, we gradually began finalizing the graphical design of the application.
We always kept in mind that the design needed to be clear and highly usable even under difficult conditions that could occur on a construction site, such as poor lighting, sun glare, frost, or dust.
While working on the UI, we also had to account for touch controls, which were necessary, for example, for rotating the robot's 3D view in service mode.
Each screen was validated with developers to ensure that all proposed data and functions were accurately interpreted in the application’s control code.
Some of the hundreds of screens and states that needed to be designed.
The importance of client cooperation
At this point, it’s important to highlight the crucial collaboration between the client and us as designers.
Specifically, on this project, without the client's technical expertise, our work would have had a much more limited positive impact. His insights into robotics and construction were a vast source of knowledge for us.
Moreover, the client's enthusiasm and passion for his project served as a great motivation and boost for our entire team. This collaboration allowed us to deliver exceptional work in unexplored areas within a short period, which the client greatly appreciated.
Client’s testimonial.
Further development
The entire project has been, and continues to be, managed in a highly agile manner. Everything is now being fine-tuned based on the first real-world usage of the robot on construction sites. This allows us to collect feedback and improve both processes and the application interface.
At this stage, we are also starting to add new features that were not included in the development over the past months, as all efforts were focused on launching the project in a minimally necessary yet fully functional and useful configuration.
Photos from real construction.
The conclusion
For me personally, this has been one of the most interesting projects I’ve had the opportunity to be a part of in nearly twenty years of experience.
I learned many new things, even in fields I previously had no knowledge of, and developed a passion for digital products with a physical impact.
I firmly believe that my work contributed to the success of the project, which is now gaining significant attention from both the general public and industry experts and represents a major breakthrough in the construction industry.