Ideation

To create a general idea of how I wanted to design my screens, I created 8 rough draft sketches. 

• My competitive analysis highlighted the importance of having an upcoming to-do list on the home page that ties in with each specific plant’s page. 

• My survey analysis emphasized the importance of providing a troubleshooting option to help users diagnose their plants quickly. 

• My “How Might We” statements also helped me keep in mind other important features I want my project to include such as reminders, care plan customizations, and correct plant-care information.

User Stories

To determine the key features necessary for my project and therefore create an MVP (minimum viable product), I developed user stories consisting of essential functions that focus on the core values of my solution. 

1

As a user,
I want to keep track of my different plant care metrics and routines so that I can avoid over or underwatering specific plants. 

Site Map

My site map visually represents the applications' main screens with their responding features and functions. Creating a site map allowed me to decide where I would place each function within my project, including where the troubleshooting articles could be found, and where the plant care to-do list could be viewed. 

• In some cases, I found displaying a feature in two locations gave the app a better organizational flow. This allows the user to locate their main information intuitively. 

• For example, my user stories emphasized the importance of placing the diagnosis page on the primary navigation bar so users could diagnose a plant at any point in their journey. 

User Flows

Once I created my site map, I then mapped out 3 separate user flows that would be crucial to the survival of users’ plants. By doing so I could determine where each click could take the user in my application, but more importantly, why. The three user flows I found to impact the health of users’ plants the most were determined by my primary research and how might we statements. They include:

1. Troubleshooting or diagnosing a sick plant

2. Creating a personalized care plan for a specific plant

3. Learning more about one of your existing plants

I found myself making more edits to ensure the usability of the app remained intuitive and solved the users' issues.

• For example, one idea that arose after mapping out my user flows was adding buttons that would help tie each flow together. I ended up adding an “add plant” button on the results page allows the user to immediately add their sick plant to their library instead of having to do it manually from the “My Plants” page.

Sketches

The real magic began when I started bringing my ideas to life. By utilizing the Carazy 8’s technique and concepts from other applications I’ve used, I was able to draw out streamlined sketches for my 3 user flows. I began by drawing out 8 simple ideas in under one minute to see what ideas quickly came to mind.

I also kept in mind my “How Might We” statements and my user stories to make sure I was focusing on the key functions required to solve the users' problems. 

Techniques

To provide an enjoyable way for users to keep track of their plant-care schedule I’ve added a weekly calendar and checklist on the home page that includes the users’ most important tasks. 

To provide users with the correct plant-care information I’ve added 3 bullet points of information on each plant’s page.

To allow users to differentiate each of their plants’ care plans I’ve added a customization screen that will automatically calculate how often they need to water their plants.

Wireframes

The next step in my design process included drafting out low-fidelity wireframes that included basic layouts to quickly visualize the flow of my project and highlight any usability issues early on in the design process. 

This allowed me to then create medium-fidelity wireframes with more details and refinements before adding color and images. Here, the focus was still on making sure each of my content placeholders was vital to solving the users’ problem.

Throughout each stage of my wireframing process, I uncovered more areas for improvement. Specifically, I noticed how important my spacing was and how text hierarchy can play a special role in calling attention to the users.

Moodboard

Throughout the design process, I came across countless examples and pieces of inspiration that I wanted to apply to my project. Using a mood board I was able to narrow down which features I wanted to prioritize in my design to make it feel energized and organized. 

I opted for a design that included rounded corners, bold headings, and minimal drop shadows. Using plant photos with white backgrounds helped give the app an organized feel. 

Style Guide

Hi FIdelity UI’s

Testing

My style guide consists of the colors, fonts, and icons I wanted to use to maintain consistency throughout my application. By choosing the Playfair font I’m instilling a sense of knowledge, considering this project is named Plantopedia to resemble an encyclopedia of plants.

For my color choices, I wanted to use a bright fuchsia that would compliment the natural color of the plants and stand out from the competing apps on the market that mainly use shades of green. Fuchsia is known for representing a strong and bold visual identity. To help balance this bright pink I’ve also introduced some softer pinks and greens into the mix.

