When deep linking is worth the effort

This is one of those topics that looks small until it costs you something. Deep linking is not free, and pretending otherwise leads to bad decisions.

You do not control the device, the network, or the operating system version, and the design has to accept that. It is the sort of thing that looks like polish right up until it costs you an enquiry.

When it is worth it

Every shareable screen should have a URL. Small and consistent beats large and occasional here. Budget a little time for it every quarter and it never becomes a project of its own.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. Getting it slightly wrong is survivable. Ignoring it entirely is not.

How to decide

Test the case where the app is not installed. The reasoning matters more than the rule, because the rule has exceptions. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

In practice

Mobile releases are slower to correct than web ones, so the cost of shipping a mistake is higher. Three things worth confirming about deep linking before you move on:

• Someone can say what the current setup is without going to look
• Test the case where the app is not installed — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Worth checking on your own setup before it becomes someone else's problem to fix.