AGROPLANT · 2026 / PRODUCT DESIGN · MOBILE PRODUCT
AGROPlant turns agricultural field assessments that previously depended on fragmented forms, calculations and manual reporting into a structured mobile workflow.
The product was designed around real field conditions, technical measurements, reporting requirements and unreliable connectivity — allowing assessments to remain useful even when a stable internet connection is unavailable.
ROLE
Product Designer & Product Builder
RESPONSIBILITIES
Product Strategy · Product Management · Information Architecture · UX/UI · Prototyping · Implementation
PLATFORM
Mobile / iOS
TECHNOLOGY
React Native · Expo · Supabase
STATUS
In active development and field validation
01 / THE PROBLEM
Field assessments were generating data, but the workflow around them was fragmented.
Agricultural consultants perform technical evaluations directly in the field, collecting measurements, observations, photos and machine information that later need to become understandable technical reports.
The challenge was not simply turning a calculation into an app. The product needed to support the complete workflow: field work, technical measurement, assessment, results, report and history.
FIELD WORK
TECHNICAL MEASUREMENT
ASSESSMENT
RESULTS
REPORT
HISTORY
02 / PRODUCT EVOLUTION
What started as a field calculation became a broader assessment product.
The initial opportunity was to make recurring agricultural calculations faster and more reliable in the field. As the product evolved, the workflow expanded to support different kinds of technical assessments, structured data capture, photos, report generation, editing and historical records.
SEEDS
Distribution measurements · Acceptable / Double / Failure · Point-based results · Technical reporting
FERTILIZERS
Application measurements · Dosage and tolerance · Field collections · Technical reporting
EQUIPMENT / DAP
Machine assessment · Structural checks · Technical status · Recommendations
03 / CORE CONSTRAINT
Agricultural assessments can happen in locations where network connectivity is unstable or unavailable. That meant core assessment workflows needed to remain usable without depending on a constant internet connection.
OFFLINE-FIRST WHERE THE WORK REQUIRES IT.
FIELD
LOCAL ASSESSMENT
SAVE
CONNECTIVITY AVAILABLE
SYNC
CENTRALIZED DATA
04 / INFORMATION ARCHITECTURE
Different assessments needed different workflows without becoming different products.
Seed distribution, fertilizer application and equipment diagnostics involve different measurements, calculations and technical outputs. The challenge was creating enough specialization for each workflow while maintaining a coherent product structure.
SEEDS
FERTILIZERS
DAP / EQUIPMENT
Specialized workflows, one coherent product structure.
05 / FIELD EXPERIENCE
Data entry needed to immediately become technical feedback.
The consultant should not need to collect information first and interpret everything somewhere else later. Measurements are structured so the product can transform field inputs into understandable results during the assessment.
FIELD MEASUREMENTS
CALCULATED RESULTS
STATUS FEEDBACK
MEASUREMENTS · RESULTS · STATUS
Field inputs become understandable feedback during the assessment.
06 / REPORTING
The assessment doesn’t end when the last field is filled.
Technical information collected in the field ultimately needs to become a document that can be reviewed, shared and revisited. Report generation therefore became part of the core product experience rather than a separate administrative task.
ASSESSMENT
Field information is captured and reviewed.
STRUCTURED DATA
Measurements and decisions are organized.
TECHNICAL REPORT
Replace with a real report visual
SHARE / HISTORY
07 / ITERATION
The product evolved through repeated field and stakeholder feedback.
The product went through multiple iterations involving workflows, terminology, calculations, report structure, navigation, photos, synchronization and technical information. Instead of treating the first interface as final, product decisions continued to change as the workflow was tested against real consulting needs.
BUILD
TEST
FIELD FEEDBACK
ADJUST
TEST AGAIN
08 / PRODUCT STATE
Saving, syncing, editing and reporting needed to feel like one continuous workflow.
Field products have more states than simply complete or incomplete. The experience needed to communicate whether assessments were still being worked on, saved locally, synchronized, available in history or reopened for editing.
IN PROGRESS · SAVED · SYNCED
FIELD WORKFLOW
Assessments move through operational states as work continues.
REPORT AVAILABLE · EDIT / NEW VERSION
PRODUCT RECORD
The current state remains visible beyond the field session.
STATE CONTINUITY
09 / DELIVERY
My responsibility didn’t stop at the design handoff.
I worked across product definition, UX/UI and implementation, which allowed design decisions to be evaluated against the technical reality of the product.
REACT NATIVE · EXPO · SUPABASE · GITHUB
DESIGN FIRST. IMPLEMENTATION-AWARE THROUGHOUT.
10 / SYSTEM THINKING
The interface, data and report needed to describe the same assessment.
As the product became more complex, consistency between what consultants entered, what the application calculated, what was stored and what appeared in reports became an important product-design constraint.
FIELD REALITY
USER INPUT
PRODUCT LOGIC
STRUCTURED DATA
FIELD REALITY → USER INPUT → PRODUCT LOGIC → STRUCTURED DATA → TECHNICAL REPORT
11 / CURRENT OUTCOME
AGROPlant evolved into a mobile product supporting multiple agricultural assessment workflows, technical reporting and field data management. The product has gone through repeated stakeholder validation and continues to evolve as new operational requirements are tested.
12 / WHAT I LEARNED
Building for the field changed how I think about product constraints.
A workflow can look simple when viewed from a desk and become completely different once connectivity, technical measurements, reporting, equipment variation and real field conditions are introduced. Working across design and implementation helped me understand those constraints as parts of the same product problem rather than separate design and engineering concerns.
NEXT PROJECT
G12 AGRO
Designing a centralized field operations platform for agricultural consulting teams.
LET’S WORK TOGETHER
Have a complex product problem to untangle?
I’m open to Product Design opportunities and selected projects worldwide.