Farm Dash  •  Farm Dash  •  Farm Dash


Vegetables—we all hated them as kids. But this isn’t your mom’s recipe, or dashboard. I'm talking veggies grown indoors, without soil. Seem futuristic? Well, the future is here with FarmDash, a SaaS application I worked on. I tackled UX challenges to streamline efficiency, adding my own dash of innovation to the farm-to-table journey.
3 people icon
Client: Farm Dash
3 rectangular shapes
Project Type: Web App
1 person with 4 curved lines surrounding
My Role: UX, UI
Web application dashboard


Reframing a key farming task
FarmDash, a tool designed for soilless cultivation of herbs, fruits, and vegetables, faced a significant hurdle with its reliance on multiple, disjointed interfaces for simple tasks. This required users to frequently switch platforms, complicating their workflow. My contribution was to refine the overall experience, particularly within the ‘Batches’ section of the app. Knowing your time is valuable, I’ll get straight to the impactful outcomes...
Basil leaf
Man inspecting indoor farming produce
Streamlined User Journey
I streamlined the user journey across multiple tasks, creating an intuitive workflow that feels like a single, unified platform.
Consistency in Interaction
I also established consistent interaction patterns throughout the app, reducing the learning curve and enabling users to perform tasks with greater confidence and speed.
User Satisfaction Enhancement
A revamped interface and streamlined process flow are anticipated to significantly boost user satisfaction, as evidenced by positive feedback upon completion.


Unpacking the solution
Focusing on the key process of batches, which allows farms to categorize groups of crops, I recognized the diverse roles involved in running an indoor farm, from supervisors to farmhands. I restructured the UX to make content access intuitive for farmhands, simplifying their day-to-day work. The interface layout is as follows:
UX design for web app
1. Main Navigation
Farmhands can track inventory, consumables, sales, and much more within the app. I identified and made accessible the primary items they typically need.
2. Secondary Navigation
This navigation allows users to be more precise in their tasks. With the Tasks tab active, users can see and perform specific actions on a set of crops, a.k.a. a batch.
3. Batch Phases
I outlined the steps a batch must go through as it matures, enabling farmhands to assess and perform necessary tasks to harvest a crop at the right time.
Modal window
Detail: Farmhands print tickets from batches to affix to physical crops.
Dashboard for indoor farming
Detail: Viewing a batch’s details shows every logged action it has undergone.


The batch screen defaults to displaying tasks that need attention. It was important to enable farmhands to add additional information as they complete tasks on a batch, especially if a crop’s recipe needs modification. Comments are later reviewed by recipe scientists who adjust the algorithm for each batch task accordingly.
Business-facing web application

Task completion, and more

A farmhand’s objective here is to successfully progress each batch to the next phase of its lifecycle. There’s an area for the farmhand to add additional information, such as the location on the farm where a crop has been moved to, in addition to marking a task as done, by tapping the circle—a large hit area makes this more convenient as a farmhand is likely using a tablet out in the field while they perform tasks.
Web application design


Person using tablet with pumpkin seeds on table
Batches are predicated on a set of rules that have been designated via the Batch Recommender—housed inside the ellipses menu. Below is where batches are actually confirmed.
Creating a batch initiates its physical existence on the farm, a routine task. And although it was an infrequent use case, we still needed a way to enable farmhands to create one from absolute scratch. I achieved this by adding a button in the bottom right corner, taking a cue from Material Design’s floating action button.
Web application
Detail: Clicking Create Batch confirms the batch’s physical existence on the farm.

Minimizing operational monotony

The Batch Recommender is an easy way for farms to create batches that they regularly grow. So that the farmhand has an immediate understanding of what to do when they hit this screen, I included a prominent interaction prompting them to add their first batch recommendation.

Recommendations are based on a recipe, which is why creating a batch from absolute scratch isn’t likely. On this screen, a farmhand can search for a recipe by entering its name. Then, they select the pertinent batch details like version number, multiple (quantity), and recommendation frequency. I also included a large toggle to disable a recommendation temporarily.
Detailed blackberry fruit
Dashboard for indoor farming

maximizing capacity oversight

Since a farm has many batches growing in tandem, it was important to enable viewing and filtering by multiple criteria and seeing what stage a particular batch was in. I designed multiple interfaces, charts, and interactions to solve for this. Paying close attention to requirements, content, and hierarchy, I designed the charts to display the right details and information based on a farm’s overall production.
Farms with lower production can see larger charts, while higher-volume farms favor compact views. Find-as-you-type filtering helps farmhands narrow down exactly what they’re looking for. Beyond this, there's a screen for viewing farm capacity visually, integrating what was once a fragmented array of third-party platforms. Together, these UX considerations help farmhands easily see relevant and specific batch details.
UX design for web app
Various pie charts in an application
Detail: A compact view enables farms with many batches faster oversight of crop statuses.
Web app showing graph of usage
Detail: Housed inside the ellipses menu, a farm’s equipment usage is visually represented.

High fidelity design

The main focus of my involvement with FarmDash was to assess the user experience and provide a number of prototypes.
That said, I thought it was important that a component of the deliverables include higher fidelity design of at least one section. While this isn’t the main dashboard that a farmhand sees when they first log in, it’s a reasonable demonstration of the overall style and direction.
Web application dashboard


Case Study

Up Next