Re: [w3ctag/design-reviews] Web Share API (#170)

Hi Matt, thanks for the response. My concern about service specific metadata arises from use cases where services would retain a strong incentive to get developers to implement a custom share button rather than integrate with the web share api.

For example, twitter offers lots of metadata properties on a share, including tagging other accounts, which is obviously definitionally service specific. I'm aware of several large orgs that use that feature, because it helps them build engagement around their own account.

So there are a number of options here. There could be an option to pass namespaced custom properties into the share action, which would make sense to only one share service.  Or some "borderline" cases could be absorbed into the standard as you suggest. Or maybe there's another solution or one isn't necessary. I just wanted to flag the potential for this to be a brake on adoption.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/170#issuecomment-305703892