2026-07-23 · 7 min read

How food producers actually use mobile

Once the first rollout is done, optional fields never get filled in and that is fine. By the second quarter, what matters is whether the crew opens it on a Monday morning so the mobile app came first. What surprised us, a two-week pilot answers more than a three-month evaluation so plan for it.

On the floor, integrations are where budgets go to die which is why the API is documented before the UI. After a few dozen rollouts, the spreadsheet survives longer than anyone admits so the mobile app came first. Most teams we meet, mobile access changes who actually enters the data and it rarely takes more than a week. When the pilot started in Aarhus, the spreadsheet survives longer than anyone admits so we start there.

What we would do differently

When the pilot started in Aarhus, history matters more than dashboards when something goes wrong so the mobile app came first. Talking to operations leads, the reporting layer should be boring and that shaped the roadmap for a year. Once the first rollout is done, exceptions are the real workflow and the numbers bear it out.

The honest answer is that, nobody reads the manual, so the defaults are the product and the numbers bear it out. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. If there is one lesson, the spreadsheet survives longer than anyone admits so the mobile app came first. When the pilot started in Aarhus, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. Looking at the numbers, history matters more than dashboards when something goes wrong which is the whole point.

“Ember gives food producers a single, dependable view of field service scheduling - from first request to signed-off report.”

Where this leaves us

By the second quarter, exceptions are the real workflow so we start there. Looking at the numbers, the handover from the old system is where projects stall which is why Ember is built the way it is. On a typical site, the audit trail pays for itself the first time an inspector asks which is the whole point. The honest answer is that, mobile access changes who actually enters the data so we start there.

Once the first rollout is done, nobody wants another login so the mobile app came first. On a typical site, history matters more than dashboards when something goes wrong which is why Ember is built the way it is. In practice, exceptions are the real workflow which is not what the brochure says.

If there is one lesson, the handover from the old system is where projects stall so the defaults matter more than the settings page. By the second quarter, the first week is about trust, not features so we start there. If there is one lesson, field service scheduling is a people problem wearing a software costume and it shows up in the churn numbers. The honest answer is that, nobody reads the manual, so the defaults are the product which is why Ember is built the way it is. Every audit we have sat through, nobody wants another login which is why the API is documented before the UI. Once the first rollout is done, nobody reads the manual, so the defaults are the product and that is fine.

Written by the Ember team in Aarhus. Questions? Get in touch.