Leafy
Helping plant parents manage and organize plant care tasks.
Helping plant parents manage and organize plant care tasks.
Helping plant parents manage and organize plant care tasks.
MY ROLE
The full design process including discovery, ideation, user flows, prototyping, and testing.
PROJECT TIMELINE
6 weeks
How do they do it?
COMPETITIVE ANALYSIS
A search on the app store showed me that there are already apps that provide plant care support. I compared three of the most popular, including Planta, Blossom, and Vera by using them directly and by reading user reviews.
User reviews on all three apps reflected a desire for a nice-looking app with specific plant care guidance and features that are available to try for free, but most importantly they wanted the available features to function as promised.
A search on the app store showed me that there are already apps that provide plant care support. I compared three of the most popular, including Planta, Blossom, and Vera by using them directly and by reading user reviews.
User reviews on all three apps reflected a desire for a nice-looking app with specific plant care guidance and features that are available to try for free, but most importantly they wanted the available features to function as promised.
A search on the app store showed me that there are already apps that provide plant care support. I compared three of the most popular, including Planta, Blossom, and Vera by using them directly and by reading user reviews.
User reviews on all three apps reflected a desire for a nice-looking app with specific plant care guidance and features that are available to try for free, but most importantly they wanted the available features to function as promised.
Surveying Plant Parents
SURVEY DESIGN & IMPLEMENTATION
I wanted to hear more from plant parents about their experiences with plant care and areas in which they would most like more support. I had specific, concrete information I wanted to collect, which I determined would best be captured by a survey. I designed and conducted a survey with 30 plant parents.
I wanted to hear more from plant parents about their experiences with plant care and areas in which they would most like more support. I had specific, concrete information I wanted to collect, which I determined would best be captured by a survey. I designed and conducted a survey with 30 plant parents.
I wanted to hear more from plant parents about their experiences with plant care and areas in which they would most like more support. I had specific, concrete information I wanted to collect, which I determined would best be captured by a survey. I designed and conducted a survey with 30 plant parents.
Survey Takeaways
63%
63%
63%
were novice plant parents, having cared for plants between 1-3 years, and still felt unsure about their abilities.
were novice plant parents, having cared for plants between 1-3 years, and still felt unsure about their abilities.
were novice plant parents, having cared for plants between 1-3 years, and still felt unsure about their abilities.
97%
97%
97%
said they look online for plant care guidance, but many said it's difficult to find detailed, specific information.
said they look online for plant care guidance, but many said it's difficult to find detailed, specific information.
said they look online for plant care guidance, but many said it's difficult to find detailed, specific information.
2
primary challenges stood out with diagnosing problems being the most commonly cited, followed by tracking care tasks.
primary challenges stood out with diagnosing problems being the most commonly cited, followed by tracking care tasks.
primary challenges stood out with diagnosing problems being the most commonly cited, followed by tracking care tasks.
Understanding the User
PERSONA
My survey results were a starting point to understanding the needs and perspectives of my users. I used those results to create two personas—one to reflect a user who is a novice plant parent, based on the majority of my survey results, and the other is based on the more advanced plant parent.
My survey results were a starting point to understanding the needs and perspectives of my users. I used those results to create two personas—one to reflect a user who is a novice plant parent, based on the majority of my survey results, and the other is based on the more advanced plant parent.
My survey results were a starting point to understanding the needs and perspectives of my users. I used those results to create two personas—one to reflect a user who is a novice plant parent, based on the majority of my survey results, and the other is based on the more advanced plant parent.
Defining Leafy
IMPACT/EFFORT MATRIX
I organized a list of possible features into an impact/effort matrix to figure out what to prioritize. While many survey participants said they wanted support in diagnosing plant problems, the impact/effort matrix results showed that diagnosis was a high-effort feature that had a potential for high impact, but only in situations where users have an unidentified problem with their plant.
Ultimately, I decided to focus on reminders and tracking for plant care tasks. Even though it was the second most desired type of support according to my survey results, a user’s need to track plant care tasks would be ongoing and consistent.
I organized a list of possible features into an impact/effort matrix to figure out what to prioritize. While many survey participants said they wanted support in diagnosing plant problems, the impact/effort matrix results showed that diagnosis was a high-effort feature that had a potential for high impact, but only in situations where users have an unidentified problem with their plant.
Ultimately, I decided to focus on reminders and tracking for plant care tasks. Even though it was the second most desired type of support according to my survey results, a user’s need to track plant care tasks would be ongoing and consistent.
I organized a list of possible features into an impact/effort matrix to figure out what to prioritize. While many survey participants said they wanted support in diagnosing plant problems, the impact/effort matrix results showed that diagnosis was a high-effort feature that had a potential for high impact, but only in situations where users have an unidentified problem with their plant.
Ultimately, I decided to focus on reminders and tracking for plant care tasks. Even though it was the second most desired type of support according to my survey results, a user’s need to track plant care tasks would be ongoing and consistent.
Lauren's User Journey
USER JOURNEY
I used my persona, Lauren, to consider how a user might find their way to the app and how it could add value to their plant care process. In doing so I was also able to begin visualizing how Leafy would be structured and organized in a clear and usable way.
I used my persona, Lauren, to consider how a user might find their way to the app and how it could add value to their plant care process. In doing so I was also able to begin visualizing how Leafy would be structured and organized in a clear and usable way.
I used my persona, Lauren, to consider how a user might find their way to the app and how it could add value to their plant care process. In doing so I was also able to begin visualizing how Leafy would be structured and organized in a clear and usable way.
Design Evolution
PROTOTYPING & TESTING
From sketching to prototype, the design underwent many adjustments as I considered the end goal from my above user journey—giving plant parents greater confidence and support in their ability to care for their plants.
The following examples show my process of taking two of the app's most essential screens from low-fidelity sketches to a high-fidelity design using valuable feedback received during usability testing.
From sketching to prototype, the design underwent many adjustments as I considered the end goal from my above user journey—giving plant parents greater confidence and support in their ability to care for their plants.
The following examples show my process of taking two of the app's most essential screens from low-fidelity sketches to a high-fidelity design using valuable feedback received during usability testing.
From sketching to prototype, the design underwent many adjustments as I considered the end goal from my above user journey—giving plant parents greater confidence and support in their ability to care for their plants.
The following examples show my process of taking two of the app's most essential screens from low-fidelity sketches to a high-fidelity design using valuable feedback received during usability testing.
Home Page
Plant Profile Page
Leafy in Action
FINAL PROTOTYPE
This video of the final prototype shows how a user would add a new plant to their collection.
This video of the final prototype shows how a user would add a new plant to their collection.
This video of the final prototype shows how a user would add a new plant to their collection.
Reflections
Reflections
Reflections
Because this was an end-to-end design, I learned a lot about staying focused on the MVP. I received a wealth of valuable feedback throughout the process that included suggestions of additional features or mechanics that I could add. Some of these I implemented, but some I made the difficult decision to leave out. What I realized was that there will always be improvements to make or things to add and it's both challenging and important to set a limit when time is of the essence. That being said, I would love to keep exploring new ideas for Leafy in the future.
Because this was an end-to-end design, I learned a lot about staying focused on the MVP. I received a wealth of valuable feedback throughout the process that included suggestions of additional features or mechanics that I could add. Some of these I implemented, but some I made the difficult decision to leave out. What I realized was that there will always be improvements to make or things to add and it's both challenging and important to set a limit when time is of the essence. That being said, I would love to keep exploring new ideas for Leafy in the future.
Because this was an end-to-end design, I learned a lot about staying focused on the MVP. I received a wealth of valuable feedback throughout the process that included suggestions of additional features or mechanics that I could add. Some of these I implemented, but some I made the difficult decision to leave out. What I realized was that there will always be improvements to make or things to add and it's both challenging and important to set a limit when time is of the essence. That being said, I would love to keep exploring new ideas for Leafy in the future.
