Mobile Apps en Frankfurt
How we work in Frankfurt
With no signal the phone is in charge, and you need to know it
An app used in a warehouse or out on the road creates records that take hours to upload. Each one stores the time it was actually created and the time it reached the server, which don't match: confusing them is what makes a report fail to add up. We solved this in Arrels 360, for technicians on the move.
Two phones, the same record, nothing lost
When two people modify the same thing offline, somebody has to decide which version wins. That policy is agreed with you before any code is written, and both versions are kept. What we don't do is let the last upload win and delete the other one without telling anyone.
Every installation knows which version it runs
Errors arrive tied to the build number and the commit that produced them, so a bug that only shows up in the version from two weeks ago is found in minutes. With hundreds of phones updating at their own pace, knowing what code each one runs stops being a detail.
The user sees what has been uploaded and what hasn't
Someone filling in a job sheet wants to know it arrived. The app shows what is still pending upload, what went up and at what time, without asking anyone to take it on faith. That one indicator removes half the checking calls and stops the same sheet being entered twice.
Answering your questions
What people ask us about Mobile Apps in Frankfurt.
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