The final stage of my design refinement before moving on to prototyping and development included drafting out my hi-fi wireframes. These screens included more accurate content, details, and visual styling to further instill a sense of branding across the app to get it as close to the finished product as possible. 

Having a highly realistic representation of my final product was crucial before presenting it to users to obtain feedback. The more realistic my wireframes were, the better the feedback on specific interactions would be. 

This exercise was one of my favorites because I got to pull ideas straight from my style guide, almost as if it were a master plan for the entire application. I found myself making minor adjustments to my style guide along the process to reflect changes made that better suit the mobile screens. After many iterations, I landed on the following designs.

Prototype

At last, it came time to animate my designs by using the prototype function within Figma.

I animated my user flows determined earlier in my project to get an idea of my screens’ overall flow and usability. This process allowed me to see what it would look like on a life-size phone screen and prompted me to make changes that improved consistency and usability.

Usability Testing

Usability testing was conducted to evaluate the usability and effectiveness of the application using a prototype to uncover any obstacles the user faced. I first began by animating my Plantopedia prototype within Figma. Then, I recruited and scheduled 5 users to complete 3 tasks to evaluate overall usability. 

Users were recruited using hobby groups, social media, and word of mouth from people in my network. Requirements of my participants included people who were willing to use houseplant tracking applications, who have used houseplant tracking applications in the past, or who have houseplants that they’d like assistance with. 2 users completed an in-person moderated test and 3 users completed a virtual moderated test via Zoom.

I asked participants to complete the following tasks:

1. Diagnosing a sick houseplant

2. Updating the care plan for a plant after repotting it

3. Finding more details about an existing plant

Results

Once receiving my usability testing feedback I immediately wanted to fix every problem, but I knew I needed to utilize my time wisely.

Utilizing my priority chart I narrowed down the 3 most important fixes that impacted the users' overall ability to solve their problems. I enjoyed this point of my project because I was able to create solutions to the problems identified by firsthand users.

Redesigns

Issue 1: Interactive Elements

When selecting photos of a plant to identify and diagnose, users were unclear on how to select the correct plant on the Confirm Plant page. Users attempted to click on the photo itself instead of scrolling down to the Confirm button.

• A solution to this problem could include adding a thicker stroke around the selected plant photo itself and adding a “rediagnose” button on the Confirm Plant page.

Issue 2: Navigation Difficulty

The inline “Edit Plant Care Plan” button on the Specific Plant page was confusing to the user and didn’t draw enough attention. It was only after the user scrolled to the bottom and then back up that they found the small inline button.

• Grouping the editable care plan items on the Specific Plant page and placing them in an accordion menu underneath the general plant care details would cause less confusion. Renaming this section to “calculate your care plan” would be more intuitive.

Reflection

This project has allowed me to create something I’m truly passionate about by combining my passion for organization and horticulture. I was able to discover a whole new world quite literally at my “fingertips” and spent hours playing with different screen layout possibilities simply because it brought me joy. Throughout this project, I’ve learned:

• The first iteration will not be the last, and that’s okay! In the beginning, I was set on creating screens that were perfect on the first go-around, but I quickly learned that improvements can always be made. My project still has some minor tweaks that could be made, but I learned how to prioritize the issues that affected the users' ability to achieve their goals. 

• Each user has differing priorities. Instead of developing a project based on my own needs, or one specific user’s needs, I included features that would help a group of houseplant owners. By tailoring the app to benefit a wide variety of users I uncovered areas of improvement including adding a “share info” button and an “upload photos” button to allow users to customize their plants’ homepage.

With more user testing and experience with UX/UI design, I believe I could improve this application even more. Some ideas I have include:

• Smart Problem Solving: The ability to troubleshoot houseplant problems based on the user’s previous experiences that were tracked inside the application.

• Gamification: Adding a celebratory animation when users complete a task to provide them an overall sense of enjoyment would encourage them to return to the application and therefore keep their plants alive.

Thank you for your time!