- Tina Greist
Great question:
How would you design a gardening app?
| Users | TAM | Freq |
| Beginners | H | H |
| Ocassional hobbiests | M | S |
| Experts | H | M |
| Users: | Painpoints |
| Beginners | Don’t know what to grow/plant in their gardens |
| Ocassional hobbiests | Don’t always have time to take care of a garden |
| Experts | Need tools to refine their processes |
I’m going to choose Beginners there is a large addressable market & they may need the most help & guidance which results in frequent use of the application. This in turn can later allow us for ways to monetize with a users.
User Journey
What to plant -> Care for plant -> Sow Rewards
Knowing what to plant is the bigest painpoint in getting started with a garden, especially for beginners.
Potential solutions for beginners
| Solutions | Impact | Freq (because we are looking to increase the # of gardens) |
| Edu app that helps users understand the process and care for different types of plants | H | H |
| Reminder application that lets users know they should water/repot plant/fruit | H | M |
| App that tracks history of their garden | M | M |
So we’re designing an app targeted at beginners looking to understand which plants would be good for their garden depending on their lifestyle.
We’re focusing on the inital pain point of starting the garden
We know the edu content is helpful by users
Metrics:
WAU – Weekly Active Users; “Active” are users who have added ‘seeds’ (garden creation) to their garden, as this is a mobile app we are allowing users to understand what to plant. When they add seed’s we can tell that our information was helpful. This is more of a weekly tasks because gardening takes time.
a garden lifecycle (their garden can be in different stages -> seed, growing, bloom, death )
Support metrics:
# of plants within plant library
# of new gardens created
time spent on app
# of unique users
retention rate
Counter metrics:
churn rate
# support tickets
# of bad reviews

Google
Meta
Adobe