FruitScope on laptop, tablet, and phone: block view with a scanned apple orchard map, crop type selection, and mobile scan stats

Orchard AI

design engineering fruit vision tools at Orchard Robotics

timeline
[dates] 2026
role
design engineer intern
team
[team]
skills
design engineering · ui/ux

Overview

I work across the design-code boundary on the tools that turn orchard-scale fruit scans into decisions growers can act on.

Design / Product

  • [The interface work: which screens or flows, for whom]
  • [The component or token-system work at the code boundary]
  • [The field-conditions constraint that shaped the design]

Execution

  • [What shipped, and where it runs]
  • [The number: fewer clicks, faster scans, support tickets]
  • [The collaboration: eng, field team, growers]
photo soon
photo soon
photo soon
photo soon
photo soon
photo soon

The problem

[The user and the number: who was struggling with the current tooling, and what it cost them. The conditions the interfaces get used in — sun, gloves, truck cabs.]

Process

[The smallest honest version: what was tried, the rejected direction and why. Artifacts over adjectives.]

media soon

What shipped

[Demo or screens first, then details.]

media soon

Outcomes

[Numbers, even small ones. If unmeasured, what Grace would measure.]