Brew - Cannabis Growing Tool

Summary

Brew is a client project designed to help growers manage and automate their cultivation processes through an application.

The project challenged me beyond visual design. It expanded my technical understanding of backend processes, automation logic, and IoT systems.

view live prototype

made with lovable.
This prototype does not represent the final product.

Problem

How do you design an experience that simplifies the complexity of cultivation?

User Overview

The target user ranges from first-time growers to experienced cultivators with the shared desire to optimize their grow experience. They are motivated by the process and driven by the satisfaction of a successful harvest.

User Pain Point

The grow process requires consistent attention and care. Responsibilities like scheduling, cleaning and monitoring can feel overwhelming.

The Challenges

There were two core challenges during this project.

Designing Within an Unfamiliar Technical Domain

The product relied on IoT systems, automation, and real-time data. This was an area outside my design expertise. I worked closely with the developers to understand the process, using that knowledge to make informed design decisions.

Aligning UI Decisions with Backend Logic

The interface needed to accurately reflect the complex backend system while staying user-friendly and intuitive.

Competition Analysis

Hampa

Growing cannabis tool app. It supports the user from seed to harvest.

Hey abby

A growing cannabis tool app and automated grow box. It provides grow support and community features.

Budlabs

A hydroponics grow guide app. It provides a nutrient calendar and feeding schedule.

Shrooly

A smart growing mushroom tool app and grow pod. It provides support and guidance to cultivate mushrooms.

Understanding Smart Ecosystems (IoT Learning)

This project provided hands-on learning to how smart ecosystems operate in order to accurately reflect functionality and data.

Devices communicate via Wi-Fi, requiring a guided setup process to get users connected.
Each device needed distinct feedback states: online, offline, disconnected and unavailable.
Working with developers was essential to understading how logic is processed in the backend and how that needed to be in the UI.
Edge cases were mapped out including, system failures and troubleshooting scenarios alongside system states such as scheduled, active, planned and failed.
Tutorialization and clear UI feedback were built into the experience to communicate actions, data and system limitations without confusing the user.

Explorative & Iterative Design Process

The explorative nature of the project became an opportunity for strong collaboration, a refined process and strengthened decision-making.

Early concepts explored multiple features and journeys to define the product's direction.
Designs were frequently revisited as technical constraints and backend limitations surfaced throughout the process.
Features were refined, reworked or descoped to prioritize feasibility and clarity.
Adjusted flows and interactions based on developer feedback and technical discoveries.
Each design improved alignment between user needs, system capabilities, product goals and simplified user interfaces and flows.

Learnings

This project challenged my skills and improved my capabilities as a designer.

Gained a more informed perspective on backend processes and developers thinking, making me a more technically aware designer.
Improved my ability to translate technical and abstract concepts into clear and feasibile products.
Developed more intentional design-thinking and decision making with developer processes in mind.
Strengthened product design skills focusing on user value, practicality and excecution.
Built greater problem solving skills and my ability to pivot and adapt to new workflows.

Reflection

This project helped me understand systems, developers perspectives and smart ecosystems. It challenged me to learn on the fly, adapt quickly and apply them to practical solutions. I've gained product design skills with a greater understanding of what to prioritize and when to descope. It is important to balance user goals and client goals with feasibility and execution to ensure project success.

view live prototype

made with lovable.
This prototype does not represent the final product.

2026 Update

UI improvements were made directly in Lovable, refining the visual design and overall experience.

see more updates

Established Visual Language

Colour-coded chips to differentiate between growth phases. Phase imagery was also added to give users a clearer understanding of each stage.

Improved Prototype Logic

The prototype was updated to better reflect how the actual product would work. Users can now add and edit elements such as tents, plants and devices.