// Logistics
Driver app
Daily tour, navigation, status updates, proof of delivery by signature or photo. Connected to PS1 or any ERP. Tough enough for everyday use.
// Mobile Apps · iOS · Android
Apps that
work in real
hands.
Driver apps, warehouse apps, field-service apps, self-service apps. Built on top of your existing ERP backends, not next to them. Published natively in the App Store and Google Play, or as a hybrid cross-platform solution.
◆ 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, not with demo JSON.
// Service
Field-service app
Appointments, customer records, asset records, photo documentation, report sign-off with signature. Works offline at industrial sites and 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 and under warehouse lighting.
// Customer
Self-service app
Orders, delivery status, contracts, service appointments, open tickets. Takes a noticeable load off your back office and hotline.
// Maintenance
Maintenance & service app
Maintenance schedules, inspection reports, defect logging, asset history, documented on site and saved into the system automatically.
// People
Employee app
Shift schedule, leave requests, payslips, messages from the employer, an app that gets used every day.
// Stack
Native.
Native.
Hybrid.
Your call.
Native apps are more robust when it comes to hardware, performance and long-term maintainability. Hybrid apps are cheaper and faster for a manageable feature set. We recommend what fits, not what we enjoy building.
// 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.
We don't build a second data silo next to your ERP. 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?
It depends on the app. Native is more robust for hardware access, performance and long-term maintainability. Hybrid is cheaper and faster when the feature set stays manageable. We give you an honest recommendation.
Can we use the app offline?
Yes. For driver, warehouse and field-service scenarios, offline mode is standard: data is buffered locally and syncs as soon as a connection is available.
How do we publish the app?
Publicly via the Apple App Store and Google Play. For internal apps via MDM (e.g. Microsoft Intune) or Apple Business Manager. On request, we handle the full store setup for you.
What about data protection?
Data protection is part of the architecture, not just the copy. Data flows are minimised, permissions are explained clearly, servers are in Germany. On request, entirely without external tracking SDKs.
We already have an ERP. Can the app use it?
Yes. We connect existing ERPs (including custom-built ones) via REST or webhooks. If the ERP has no suitable interface, we build one, usually within a few sprints.
What does an app cost?
Realistically in the five-figure range, depending on feature scope, platform choice, backend integration and design depth. We give you 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, in clearly defined stages.
Who maintains the app after go-live?
We do, on request as part of a maintenance retainer. OS updates, store requirements, security updates and smaller enhancements. The source code stays with you, we're not the lock-in.
Know what your app
should do? Let's talk.
In a 60-minute workshop we cut the scope cleanly, clarify backend integration and give you a realistic first estimate for time and budget.