Deep Web App Linking

I am passionate about making web apps discoverable and interlinked. It is one of the reasons why I created the very first Web Intents prototype and then worked on trying to get it standarised and implemented as WebIntents.

Web Intents as we know it today failed (it still hurts), yet I still think about it a lot.

In my recent post about SLICE I mentioned that inter-app linking is MIA on the web. It's a bit silly really, the web and web developers take pride in that we have the URL yet we don't actually use them well at all and it is hurting us.

A couple of things happened recently that got me thinking more about this.

These three things together really hit home something that I had been mulling for a while: It's impossible to link to a web app and it's our fault.

Today one of the biggest benefits that we have on the web that native platforms don't yet have is the ability to send someone to a link and they can use the thing that is there with zero install. Effectively we have a frictionless way to do app interop without worrying that the user doesn't have the app installed.

Sounds absolutely amazing. But we have a huge problem! When was the last time you found a web app that let you use it immediately?

Watch the following video and then I will explain more about what I mean.

This is the simplest case, 3DTin let's you use the app immediately and then only requires you to sign-in when an action such as Save is initiated. TinkerCAD on the other hand requires you to read up about their service, fill in a long (and slow) form and then finally once you meet all the requirements you can.

Product landing pages, Login pages and everything that is in the way of the actual web app is equivalent to an App Store install page. These pages kill what we value most about the web: The L and E in SLICE.

I get why we think we need to do it. You want to capture the user and get them registered on your systems and you need an "account id" to persist data.

My good friend Mike Mahemoff pointed out to me that this already is a known thing in Native App development circles. The concept of "tourists" (or "shadow users" as Facebook calls it). The idea it that when a user hits your service a proxy account is made that can then be converted into an official user once they sign up to your service.

Given the scale of the web and the number of users that can casually visit your experience and not have any commitment to it, "tourist" users might not be a viable solution but fundamentally we need to build sites and apps that don't block the user and encourage simple linking and frictionless usage of web apps.

Native Apps are exploring this area with App constellations (groups of interconnected apps) and I fear that whilst we have all the tools to do this on the web today we are not interconnecting our apps.

If we want to make our apps linkable then we will need to let the users use the applications instantly.

Image Credit: Ruby Gold

I lead the Chrome Developer Relations team at Google.

We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.

Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.

I love to learn about what you are building, and how I can help with Chrome or Web development in general, so if you want to chat with me directly, please feel free to book a consultation.

I'm trialing a newsletter, you can subscribe below (thank you!)