Mobile Apps en Porto
How we work in Porto
The app identifier is written once and for good
The package identifier cannot be changed once the app is published. If it has to change, what you do is publish another one: the downloads, the ratings and the history stay with the old app and your users install something different. It is a field filled in five seconds that lasts as long as the product.
The developer account, in your company's name
App Store Connect and Google Play in your name, not the agency's. Transferring an app between accounts exists, with its conditions and its timings, but it is a formality that always has to be done at the worst moment, when there is already a rush. Starting well costs the same as starting badly.
What can be rebuilt without anyone noticing
The design, the copy and even the framework the interface is built with can be replaced without the user losing anything, as long as the logic and the data live on the server and not inside the phone. That separation is what keeps the door open to rebuilding the app without rebuilding the product.
Old versions stay installed
An app is not updated like a website: there will always be people carrying the version from eight months ago. The server has to keep understanding it for a while, so every change to the conversation between app and server is treated as something to maintain in parallel.
Answering your questions
What people ask us about Mobile Apps in Porto.
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