Mobile Apps en Manchester
How we work in Manchester
The app is published in the account of whoever built it
If the listing lives in the previous supplier's developer account, the app is not entirely yours. Transferring between accounts is possible, but it comes with conditions and the listing has to be left in a state the store will accept. What you cannot do is take it for granted on the day an urgent release is due.
Getting it to build again is the first goal
A mobile project left alone for two years does not compile: the toolchain moved on, the certificates expired and half a dozen dependencies no longer exist at the version it asks for. Before promising any feature we produce a reproducible build on a clean machine, written down step by step. Until that happens there are no serious dates to give.
The signing key, or starting over
On Android, if the key the app was signed with is lost and it is not held by the store's signing service, there is no way to publish an update: you have to create a new listing and give up the installs you already have. Asking where that key is comes very early, and there is not always an answer.
The users who already have it installed are the asset
Rebuilding a published app is not launching it again. It has to go out as an update, under the same identifier, and the data people already hold on their phones has to survive the migration. Ignoring that means asking every user to install something different, and some of them never will.
Answering your questions
What people ask us about Mobile Apps in Manchester.
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