Mobile Interface

The AgriERP mobile app is what most people in the agribusiness actually use to interact with the system. Not the web app on a desktop. Not the dashboards on a screen in the office. The mobile app, on a phone or a tablet, often in a glove or a dusty pocket, often offline, often in bright sunlight. It is the operating layer of the agribusiness, used by field workers, harvest crews, warehouse staff, machinery operators, supervisors, agronomists, and field officers, every single day.

This document is about what the mobile interface looks like, how people navigate it, and what makes it work in agriculture. For the architecture view of the mobile stack (sync, offline storage, security), see Platform Architecture > Mobile App.

1. The design principles

Core design choices

Capability	What it means in practice
Glanceable, not deep	Every primary screen surfaces the information the user needs in a single glance: “what am I doing today, what is next, what needs my attention.” Drilling deeper is possible, but the surface answers the common question.
Touch targets sized for gloves and dirt	Buttons, list items, and tap targets are sized larger than the standard mobile guideline. A worker with muddy hands or wearing gloves can still hit them reliably.
High contrast, large text	Designed to be readable in direct sunlight on a phone screen. Default text size is generous; users with vision difficulties can scale further.
Local language by default	The interface displays in the user’s chosen language. Common agricultural terms are translated correctly; signs, labels, and form fields all match. English is one option among many, not the default.
One-thumb operation	Most key actions can be completed with one hand. Common in the field where the other hand is holding tools, produce, or a bin.
Offline-first interaction	The interface does not behave differently when offline. Users see no connectivity errors during normal work; sync happens in the background when signal is available.
Visual confirmation	Critical actions (scanning a bin, completing a work order, clocking in) trigger a clear visual and haptic confirmation. Workers know the action landed without checking a status screen.

2. The role-based home screen

Home screens by role

Capability	What it means in practice
Harvest or field worker	Today’s work orders at the top: what crew, what block, what activity. Below: clock-in status, current task, and a single primary action (“Start work,” “Scan bin,” “Submit count”). Most of the screen is one or two actions away.
Crew supervisor	Crew status: who is clocked in, who is missing, the work orders assigned to the crew today, productivity against target. A team-overview lens rather than an individual-task lens.
Agronomist or scout	Today’s farm visits, the blocks to inspect, any open scouting tickets or follow-up items. The map view is one tap away.
Machinery operator	The equipment assigned today, pre-use checklist, current work order, hours-meter entry. The asset details one tap away.
Warehouse worker	Today’s putaway, picking, replenishment, or dispatch tasks. Scanner access on the primary button.
Field officer (grower programs)	The day’s grower visits, each with grower code, location, purpose of visit, and any outstanding follow-ups.
Manager or director	Operational dashboards: live status of farms, exceptions surfaced, financial headlines. Read-mostly, with drill-down.

Why the home screen matters

• First impression: the user opens the app many times a day. If the first screen does not show what they need, they have to navigate to find it. Multiplied across hundreds of workers and thousands of opens, the time loss is large.
• Reduced training: when each role sees only their relevant content, training is faster. A new harvest worker does not have to learn the navigation; the screen presents the actions they need.
• Less screen-noise: irrelevant menu items hidden, not shown-and-disabled. The screen feels light, focused, and answerable in a glance.

3. Navigation

Bottom navigation

Most users see a bottom navigation bar with four or five tabs, each leading to a primary work area. The tabs themselves vary by role: a harvest worker sees different tabs from a field officer. The principle is the same: the most-used areas are one tap from anywhere in the app.

Typical navigation tabs

Capability	What it means in practice
Home	The role-based home screen. The default screen when the app opens. Always available.
Work	The work orders, tasks, or activities assigned to the user. The screen where most of the actual work happens.
Map	The map view showing the user’s location, the blocks and assets around them, and the work points relevant to their activity.
Scan	Direct access to the barcode and QR scanner. For workers who scan frequently (warehouse, dispatch, harvest), the scanner is permanent on the bar.
Notifications	The notification inbox: alerts, messages, approval requests, escalations. Badge counter shows the unread count.
More	Less-frequent areas: profile, settings, help, language change, sync status, log out. The drawer pattern, not the primary screens.

Deep navigation, when needed

• Breadcrumbs and back behaviour: every screen has a clear back path. The user is never trapped or lost; pressing back returns to the previous screen, not a generic home.
• Search: where the user knows what they are looking for (a specific grower, a specific block, a specific work order number), search is available on the relevant screens. Predictive results show as the user types.
• Quick actions: long-pressing a list item often surfaces quick actions (view detail, mark complete, escalate, message) without forcing a navigation into a detail screen.
• Shortcuts to common workflows: frequent actions (scan a bin, log a fault, request a transfer) have direct entry points from the primary screens. No menu archaeology required.

4. Language, accessibility, and offline

Language support

• Multi-language by default: the app ships with the languages the program operates in. Workers select their preferred language at first login; the choice is persistent.
• In-context translation: field labels, button text, and notification messages are translated by agricultural-domain translators, not generic translation services. “Spray work order” carries the right local meaning, not a literal word-for-word rendering.
• Voice support for low literacy: for workers with limited reading ability, key prompts and confirmations can be played as voice in their local language. Optional, not imposed.
• Numerals and currency: displayed in the format the user expects: local digit systems where used, local currency symbols, local date format.

Accessibility

• Text scaling: users can scale text size up or down. The layout adapts without breaking.
• High contrast mode: for users who struggle with low-contrast screens (vision difficulties, screen damage, bright sun), a high-contrast mode is available.
• Screen reader support: for users with visual impairments, screen reader compatibility is maintained on key screens.
• Reduced motion: users sensitive to animation can reduce or disable animations.

Offline behaviour

Most of the app continues to work when there is no signal. The interface does not change; the user does not see error messages; the system tracks what needs to sync when connectivity returns.

• Visible sync state: a discreet indicator on the screen shows whether the device is online, syncing, or offline with pending data. Workers learn to glance at it; the system does not interrupt them with modal dialogs.
• Queue and retry: actions performed offline are queued. When connectivity returns, they sync in the right order. Conflicts (rare in a properly-designed system) are surfaced to the user, not silently overwritten.
• Cached reference data: the blocks, grower lists, item masters, and other reference data needed for the day’s work are cached on the device. The user can open the app and work without ever connecting to a server.
• Long offline runs: the app is designed to handle days without sync, not just hours. Field officers working remote areas can capture a week’s data and sync when they return to the office. Storage and integrity are managed appropriately.

Why this mattersA mobile app that fails in the conditions of real agricultural work is worse than no app at all. It teaches workers to distrust the system; it forces them back to paper; it loses data; it creates errors. An app that works in the conditions of real agricultural work earns the trust of the people using it. That trust is what makes the operational data captured at the point of work actually accurate and complete, which is what makes everything else AgriERP does possible.

In summary

The Mobile Interface is the front door of AgriERP for almost everyone in the operation. Role-based home screens show each user what matters for their job. Simple bottom navigation puts common actions one tap away. Language support, accessibility, and offline behaviour respect the conditions the app actually has to work in. Design choices, glanceable surfaces, generous touch targets, high contrast, local language, are deliberate, not accidents.

For what users actually do on those screens, see the next four documents in this section: Work Execution, Time Tracking, Notifications, and Map View.