01 · Context
A public-service workflow had to feel usable in the field.
E-Peek Pahani enabled Maharashtra's farmers to record crop information digitally and interact with agricultural land records through an Android application.
The target audience was broad: farmers differed in literacy, smartphone familiarity and access to reliable internet. A conventional text-heavy government interface could easily turn a necessary task into a confusing sequence.
The design challenge was to translate official requirements into a clear, locally understandable workflow—without ignoring the practical realities in which the product would be used.
02 · My role
From field information to flows and final interface.
I worked closely with the Project Manager throughout the process, synthesising information collected in the field and converting it into UX decisions and UI design.
Research synthesis
Reviewed field information, farmer inputs and functional requirements shared by the PM and field team.
Problem solving
Used brainstorming and secondary research to identify practical solutions for the key farmer tasks.
UX and UI design
Defined task flows, navigation patterns, wireframes and the final Android interface.
Cross-functional delivery
Coordinated with the PM and frontend and backend developers as the designed product moved into implementation.
03 · Field inputs
Design decisions began with observed farmer needs.
Approximately ten farmer interviews contributed to the project. The field team, Project Manager and designer collected and interpreted the information used to shape the experience.
Important actions needed to be understandable in Marathi and recognisable beyond text alone.
The product could not assume that every farmer was comfortable interpreting complex mobile navigation.
The experience needed to account for inconsistent connectivity rather than depend on an uninterrupted session.
04 · Core journey
A guided sequence for completing an official task.
The information architecture grouped the experience around recognisable farmer goals instead of exposing the complexity of the underlying administrative process.
05 · Inclusive-design decision
Pairing icons with text throughout the navigation.
Icons and Marathi labels—not icon-only navigation
Not every farmer had the same literacy level or comfort with text-heavy digital interfaces.
Menus, submenus and relevant clickable actions combined a familiar icon with a written label.
The paired cues improved recognition while keeping the meaning explicit for users who could read the label.
06 · Operational constraint
Designing for unreliable connectivity, not ideal conditions.
Offline functionality as part of the core experience
Farmers could be completing the task in areas where mobile connectivity was slow or inconsistent.
The experience accounted for offline use so connectivity would not immediately block task progress.
A field product should preserve user effort and provide a path forward when infrastructure is unreliable.
07 · Validation
Tested with the intended users before release.
The application was tested with target farmer users before public deployment, helping the team assess whether the main actions and navigation were understandable.
After testing and refinement, the product moved through development and was released publicly on Google Play.
08 · Visual design
A Marathi-first interface built around recognisable actions.
Selected screens from the original project show the green visual language, icon-supported choices, task-oriented cards, forms and crop-recording views used across the Android experience.
09 · Outcome
From field-informed design to a live public-service product.
The designed application was developed, tested with target farmers and released on Google Play. It provided a more structured way for farmers to report crop information and interact with land-recording tasks digitally.
The central lesson was that inclusive design is not a visual layer added at the end. Language, recognition, navigation and connectivity constraints must shape the product architecture from the beginning.