Skip to content

Farm Fly

Drone spraying and crop monitoring booked from a phone, in the farmer’s own language, in a few taps.

View the live product
Client
Farm Fly
Industry
AgriTech
Year
2026
Platforms
Android
Our role
Product design, mobile engineering, store release

01 — Context

Where this started.

Agricultural drone services in India are typically arranged by phone call and word of mouth. That works until demand grows, at which point the operator loses track of bookings and the farmer has no way to confirm anything.

02 — Challenge

The hard part.

The audience is the constraint. This app is used standing in a field, on a mid-range phone, by someone whose first language is not English and who has no reason to tolerate a confusing interface. Any complexity in the booking flow is a lost booking.

03 — Strategy

What we decided.

We reduced the product to one job — book a service for a specific field and know where the booking stands. Crop type, service type and land area are the only inputs, and local language support was treated as a launch requirement rather than a later addition.

Product screens

Farm Fly interface, screen 1
Farm Fly interface, screen 2
Farm Fly interface, screen 3
Farm Fly interface, screen 4
Farm Fly interface, screen 5
Farm Fly interface, screen 6
Farm Fly interface, screen 7
Farm Fly interface, screen 8

04 — Experience

How it works for the person using it.

The booking flow is short and linear, with crop selection presented as recognisable choices rather than a text field. Booking and service status are visible from the home screen so a farmer never has to phone to ask whether the drone is coming.

05 — Engineering

How it is built.

A Flutter application covering the mid-range Android devices that dominate rural India, with localisation built into the interface layer from the start so additional languages are configuration rather than rework.

  • Flutter
  • Firebase
  • Google Play

06 — Feature stories

The decisions that mattered.

  1. Crop-aware booking

    Paddy, maize, cotton and other crops are selected directly, so the service request carries the context the operator needs without the farmer filling in a form.

  2. Local-language interface

    Shipped as a launch requirement, not a roadmap item. The app is unusable to most of its audience without it.

  3. Visible booking status

    Bookings and service state are surfaced on the home screen, removing the phone call that would otherwise be needed to confirm anything.

07 — Results

What we can prove.

4.9★
Play Store rating

Source: Google Play listing

3+
Crop types supported at launch

Source: Play listing — paddy, maize, cotton

Live
Shipped on Google Play

Source: Google Play listing

Only verifiable figures appear here. We do not publish uplift percentages or revenue claims we cannot evidence, and we do not restate a client's internal numbers as our own.

08 — Ownership

What was handed over.

At launch, everything below transferred to Farm Fly. Nothing in this product depends on DevXAI to keep running.

  • Full Git repository with commit history
  • Infrastructure and store accounts in the client’s own name
  • Architecture and deployment documentation
  • Walkthrough session with the client’s team
  • 30-day post-launch defect warranty

Build something similar

Have a problem shaped like this one?

Send us the brief. You get a discovery call and a written fixed-price proposal within 24 hours — with the same ownership terms Farm Fly got.

Response
Fixed-price proposal within 24 hours
Confidentiality
Mutual NDA signed before any project detail is discussed

Prefer to just talk? WhatsApp is answered fastest during studio hours.