There's a lot to like about the Web Share API

I have a special place in my heart for online creativity tools. I tinker with them, share them with my kids, and build them myself.

One of the most important features these tools can have is frictionless sharing with other people. The best tools have a dedicated place to submit your creations and browse the creations of others (think Scratch explore or Dribbble shots). These community features are great but they’re relatively rare because it takes so much work to build and support them. At the minimum, you just need an easy way for someone to share their work with their friends.

One option is to add social media share buttons to each project page:

Share buttons for social media sites like Facebook, Twitter, and LinkedIn
Remember these? They're not just for blog posts. You can use them to share anything with a unique URL.

There’s a lot to dislike about these social media buttons. They look garish and they often require JavaScript embeds that include trackers and slow down your site with network calls.

And which social networks should you support? Do you clutter your site with a bunch of niche options (that most people don’t use), or do you encourage centralization by only promoting the biggest social networks? 😐

That’s why I got excited when I discovered a new approach with a lot fewer downsides: the Web Share API

The Web Share API is a new browser API for sharing content natively. Basically, a user clicks a share button and it launches an operating-system-specific dialog that looks something like this:

The Web Share dialog, as shown on iOS and Android

The Web Share dialog, as shown on MacOS

The Web Share dialog, as shown on Windows

As you can see, the sharing options depend on what the user has installed on their device. This is great because as the developer, you don’t have to care about what social networks they use—the list of options is always relevant. And if they don’t use social networks, no big deal—there are still options for things like texting, email, and copy to clipboard.

No ugly buttons. No tracking. No free advertising for social media giants. Are there any downsides to using the Web Share API?

Browser support could be better. It’s great on mobile but we’re currently missing desktop Chrome (on Mac) and desktop Firefox. There’s no fundamental issue with adding support… the developers just need to prioritize it. If you want to encourage them, go ahead and star this Chromium issue. In the mean time, you can use feature-detection to only show your share button in supported browsers (as shown on this test page).

Overall, there’s a lot to like about the Web Share API. It feels like a small step towards a cleaner, healthier web ecosystem, and that’s worth celebrating. 🎉

More resources: