Service
Apps
iOS and Android from one source — and the interfaces they hang on.
What we build
Apps for iOS and Android, from one source. Along with what sits behind them: sign-in, roles and permissions, payment, location and maps, sensors — and the interfaces to the systems you already run.
How we build
- One source, two platforms. What is meant to be the same on both is written once. What has to differ, differs deliberately.
- German as the default language, English alongside — in the store listings and the legal texts as well.
- Permissions one at a time, with a reason. Camera, location and notifications go in when a feature needs them. Not as a precaution, because one might want them later.
- Updates without the detour, where the platforms allow it: corrections reach the devices without waiting for a store review.
What does not happen
No advertising modules, no behavioural tracking, no library whose purpose we cannot explain to you. What an app collects about its users stands in its privacy policy — and what stands there is what it really collects.
What you get
- The app in your own developer accounts, published in your name.
- Source code and build instructions — complete enough that somebody else can carry on with them.
- The texts and images for the store listings, in German and English.
- Privacy declarations that match what the app actually asks for.
How it starts
With the question of what the app is to do on the device and where the data comes from. Only that shows whether it really has to be an app, or whether a website in the browser does the same — we ask that question before we write a quote.
Scope, process and price are stated in the quote — once it is clear what the job is. All amounts net, plus VAT.
The question first, then the platform
Describe the process the app is meant to carry. We will tell you what that takes — and what it does not.