The paperwork is done by the time the driver moves on
- Fewer errors documentation happens at delivery
- Offline the record can be made on the spot
- Guaranteed every single record reaches the system
- 150 drivers use the app every day
- The documentation from the field arrives in varying quality.
- Someone has to put it right afterwards, in several places.
- The systems are built for the office, not for being on the move.
That is what it looks like in many companies with people on the move. These are some of the challenges we have worked on with Bygma.
What was Bygma facing?
Bygma is one of the Nordics' largest suppliers of building materials, and delivery is part of the product. Bygma had built a web version for the drivers themselves, and it covered part of the job. But it required a connection, and that is rarely available exactly where the goods are dropped off.
The consequence was that things could not be done consistently. Records were forgotten or made later from memory, the documentation arrived in uneven quality, and head office had to ring around to fill in what was missing. The experience from the web version was what made it clear what the solution actually had to be able to do.
Bygma gets consistent documentation first time, every time.
A web version that required a connection. Records were forgotten, the documentation was incomplete, and head office had to follow up by phone.
The delivery is recorded on the spot with scanning and photos, and the documentation is the same no matter who is driving.
The driver gets a tool that is faster than paper, instead of a system that has to be tended to.
Built to work when the connection doesn't
- Offline first
The driver can record the whole delivery without a connection. There is no offline mode to switch to; that is simply how the app works.
- Guaranteed delivery
The server solution acknowledges every piece of material and keeps going until it has arrived. Nothing disappears because a connection broke along the way.
- One hand, large buttons
The interface is cut for use under pressure: few choices, large tap targets, and no screens that require finding shelter to read.
It is the interplay between app and server that makes the solution trustworthy. Because the documentation is correct on the spot and always arrives, the rework further down the chain disappears.
The technology choice decided whether the solution could be trusted
An app is not always the right answer, and web is often cheaper and faster to get started with. But when a tool has to be used every single day, by people with no signal, and the result has to be trustworthy, the requirement shifts from convenience to robustness. That is where a native app became the right choice.
Stay on web
- Faster to start and cheaper to run
- But it assumes a connection, which is missing at the address
- No guarantee that a record survives the day
App on the road, server solution behind it
- The record can be completed regardless of signal
- The server guarantees the material reaches the systems
- Flutter gives iOS and Android from the same codebase
Three moves that keep the solution robust and cheap to own
Bygma knows the logistics, the routes and the documentation requirements. Our contribution was building both the app and the server solution behind it — robust enough for daily operation and no more expensive than it needs to be.
- 01
One codebase, two platforms
Flutter means drivers on iOS and Android get the same app, and fixes only have to be made in one place.
- 02
Server solution with a safe route to the ERP
The integration to M3 is built as a separate service that both guarantees delivery of the data and lets the app be developed further without disturbing the rest of the house.
- 03
Contacts right at hand
The recipient and the relevant Bygma staff are one tap away, so a problem at the address can be solved on the spot.
A clickable prototype before the first line of code
We built a clickable prototype first and tested it before development started. That made it possible to find the use cases that were not in the brief, and it kept development costs down.
Bygma's own staff gave the feedback that shaped the app. They know what a delivery day looks like, and that knowledge decides whether a tool gets used or left in the glove compartment.
Coignite has been a trusted partner in developing our Driver app, which has created real value by making complex tasks simple and efficient. The app has improved the workflow and increased productivity for our drivers. Coignite’s reliability and understanding of our needs make them an invaluable partner in our digital development.
Data from the road that can be used for more than delivery
The app is built as an internal system where Bygma decides which tools and information the drivers should have access to. It can be extended as the workflows change, without the logistics having to be reorganised around the software.
Because the app follows the goods all the way out to the address, a reliable record also emerges of what was driven where and when. That is exactly the kind of data ESG reporting asks for, and which otherwise has to be assembled retrospectively in spreadsheets. The trail is already there, as a by-product of the drivers getting their work done.
- Industry
- Building materials and logistics
- Platform
- Mobile app (iOS and Android) and server solution
- Our role
- Development partner with operational responsibility under a service agreement
- Capabilities
- UX and service design , App development , System development
- Technologies
- Flutter (Dart), Java/Scala, Postgres
- The collaboration
- Prototype first, then development with Bygma's own people
Shall we look at your work in the field?
- A reply from one of us by the next business day.
- A no-obligation review of your situation.
- Clarity on which options are relevant to you.
- A concrete plan, if you choose to go ahead.