Apps for the field, not the demo.

Every design instinct that works for an urban consumer app is wrong in a field. Dense text fails. Subtle iconography fails. Clever navigation fails. I design agritech that works outdoors, on a cheap phone, for someone whose decision this week affects a season's income.

Start a project

DesignBuildGrowScale

One continuous process. One partner.

Not four services — four stages of the same product.

01 — Work

What's shipped

Live products in this sector — verifiable from the store listing or the product itself.

Mobile AppsAgricultureLive

An agritech app putting crop guidance, soil health, weather, inputs and expert consultation in the hands of Indian farmers.

50K+ downloads · 4.0★ from 398 reviews on Google Play

02 — The domain

What field software demands.

The constraints that don't show up in a generic design brief, and decide whether the product works in the field.

  • 01Icon-led, thumb-sized. Entry points sized for a thumb and readable at arm's length in bright light. Text menus and subtle icons don't survive the context.
  • 02Visibly local, visibly current. Advisories tagged with district and date, so guidance reads as specific to here and now rather than generic. Trust is built on relevance.
  • 03A photo instead of a sentence. The ask-an-expert flow accepts an image, because a photograph of a diseased leaf is easier to send than a description of one.
  • 04Prices in the open. For an input catalogue, the fastest way to be trusted is to be the one place that doesn't hide the price.
  • 05Low-bandwidth by default. Metered data, intermittent signal. The app has to be useful before everything loads, and honest about what needs a connection.

03 — How I'd help

The engagement

An industry frames the work; the engagement is one of these.

Compare engagement models

04 — Questions

Common questions

Multi-language and low-literacy support?
Yes — a core constraint, not an add-on. Icon-led navigation, minimal text, and layouts that survive translation into longer or right-to-left scripts.
Farmer-facing only, or agri-business tools too?
Farmer-facing is the portfolio — Farmology, 50K+ downloads. Agronomist, FPO and supply-chain tools are in scope with a related but different set of constraints.
Do you design the store listing?
Yes — screenshots and feature graphic included. For this audience the listing is often the first and hardest trust test.
Can you build it?
React Native and web front-ends, yes. A fully native build I'd design for and hand to your engineers.