Two needs for deep linking
What are Deep Links? Scott Rosenberg recently wrote a piece on Backchannel on Medium about Deep Links. He wrote:
Deep linking means to bore a wormhole-tunnel that hops you directly from a specific spot in one app to a spot in another, no side trip to a browser or a home screen needed.
You get it. If you have Swarm and Foursquare or Facebook and Messenger installed you get pushed from one application to another all the time. Facebook forces you to send private messages via Messenger and Foursquare forces you to check-in via Swarm. So, if you’re in one app and need to do one of those tasks it “deep links” you from one application to another.
Sort of like a hyperlink on the web goes from one web page to another.
Rosenberg goes on to state why he thinks they’ve failed (so far). Here is my reason:
They aren’t discoverable. They can’t easily be found, written, or shared. You may see one from time-to-time. For example, if you click on a Periscope link on Twitter you will be asked to open Periscope to view the live video stream. This is a “deep link”. And, the URL for the deep link looks sort of familiar but also foreign and weird. It is typically something like pscp://broadcast/2034390
To me that reads; open Periscope to this broadcast.
Wouldn’t it be cool if I could hand-write some Periscope links to send people to one of my broadcasts? A friend’s broadcast? Or my profile? I asked Periscope about this 3 days ago on Twitter. No response from them.
I think if “deep links” could be more easily written and shared we’d see a huge increase in their usage.
Note: I found Rosenberg’s Medium piece via Jeremy Keith.
Edited for content and clarity on October 11, 2016. Essentially I removed my argument that they are poorly named and focused on the much more important issue with deep links; discoverability.