GSMA Publishes UX Design Guidebook for AgriTech Builders
GSMA's new AgriTech UX Design Guidebook tells product teams how to design for low-literacy, low-bandwidth, shared-device users in rural markets where connectivity drops and one phone serves a household.
- AuthorRebecca Stone
- ChannelUX Research
- Filed
- Read3 min

- GSMA released the AgriTech User Experience (UX) Design Guidebook for designers and product teams.
- The guide targets smallholder farmers and rural agricultural workers in low-connectivity markets.
- It addresses shared-device, low-literacy, and low-bandwidth conditions as default design constraints.
- It aligns with WCAG 2.2 inclusive design principles applied to an infrastructurally constrained audience.
- Hundreds of AgriTech services have launched across Africa and South Asia over the past decade.
By Rebecca Stone
GSMA, the mobile industry group that represents operators worldwide, has released an AgriTech User Experience (UX) Design Guidebook. The publication targets designers and product teams building digital tools for smallholder farmers and rural agricultural workers.
The release lands in a sector where design has lagged behind deployment. Hundreds of AgriTech services have launched across Africa and South Asia over the past decade. Many of them shipped with familiar patterns. Most failed in the field.
What problem does the guidebook solve?
Most UX playbooks assume a literate user, a personal smartphone, and a reliable broadband connection. None of those hold for the average smallholder farmer using AgriTech today. The GSMA guide reframes the user as the starting point, not the final check.
That single inversion changes how a product gets built. Information architecture has to assume a one-handed grip, glare on the screen, and a network that drops mid-tap. Onboarding has to work on the third try, not the first.
What does "design for the field" actually mean?
It means voice where a text field would normally sit. Icons where a paragraph would normally go. Error messages that speak, rather than scold. And a session length that fits between milking and the morning market — not a 40-minute onboarding flow.
The GSMA guide is the mobile industry's attempt to codify this. The patterns are not new to anyone who has shipped in design-for-development. The packaging is.
A voice-first layer lets a farmer query a market price while herding cattle. An SMS fallback, with a USSD menu behind it, covers the moment when LTE disappears. A pictorial home screen replaces a text-heavy dashboard. Each choice is a deliberate trade against capability.
Why shared phones still trip up designers
A single smartphone in a household or cooperative can serve five, ten, even twenty users over a week. Profile-based design collapses. Login walls fail. Personalization means nothing if the person holding the device changes.
Designers trained on personal-device assumptions tend to miss this. The guide, by all indications, treats shared-device flow as the default state, not the edge case. That alone is worth the read.
Where does this sit next to mainstream UX standards?
It sits next to WCAG 2.2 and the broader inclusive design canon, with one important difference. Accessibility standards were written for users with disabilities in connected markets. The AgriTech user often has a working phone, a working pair of eyes, and a network that goes dark every afternoon. The constraints are infrastructural, not personal.
Both worlds need the same underlying discipline — perceivable, operable, understandable, robust. The GSMA guide applies that discipline to a population the standards bodies rarely target. Mobile money, weather alerts, and market prices all live or die on the same handful of pixels.
What comes next?
The guidebook's value will show up in shipping decisions, not in download counts. The test is whether the next wave of AgriTech tools — advisory chatbots, climate information services, e-commerce platforms — actually launch with these patterns baked in.
The mobile industry now has a shared reference. Designers have somewhere to point when product managers ask why the screen needs a voice button. The hard part, as always, follows the publication.
Source: Google News: UX research
More from Rebecca Stone
Show full bio
News editor covering technology and product news in Product and interaction design, design systems at Interface Wire.
50 articles