Mobile Apps en Rome
How we work in Rome
The installed version still points where it pointed
Publishing an update does not install it on people's phones. Weeks after a change there are still users on the previous version asking the old entry point for data. That is why that entry point is not switched off on launch day: it runs alongside the new one until usage figures say nobody is calling it.
Deep links live on the web domain
For a link to open the app instead of the browser, iOS and Android read two small files hosted on your domain. They are among the first things to disappear when a site is rebuilt, because they are not part of any page and nobody misses them until links stop opening the app.
A shared link lasts for years
Somebody sent a product page over messaging in 2021 and that conversation is still there. When the structure changes, that link has to keep leading somewhere sensible: inside the app if it is installed, in the browser if it is not. They are two different paths and both get tested.
The store listing carries URLs too
The privacy policy, the support site and the legal notice you declare in the App Store and Google Play are specific addresses. If they stop responding after the site is rebuilt, the problem surfaces at the next review and holds up an update that had nothing to do with it. They go into the same sweep.
Answering your questions
What people ask us about Mobile Apps in Rome.
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