Case study
iPhone app link opens the wrong screen
A link that opens an app's home screen instead of the page it named makes customers think the app is broken. We found the cause in one file on the website that every app version reads, and changed it to promise only what the oldest version can show.
Key takeaways
- A link that opens the wrong screen is worse than one that opens the browser.
- The website file that tells iPhones which links belong to your app is read by every installed version.
- Claim a page only when the oldest app version you still allow can show it.
- Test links on an older version, with the app closed and the person signed out.
- A link tapped before sign-in should wait and open on the same screen as a notification about that page.
A tapped link that opens an app's home screen instead of the page it named is worse than one that opens the browser. The customer reads it as the app being broken, or as the thing they were sent having disappeared. On our own platform, emails and messages link to a request, a board or a chat, and our new iPhone app can show each as its own screen, so making those links open the app looked like the obvious shortcut — except on every older version still on people's phones.
A link that lands in the wrong place costs trust
The shortcut only works if it lands on the same thing the link named. A customer who taps a link to a request, a board or a chat and arrives on an app's home screen has no way to tell whether the request is gone or the app is broken. Old versions of an app stay on phones for months, because many people never update until they are made to, so the confusion keeps coming rather than clearing up quickly.
Why an iPhone app link opens the wrong screen
Apple decides whether a tapped link opens the app or the browser from a small file your website publishes. The file lists the addresses the app takes over; people in the trade call these universal links, and you can think of the file as the list of addresses your app claims. There is one file for the whole website, not one per app version. Every installed version reads the same list, so the question is not only whether the newest version can open a page, but whether every version still allowed to run can. Turning the new links on the day the new version was built would have sent everyone on an older version to the home screen.
What we found
The older versions did what the shared list told them: they opened the app, then showed the home screen without saying anything. We also found a second gap in the new version itself. A link tapped while the app was still starting, locked with face recognition, or before anyone had signed in could be lost before the screen it pointed to existed. The list of addresses is shared by every version on people's phones, while only the newest version knows the new pages.
The website makes the promise, not the app
An app cannot fix this from inside. The website is the only place that tells the phone which addresses belong to the app, and it speaks to every installed version at once. That is why the change belongs on the website, not only in the new app. The app can hold a link that arrives before sign-in, but it cannot make an older version show a screen that version never had.
What we changed
We made the website's file follow the oldest app version we still allow to run, instead of a fixed list. Until that oldest version can show the new pages, the file names only the few addresses every version handles: coming back from a card payment, a question in the help, and a sign-up code. Once we raise the oldest allowed version — already a step of every app release — the file adds the pages for requests, chats, boards and the rest of the account pages by itself, with nothing else to remember. The website asks for that oldest version at most every ten minutes and keeps its last answer if one check fails, so a brief failure never changes what phones are told. In the app, a link tapped before the account is on show is now held, the way a tapped notification is, and opened once the person is in, on the screen a notification about the same page would open.
Where it stands
The website side is live: today it names only the addresses every version handles, so nobody on an older version is sent to the wrong screen. The iPhone app version that opens the new pages is built and in testing, on its way to the App Store. Once it is out and becomes the oldest version allowed, links to requests, chats and boards will open straight in the app by themselves: 11 extra kinds of page beside the 3 every version already handles. We built and deployed the website side in one day, the day after the new app version gained its links between screens.
What you can check yourself
- Tap a link to your own website from an email on an iPhone with your app installed, and see whether it opens the app on the right screen or the browser.
- Ask your developer which addresses your website tells iPhones belong to your app, and whether the oldest version people still use can open each of them.
- Tap a link to your site while your app is closed and locked, and check that you still end up on the page the link named after you open the app.
- Check how many of your app's users are still on old versions before you change what a link does.
- Open the same link on an iPhone without your app, and confirm it opens the browser page a customer would expect.
Questions people ask
Why does a link to my website open my iPhone app on the home screen instead of the page I sent?
Because your website has told iPhones that the address belongs to your app. If the installed version of the app does not know that page, it can open the app and show the home screen. The website's list is shared by every version, so an older app can claim more than it can show.
Do old versions of my app really matter once a new one is in the App Store?
Yes. A new version does not remove older ones from phones. People can keep an older version for a long time, and the website's list still applies to it. The safe rule is to promise a page only when the oldest version you still allow can show it.
Can I choose which links open the app and which open the browser?
Yes, through the list your website publishes. You can name only the addresses every version handles, such as a payment return or a sign-up code, and leave the rest opening the browser. Turning on a new address is a change to ask whoever looks after the site about.
What happens if a customer taps a link before they have signed in to the app?
Without handling, the link can be lost while the app is starting or waiting for sign-in. We now hold it the way a tapped notification is held and open it once the person is in. The screen should be the one a notification about the same page would open.
How soon after releasing a new app version can I turn on links to its new screens?
Only once that version is the oldest one you still allow. Until then, the website should claim only what every version in use can show. When the oldest allowed version is raised, the website can add the new addresses without a separate switch.