Back to home
CRCLR Recipes Creating a simple, user-friendly interface for a complex tool that allows farmers to set specific environmental conditions for any plant they’re growing, including temperature, air speed and unique light spectrums
Highlights
Recipe builder
Recipe setpoint builder

The editing page allows users to control over 15 environmental conditions over time. Parameters can be set with number inputs or visually through the graphed interface.

Setpoint pop ups

The variables can be more precisely controlled with the pop setpoint pop ups. Users can set time and values directly or move to advanced settings to change the line type or acceptable ranges.

Timelines

Timelines can be created to break the grow duration up into stages. Adding time to the recipes allows users to create environments that match a growing plants changing needs.

Visual Cues

Helpful visuals guide users towards physically feasible expectations to prevent any impossible recipes from being pushed to production.

The editing page allows users to control over 15 environmental conditions over time. Parameters can be set with number inputs or visually through the graphed interface

The variables can be more precisely controlled with the pop setpoint pop ups. Users can set time and values directly or move to advanced settings to change the line type or acceptable ranges.

Timelines can be created to break the grow duration up into stages. Adding time to the recipes allows users to create environments that match a growing plants changing needs.

Helpful visuals guide users towards physically feasible expectations to prevent any impossible recipes from being pushed to production.

Background
What is the CRCLR system?

The CRCLR system is a series of movable racks, a nutrient distribution system and a software that allows users to manage indoor farms. These farms operate year round controlling all possible environmental variables such as temperature, nutrients, humidity, light levels & more.

Branding: Simple yet powerful

CRCLR as a brand aims to offer capable hardware & software packaged in a very sleek & easy to understand package. Important functions are always easily accessible with more niche specialized options hidden for users willing to dig.

Problem
How do we use recipes to grow plants?

A recipe is really just a series of directions for the racks to follow. At any given moment the racks are given variables like temperature or air speed, and adjust physical devices to reflect those inputs.

Organizing the Variables

A recipe is what allows a user to control environmental variables within their farming units. Up to 15 unique variables can be controlled.

All Variables
Organized variables
Water Temp
EC
pH
ORP
Spray Rate
Leaf Temp
Air Temp
VPD
Relative Humidity
Air Speed
CO2
Green Light
Red Light
Blue Light
Far Red Light
CLI
PPFD
Planning
Who will be using this?

There are two main users the will find value from manipulating recipes, growers and plant scientists. Growers will be tweaking, reading and running the recipes while growing out their crops while plant scientists will be pushing the boundaries of the recipe's capabilities to yield new growing insights.

Farmers
- Minimal experience with plant science basics
- Decent understanding of the plants needs over time
- Managing multiple grows
Plant Scientists
- Extensive experience with plant science basics
- Decent understanding of the plants needs over time
- Working out of a test unit
Managing grows over time
Splitting a grow into stages
Stages of a grow's life can be split up into groups depending on the plant type. For example plants can have seedling, leaf growth or fruiting stages.
Splitting a stage into 24 hour cycles
The larger cycles can last over a week. These larger cycles can be broken down into a number of days they last.
Splitting a 24 hours into day & night cycles
Plant's needs can even span single days so we split the days into day & night cycles. For example a plant might need brighter lights during a day & no lights during the night cycle.
How do we use recipes to grow plants?
On/Off concept
First design concepts were based around the idea of setting all setpoints at a single instance on a timeline. This worked well for inital R & D testing but proved clunky when building recipes made to actually grow plants.
Graphed data
The preferred design included graphing the data over a repeating time frame. These cycles of either 12 or 24 hour periods let users create a day & night mode that ramps down quickly and easily.
Design
Managing setpoints through a graphed interface

The setpoints page is the main location for managing the variables a recipe runs through during a grow. The setpoints can be managed in the legend to the left while the timeline is displayed visually below. Within the graph, dots called "set points" can be added to lines and either dragged into place or manipulated through the setpoint popups.

Values
The regular pop up allows users to manage the time & value
Advanced
The advanced tab allows users to manipulate the line type & range if applicable
Initial setpoint
Initial setpoints have manipulatable values but no time or delete function
Lighting setpoint

Lighting is a bit different compared to the other variables. Lighting spectrums all affect one another meaning increasing one may change the max limit of another. The sliders are able to be locked therefore limiting th maxes of the other spectrums.

Building out a recipe timeline

In the timeline tab, users can create their recipe timeline by adding named stages of growth & subcycles. These stages all have controlled cycle lengths & amount of cycles allowing unlimited levels of precision timing down to the hour is necessary.

Results
How did users respond to using the tool?
Too confusing

When explaining the operation of recipe creation, the first response was that the growers were overwhelmed. Any steps to simplify the process were welcomed.

how do I add unique tasks

For certain tasks, unique tasks like pruning or cutting flowers could exist. Users requested a way to add these tasks to their lists when creating a recipe.

Notes & Tips

Users often shared recipes and the one they were using might not have been created by them. There were requests for a place to include instructions alongside tasks or steps for clarity.

Improvements
What did we change
Switch from pause to Observation mode
Observation mode, formerly known as “pause mode” was also changed to being indefinite. The timers count up and change colour to indicate severity if the mode lasts beyond an hour.
More visible timers
Timers were changed to being indefinite and shown as counting up. The chips appearing on the left make them more noticeable to prevent farmers from forgetting them.
Pausing individual widgets
Resuming from observation mode was rarely used in practice. So we moved the resume buttons down into the individual widgets.
Responsiveness
How do I access these features on smaller devices
Results
How did users respond to using the tool?
95%
Positive Farmer Feedback
Positive Farmer Feedback
During demo's and test runs, we received overwhelming positive feedback from farmers. 95% of test users followed up with interest in exploring investing in the CRCLR system.
300%
Increase in recipe creation
Increase in recipe creation
After pushing the newer recipe changes, we say a dramatic increase in recipe creation from our farmers. This indicated a clear improvement in recipe creation understanding, as well as new interest in the system.
And my favourite stat:
a 100% reduction in messages like this:
HighlightsBackgroundProblemPlanningDesignFeedbackImprovementsMobileResults
Case study
Managing issues & events within a zone
2025 - All rights reserved
Drew Robinson