There comes a point where the browser is not enough: scanning a hundred barcodes in a row, taking a photo as evidence, working in a warehouse with no signal, keeping the app open all day. That is when an installed application earns its cost.
What we build
Warehouse and logistics - WMS
Receiving, put-away, order picking, transfers, rolling inventories. Entry happens on the handheld or the phone camera, at the actual workstation rather than back at the office. Discrepancies surface while they can still be explained.
Catalogue and order taking
The salesperson shows the catalogue at the customer's site - references, photos, availability, the price that applies to THIS customer - and enters the order there. The document reaches your system as soon as the network returns.
Field CRM
Visits, reports, follow-ups, the customer's credit position checked before walking in. The report is dictated or keyed in the car, not at home in the evening. Photos and signatures attach to the visit.
Service calls and maintenance
Work order, parts consumed, time spent, before and after photos, customer signature on screen. The report is complete when the technician leaves the site.
What an installed app adds
Working offline
A basement warehouse, a rural area, a lift: work continues. Entries are held on the device and synchronise when the network returns, with conflict detection - two people editing the same line do not silently overwrite each other. This is the first reason to choose an app over a website.
The phone's hardware
Continuous barcode and QR scanning, camera, GPS, on-screen signature, NFC, printing to a mobile printer. Rugged Android handhelds (Zebra, Honeywell) are supported with their physical trigger.
One codebase
We build in Flutter: Android and iOS from the same code. A fix is written once, tested once, shipped to both. That is what makes a custom mobile app affordable for a mid-sized company - two separate native builds are not.
The same data as everything else
The app talks to the same database as your management application, or to your Sage through the same interface. No parallel master data to reconcile: an item created at the office is visible on the phone.
Distribution and updates
Published on Google Play and the App Store, or distributed internally when the app is not meant to be public - often the case for a WMS. Updates are pushed without reinstalling on each device by hand.
What we do not do
We do not build an app when a browser site is enough: it costs more to build and maintain, and it has to be installed. We do not build games or consumer apps unrelated to your operation. And we do not track your employees: location only timestamps a service call, with their consent.
If the browser is enough
Many mobile needs are met without installing anything: lookups, occasional entry, order updates by messaging. Cheaper and simpler to roll out - see Mobile and conversation channels.