ds Smart Home App
Role
Lead UX & UI & Interaction Designer
Activities
Setting up design environment and tools
Lead concept
UI Design
Inforamtion Architecture
Prototypes
Usability Tests
Guidelines for Design System
Research
Tools
Figma
Protopie
Sketch
Photoshop
Balsamiq
Rotato
Team
Distributed Team - Zurich, Bern, Belgrade, Frankfurt - Team of 10 (2 UX, 5 Devs, PM, PO, Account Manager)
Achivement
Created a smart home app with the following three goals successfully achieved:
The app was designed for iOS, Android, tablets, & web
dark | light
Project Background
Collaborated with digitalSTROM to build a smart home app where users can connect and control all their smart home devices and have an overview of their home. With the app, users are able to set right scenarios according to their needs from wherever they are.
digitalSTROM partnered with different IoT device manufacturers like Philips Hue, V-ZUG, Smarter to enable third-party device control.
The digitalSTROM technology also allows users to incorporate none smart devices into the smart home system by connecting them to a digitalSTROM switch. This means that any pluged in device can at least be turned on or off with the app.
1
2
3
As much as Smart Homes and Internet of Things are used as buzz words in our tech world, for many of our households, incorporating the technology into our daily routine can be scary and uncomfortable. Changing our habits accordingly to the new system can mean that the new technology can really have a big impact on our lives. This was the biggest challenge for us as a designer: Building the right app for the right people. Users can be family members ranging from kids to elderly members. The app should be accessible to everyone regardless of their age or their understanding of technology. Therefore, it was crucial for us to understand our users, their daily routines and behaviors to find the right solution, balance, and offer features that can provide benefits to everyone.
Click to enlarge
When creating the information architecture for this application, it was very interesting to see how different each interviewed
individual's mental model was. For example, the option to create a scenario was expected by some users to be found in the room
overview screen, by some on the landing page and by a little group within the settings menu. Even after multiple interviews,
there was no clear answer to this question, so we decided to have these options on multiple screens like the landing page and
the room overview screen.
A later usability test showed that users were very happy with this solution and saw it as convenient to have the option to
create scenarios from different locations of the app.
Since this product has a high complexity and will run for a couple of years with regular updates and grow with new devices supported, we heavily relied on a
design system to stay organized. It helped our team to collaborate and quickly find and use the right components, patterns, and styles.
We used Figma to design the app and build a consistent component library. Having a
well structured component library helped us to quickly update any changes onto the entire design.
It saved us a lot of time when creating new screens, which had the same or similar components. Our developers were also able to view our
Figma design files, and they always had one source of truth
for all assets, screens or user workflows.
A unified design language was very important in providing consistent experiences to our users when controlling devices or navigating the app. It should always feel familiar, intuitive and a user should be able to reuse gained interaction- or
design-knowledge learned, from one place in the app in another place. We not only wanted to make the app feel familiar and intuitive but also help users to feel confident and smarter whenever they use the app.
Some UIs needed detailed interaction prototyping to clearly communicate how they will work. In such cases, I first sketched out the interaction patterns to give the team a rough idea on how the UI should look like and gathered some feedback and inputs. Based on those sketches and feedbacks, I then prototyped those patterns to give everyone a clear understanding of the complete interaction and complexity. These steps were very valuable because they helped a lot with estimating development time and effort as well as bringing everyone on the same page. This temperature control prototype was built with ProtoPie, which turned out to be the fittest tool to visualize and share this specific interaction after some explorations with other tools.
Visualization of each element of the UI to help estimate implementation complexity
After creating a first concept of the temperature UI with its interactions, we figured it would cost too much to implement. As a next logical step, we stripped down all components that added complexity but still tried to have a final result which is similar and still provides all the information and adjustment options. We were very happy with the final result and this process showed the team how important it is to try, test, negotiate and iterate our product.
The app was well received by users after publishing the app to the app store.