Mobile Apps en Rotterdam
How we work in Rotterdam
The phone does not talk to the ERP, it talks to a layer of yours
Between the app and the management software sits a middle service that translates, validates and limits the rate of requests. It does two things: it stops forty phones asking at once from taking down a server built for ten desktop users, and it stops an internal change from forcing a new release in the stores.
When both sides believe they hold the good record
A technician closes a job sheet with no coverage while somebody in the office edits that same record. On sync you have to decide who wins, and there is no single answer: field data rules from the field, administrative data from the office, and whatever cannot be decided gets asked. It is the heart of Arrels 360.
The old version of the app is still installed
Nobody updates at the same time, and versions live side by side in the stores for months. That is why the middle layer keeps versioned contracts and does not break the old ones: fields are added, never redefined. It is the difference between shipping an improvement on Tuesday and finding out on Wednesday that half the staff cannot work.
The app inherits the odd rules of the old system
Every program with some years on it has its own wildlife: statuses that no longer mean what they say, mandatory fields people fill with a full stop, the generic customer that everything which does not fit gets booked to. They get documented at the start, because if the app ignores them, what it sends back will not go in.
Answering your questions
What people ask us about Mobile Apps in Rotterdam.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Mobile Apps: stack, process, use cases and FAQs