Logistics
Driver app
Daily tour, navigation, status updates, proof of delivery by signature or photo. Connected to PS1 or any ERP.
Mobile Apps · iOS · Android
Apps that
work in real
hands.
Driver, warehouse, field-service and self-service apps, built on top of your existing ERP backends. Natively in the App Store and Google Play, or hybrid.
◆ Apple App Store
◆ Google Play
◆ MDM-ready
◆ GDPR
07:42
●●●
Tour CX-117
Herne · Bochum
128 stops · ETA 16:20
42
Bahnhofstr. 12A. Becker
POD
43
Markt 8F. Yilmaz
POD
44
Goethestr. 3M. Wagner
↗
45
Lindenallee 14P. Klein
↗
Start stop 44 →
10:18
●●●
Scan mode
Goods receipt
Item
PS-AX-1284
Quantity expected
120
Storage location
B-04-12
14:03
●●●
Hello,
Ms Albrecht.
Current order
#24-2891
Delivered today · 11:42
Deliveries
Contracts
Service ticket
Invoices
Types
Six app types
Six app types
we build often.
Apps rarely fail on the front end, they fail on a missing backend concept. We build apps that work with real data from day one.
Service
Field-service app
Appointments, customer records, photo documentation, report sign-off with signature. Works offline on construction sites.
Warehouse
Warehouse & scan app
Barcode/QR scanning with a smartphone or handheld scanner, real-time posting into the ERP, easy to operate with gloves on.
Customer
Self-service app
Orders, delivery status, contracts, tickets. Takes the load off your back office and hotline.
Maintenance
Maintenance & service app
Maintenance schedules, inspection reports, defect logging, documented on site, saved into the system automatically.
People
Employee app
Shift schedule, leave requests, payslips, messages from the employer, used every day.
Stack
Native.
Native.
Hybrid.
Your call.
Native apps are more robust for hardware, performance and maintainability; hybrid apps cheaper and faster for a manageable feature set. We recommend what fits.
Native iOS
Swift
SwiftUI · UIKit · TestFlight
Native Android
Kotlin
Jetpack Compose · Material 3
Cross-platform
Flutter
Dart · Material · Cupertino
Cross-platform
React Native
Expo · TypeScript
Backend
Spring Boot
REST · OAuth2 · Webhooks
Push
FCM · APNs
Silent & standard push
One app, one backend
no two versions of the truth.
No second data silo: the app talks directly to the backend you already have.
Frequently asked
What clients
What clients
want to know first.
Native or hybrid, which is better?
Native is more robust for hardware access, performance and maintainability; hybrid cheaper for a manageable feature set. We recommend based on the app.
Can we use the app offline?
Yes, standard for driver, warehouse and field-service scenarios: data is buffered locally and synced later.
How do we publish the app?
Publicly via the App Store and Google Play, internally via MDM or Apple Business Manager. On request, we handle the full store setup.
What about data protection?
Data protection is part of the architecture: data flows minimised, permissions explained clearly, servers in Germany, on request without external tracking SDKs.
We already have an ERP. Can the app use it?
Yes. We connect existing ERPs via REST or webhooks; if a suitable interface is missing, we build one.
What does an app cost?
Realistically in the five-figure range, depending on feature scope and backend integration; concrete figures after a short workshop.
How long does the build take?
A focused first version typically in 8–14 weeks, larger app platforms with backend integration in 4–6 months.
Who maintains the app after go-live?
We do, on request via a maintenance retainer: OS updates, store requirements, security updates and smaller enhancements. The source code stays with you.
Know what your app
should do? Let's talk.
In a 60-minute workshop we cut the scope, clarify backend integration and estimate time and budget realistically.