01
Mobile milk entry and scan capture
Log milk yield directly from a phone, or photograph a handwritten collection sheet for the AI scan pipeline to process later.
Mobile
Built for the field, not just the farm office.
The Boma mobile app lets workers log milk, health checks, and reminders where the work actually happens, including without signal, with entries syncing automatically and safely once the connection returns.
Offline-capable
Milk, health, and status updates queue locally and sync when reconnected.
Visible sync state
Every entry shows saved, synced, or failed so nothing is left in doubt.
Role-aware
Mobile access respects the same farm role permissions as the web dashboard.
Mobile
Field App
Saved locally, synced automatically
Every entry shows a clear sync status — saved locally, synced, or failed — so field staff always know whether their work has actually reached the farm’s record.
Product screenshot placeholder
What This Feature Does
In plain terms
Mobile Workflow Support covers how Boma works on a phone in the field, where most of the actual data about a farm is generated. Workers can record milk entries, log quick health checks, update an animal’s status or photo, and manage reminders directly from the mobile app, without needing to walk back to an office or wait until end of day to write things down.
Connectivity in the field is often unreliable, so mobile actions are designed to work offline first: an entry is saved locally the instant it is made and queued for sync, rather than requiring a live connection to succeed. When the connection returns, queued entries sync automatically in the background, with retries handled safely so a dropped connection never results in a duplicate or lost entry.
Every queued or synced item shows a clear status — saved locally, syncing, synced, or failed — so a worker always knows whether their entry has actually reached the farm’s permanent record, with a simple way to retry anything that failed.
Key Capabilities
What you actually get
Each capability below is available today inside Boma, not a roadmap promise. Together they form the working core of this feature.
02
Quick health check logging
Record a routine check or a concern for a specific animal in a few taps, clearing overdue flags without waiting to reach a desk.
03
Offline-first data capture
Milk entries, status updates, and reminder actions are saved locally first and queued for sync, so a lost signal never blocks the work from being recorded.
04
Automatic background sync
Queued entries sync automatically once connectivity returns, with no manual "upload" step required from the user.
05
Visible per-record sync status
Each entry clearly shows whether it is saved locally, syncing, synced, or failed, so trust in the mobile app does not depend on guessing.
06
Safe retry on failure
Failed syncs can be retried directly from the app, and retries are handled safely so a repeated attempt never creates a duplicate record.
07
Role-gated mobile actions
What a user can do on mobile — like changing an animal’s status — respects the same farm role permissions enforced on the web dashboard.
08
Photo capture for records
Attach a photo to an animal’s profile directly from the phone’s camera, useful for identity confirmation and visual condition tracking.
Why It Matters
The operational cost this feature actually removes
The moment farm work actually happens is rarely at a desk. A treatment is given in a barn, a milk session finishes in a parlor, a status change is noticed while walking the pens. If the only way to record that work is to remember it until someone gets back to a computer, a meaningful amount of it simply does not get recorded accurately, or does not get recorded at all.
Boma’s mobile app is built around the reality that field connectivity is inconsistent and field staff need software that works with them, not software that requires perfect conditions to be useful. Offline support with visible sync status means field staff can trust the app in the exact conditions where they actually use it.
Data captured at the moment it happens
Field entries do not wait for someone to reach a desk, which means fewer forgotten or approximated details.
No lost work from a dropped connection
Offline-first capture means a weak signal in the field does not block recording the work.
Confidence that entries actually saved
Visible sync status removes the uncertainty of not knowing whether a mobile entry actually went through.
Field staff empowered, not just office staff
Workers get real functionality on mobile, not a stripped-down viewer version of the platform.
Use Cases By Role
How each person on the farm actually uses this
Boma is built around real farm roles. Here is how this feature shows up differently depending on who is signed in.
Owner
Checks farm activity while away from the property
An owner traveling for business can review recent mobile activity and dashboard updates from their phone, staying connected to the farm without being physically present.
Manager
Trusts field entries without double-checking them at day’s end
A manager relying on mobile entries from the team does not need to reconcile a paper notebook against the system later, because entries are already structured and synced.
Worker
Logs milk and health data with no signal in the barn
A worker in an area with no cell signal continues logging entries normally — they save locally and sync automatically once the phone reconnects.
Vet
Logs a treatment immediately after examining an animal
A vet finishing a field exam records the treatment directly from their phone on site, rather than writing a note to enter into the system later.
Admin
Supports a farm troubleshooting a sync issue
A platform admin helping a farm understand a failed sync can see the entry’s status and guide the user through a retry, backed by a system designed to make failures visible rather than silent.
How It Works
Step by step, in practice
A mobile entry moves from the field to the permanent farm record through a reliable, visible path.
- 1
The action happens in the field
A worker logs a milk entry, a health check, or a status update at the moment the work occurs.
- 2
The entry saves locally first
The app saves the entry to the device immediately, independent of whether a connection is currently available.
- 3
The app queues it for sync
A background process attempts to sync the entry to the farm’s record as soon as connectivity allows.
- 4
Sync status is shown clearly
The entry displays as saved locally, syncing, synced, or failed, so the worker always knows its state.
- 5
Failed syncs can be retried safely
If a sync fails, retrying it will not create a duplicate record, keeping the farm’s data accurate.
Data & Control
Who can see it, who can change it, and who is accountable for it
Mobile actions respect the same farm-level isolation and role-based permissions enforced everywhere else in Boma — a mobile session cannot access or modify data the same user could not access from the web dashboard.
Offline queued entries use an idempotency key on submission, meaning a retried sync after a dropped connection is recognized as the same entry rather than being recorded twice, keeping the farm’s data reliable even when the network is not.
Same permissions as the web app
Mobile access follows the same farm role rules enforced on the web dashboard, not a separate looser standard.
Idempotent offline sync
Retried submissions after a dropped connection are recognized rather than duplicated.
Visible failure states
A failed sync is shown clearly rather than silently disappearing, so nothing gets lost without notice.
Local storage scoped to the session
Queued data on the device is tied to the signed-in user’s session and farm access.
Business Outcomes
What changes operationally once this is in place
These are the practical shifts farms describe once the feature is part of daily use, not a marketing estimate.
Real-time field data instead of end-of-day recall
Work gets recorded as it happens instead of being reconstructed from memory later.
No lost entries from poor signal
Offline-first design means field conditions do not block the work from being captured.
Confidence in what has actually synced
Visible sync status removes the guesswork around whether an entry made it into the system.
Field staff fully equipped, not just office staff
Workers get real functionality on mobile, closing the gap between where work happens and where it gets recorded.
Questions
Common questions about this feature
Specific answers for teams evaluating whether this part of Boma fits how the farm actually runs.
What happens if I lose signal while entering data?
The entry saves to your device immediately and queues for sync. Once your phone reconnects, it syncs automatically in the background — you do not need to do anything manually.
How do I know if my mobile entry actually saved to the farm’s record?
Every entry shows a clear status: saved locally, syncing, synced, or failed. A failed entry can be retried directly from the app.
Can a retried sync create a duplicate entry?
No. Offline submissions use an idempotency key, so a retried sync after a dropped connection is recognized as the same entry rather than recorded twice.
Do all farm roles have the same mobile capabilities?
No. Mobile actions respect the same role-based permissions used on the web dashboard, so what a user can do on mobile matches what their assigned role allows.
Is the mobile app a limited version of the web dashboard?
For field-relevant workflows like milk entry, health checks, and reminders, mobile provides full functionality. Broader administrative work is designed primarily for the web dashboard.
Related Features
Works alongside the rest of the platform
Ready To Try It
Give your field team software that works where they actually work.
Start free and put milk, health, and reminders in your team’s pocket, online or off.