Mobile Apps en Munich
How we work in Munich
Internal distribution, without going through the public store
If the app is going to be used by a company's employees, it does not have to sit in a store open to anyone. Both platforms allow internal distribution: it installs for whoever is on the list and disappears from the phone when that person comes off it. This is decided before building.
What stays on the phone, and for how long
An app is often fast because it keeps data on the device itself. The question that comes afterwards is which data, encrypted how, and what happens when the session ends. It answers well if it was decided at design time. Cutting it back later means rewriting the data layer.
Every third-party library is one more question
Analytics, crash reporting and notification components send data to servers that are not yours, and each one has to be declared and justified. Before adding one we look at whether it pays for itself, because pulling it out once it is in production costs more than putting it in did.
The permissions you ask for and the ones you do not
Camera, location, contacts, files. Every extra permission is a flag in the review and a reason for somebody not to install the app. We ask for the minimum, at the moment it is used rather than on launch, and we write down what each one is for. The stores require that justification anyway.
Answering your questions
What people ask us about Mobile Apps in Munich.
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