Article6 min readUpdated
Agritech App Design for Farmers: Icons, Voice, Offline
Agritech app design for farmers new to apps: icons with labels, local language, voice, large targets and offline use. A practical guide with examples.
By Tithi Mondal, UI/UX Designer
The farmer is not a "user" yet
Imagine a farmer near Bardhaman who owns a phone, uses WhatsApp for voice notes and watches videos. He has never installed a farming app. He studied up to Class 8. His hands are often wet or dirty. His network drops in the field. His phone is a low priced Android with little storage.
This is the real person behind agritech app design. He is not slow or unwilling. The app is simply not built for his situation. A farmer app UI that works for him must treat the first use as the hardest moment. If he cannot finish one task in the first two minutes, he will delete the app.
I worked on Agrim, an agritech product. The biggest lesson was to stop designing from my own habits and to start from how the farmer actually uses a phone.
Who uses a farmer app
- The smallholder farmer with low screen literacy who prefers voice and pictures.
- The younger family member who helps the elder with the phone.
- The village level agent or dealer who uses the app for many farmers.
- The farmer who is comfortable with WhatsApp and learns new patterns by copying them.
Each person needs a different level of help. A simple rural app design assumes the least confident person and still lets the confident person move fast. Learn how people in your target region actually use phones. My guide to user research for startups shows how to do it with a small budget.
The five principles for an app for low literacy users
1. Icons always come with labels
An icon alone is a guess. A picture of a sack may mean seeds to one person and fertiliser to another. Always put a short word under each icon, in the user's language. Use pictures of real things, such as a real tractor, a real sack, a real tomato, and not abstract symbols. If you need custom icons, a designer can draw a consistent set. See my icon and illustration design service.
2. Use the local language fully
Do not translate only the buttons and leave the rest in English. Translate the labels, errors, prices and messages. Use words people say in the village, not formal textbook words. For Bengali, test the type on a cheap phone, because some fonts break on low end devices. Read my notes on regional language app design.
3. Add voice
A voice and icon based interface lets the farmer listen and speak. Put a speaker button next to each important instruction. Tapping it reads the text aloud in the local language. A microphone button lets the farmer ask a question or search by speaking. Voice recognition is not perfect for regional accents, so always show what the app heard and let the farmer correct it.
4. Large targets and one task per screen
Make buttons at least the size of a thumb, with space between them. A farmer with rough or wet hands will miss small targets. Show one question or one choice on each screen. Avoid long forms. Avoid tabs, hidden menus and gestures such as swipe to delete. Show the main action as one big button at the bottom.
5. Work offline
Network is weak in many fields. Let the app load the last saved data, record entries without network and send them when the signal returns. Show a clear status: "Saved on your phone. Will send when network comes." Read designing for low end phones and slow networks for the technical habits that help.
The screens that matter most
For a typical agritech app that helps farmers buy inputs, learn and sell, six screens carry the weight.
- Language choice. The very first screen. Show each language in its own script as a large button. Remember the choice.
- Home with 4 to 6 big tiles. Each tile has an icon, a label and a voice button. Examples: My crops, Prices, Buy inputs, Ask an expert, Weather, My orders.
- Crop or field screen. Show the crop name, the stage and the next action as a plain sentence: "Water the field tomorrow".
- Price or market screen. Show the crop name, today's price and the place. Use a clear up or down arrow with words, not colour alone.
- Order or request screen. One item at a time, quantity with plus and minus buttons, price in rupees and a confirm button.
- Help screen. A big button to call or send a voice note to a real person.
The first use flow, step by step
The onboarding flow decides whether the farmer stays. Keep it short and forgiving.
- Choose the language. One tap.
- Enter the mobile number. Use a large number pad. Offer to read it back by voice.
- Verify with OTP. An OTP is a one time code sent by SMS. Fill it automatically if the phone allows. Also allow a resend after 30 seconds.
- Choose the crops. Show pictures of common crops with names. Allow many choices.
- Allow location only if needed. Explain in one sentence why: "To show prices and weather near you". Make the app usable if the farmer says no.
- Do the first task together. Show a guided first action, such as checking today's price, with a voice guide.
My article on app onboarding UX best practices adds more ideas for the first minutes.
Test with real farmers, not with your team
The only way to know that a screen works is to watch a farmer use it. Visit a village or a farmer group with a phone loaded with the prototype. Give one task: "Find today's tomato price". Do not explain. Watch where the hand hesitates. Note the words the farmer uses for each thing and use those words. Write down every place where the farmer pauses. Ask the younger family member to join, because they often become the guide for the elder.
Trust also matters. Farmers have seen many false offers. Show the real name of the company, a real phone number and a clear statement of what the app charges. If there is a fee, show it before the order, not after.
Mistakes in agritech and rural app design
| Mistake | What to do instead |
|---|---|
| Icons without labels | Add a short local language label under each icon |
| Only a translated menu, rest in English | Translate every message, error and price |
| Small buttons close together | Use large buttons with space between them |
| Long registration forms | Ask for the mobile number and language only at first |
| App stops without network | Save data on the phone and sync later |
| Colour alone to show good or bad | Add words and arrows |
| Designing from a city office only | Test with farmers in a real field setting |
| Hidden fees found at the last step | Show the full cost before confirming |
The goal is a tool that a person can use alone after the first guided try. If you are building a product for farmers or other users new to apps, you can see how I plan screens for mobile app design or write to me through the contact section.
Frequently asked questions
How do you design an app for low literacy users?
Use icons with labels in the local language, add voice instructions, make buttons large and show one task per screen. Test with real users before building.
Why should a farmer app work offline?
Network in fields and villages is often weak or absent. An offline capable app saves entries on the phone and sends them later, so the farmer never loses work.
Is voice a good interface for farmers?
Yes, as a help and not as the only way. Offer read aloud buttons and voice search, and always show what the app understood so the user can correct it.
How many languages should an agritech app support?
Start with the languages of the first region you serve and translate everything fully. Add more languages one at a time, with testing for each script on cheap phones.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.