Mobile Apps en Vienna
How we work in Vienna
The expiry date is set by the stores
New versions of iOS and Android arrive every year, and the stores keep raising the minimum level an app must target in order to be updated or reach new users. That forces at least one release a year even if nothing in yours changes. It is not our criterion: it is somebody else's calendar.
Certificates expire on a Sunday
Signing keys, provisioning profiles and push notification certificates all expire, and none of them warns you as far ahead as you would like. We keep an inventory with each one's date and who holds it inside your company. It is boring and it saves the Sunday afternoon phone call.
The parts of an app age faster
A maps component, a payments one or an analytics kit stop being compatible with the new system, and sometimes their author stopped touching them a long time ago. That is why we pick few outside parts and the best-supported ones: swapping a core dependency means rebuilding a whole section.
Next year's cost, said before signing
Alongside the development quote we give a yearly figure for what it costs to keep the app alive: developer accounts, compulsory updates and compatibility work. We would rather lose a project for stating that figure than win it by keeping quiet and have the awkward conversation fourteen months later, when the budget is gone.
Answering your questions
What people ask us about Mobile Apps in Vienna.
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