Mobile Apps en Zurich
How we work in Zurich
A bad release cannot be taken back
On the web, the previous version returns in minutes. On a phone, whoever has already updated keeps what they have until another one ships and they install it. That is why the rollout starts with a small share of users and widens if no errors appear; if they do, it stops there and the rest never see it.
Switching a feature off without shipping anything
New features ship behind a switch controlled from the server. If something fails, it is turned off there and then for everyone, without waiting for a store review. It is the closest thing to a rollback that exists in an app already installed.
The phone's database migrates too, and there is no backup there
When an update changes how data is stored on the device, that conversion happens once and without a safety net: if it goes wrong, what the user had is lost and no restore will bring it back. It is tested by updating from the published version with data inside, never by installing clean on a simulator.
Tested on real phones, and not only on the good ones
Plenty of faults only appear on an old handset, with little memory, with battery saver on or with text enlarged for accessibility. Before anything goes to review, the build passes through physical devices and an internal test with your own people, not only with whoever wrote it.
Answering your questions
What people ask us about Mobile Apps in Zurich.
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