Planto is an app designed to make plant care convenient and intuitive, even for the full-time individual.
Integrate Planto easily for thriving plants!
Team: Breanna Dulay, Piotr Soldaj
Supervisor: Felix Hermann
WS2022 / 2 mo. timeline
Category
Visual Prototyping
User Experience
Interaction Design
Digital Product Design
Communication Design
Toolkit
The Problem
Plant care apps can be a godsend for the busy person, so it’s no surprise that there’s an abundance of them. Though another reason can be attributed to their lack of user-friendliness, making them prone to
short-term usage.
While one app may have extraordinary diagnosis features and easy setup, editing settings later on can be frustrating.
We designed an app prototype that would be intuitive to set up and ensures long-term use, for both the novice and seasoned plant parent.
empathize
research
ideation
prototype
Design Process
empathize
First we had to consider our users:
A persona is defined to identify
user needs.
Why is this necessary?
User centered brainstorming sets the foundation for our design.
Research
To inform our design process and understand our users,
we question and observe.
We took notes on competitor apps, analyzing reviews for what worked and what didn’t work.
Then, we tested the apps and did some benchmarking to gain further insights.
What is already on the market and what do they offer?
What features aren’t so user friendly?
What features are positively received?
What do people wish to see?
ideation
We reflected on our observations to form a guiding statement for our team:
and used guidelines to structure our design.
Users should be able to intuitively use our app and watering sensor to maintain long-term plant health.
Guidelines
Fully functional mobile prototype
Lo-Fidelity -> Mid -> Hi Fidelity
Contemporary design that is minimal and functional
Easy, intuitive, targeted user flow
Enjoyable interactions
Good UX Principles
Accessible
Utility
Joy of Use
Usability
App Requirements
*supervisor outlined
We built 2 user journey maps, one for the user’s initial setup,
and another for the user’s daily use.
We sketched out iterations of our interface,
and developed our sketches after receiving feedback.
To keep our design consistent, we built a style guide.
With a good foundation, we built lo-fidelity prototypes,
Prototype
and cycled between revising and evaluating,
before we built our final protoype.