Web Intents Proxies

I built the following few pages to understand the user experience of Web Intents/Action. I used Paul Kinlan’s JavaScript shim, which implements the current specification, but has only a barebones UI.

I picked the most well understood use case, sharing a URL and created a number of proxy pages to bridge-the-gap to real services as no publishers have implemented it yet. The proxy pages collect the Web Intent JSON objects and maps the data into the correct query string to call the required service.

Click the share or bookmark buttons below and select an option from the pop-up window. The shim is in constant development, I found it’s best to test its use with Chrome.

Web Intent proxies register by this page
SiteVerbType
Twittersharetext/uri-list
Facebooksharetext/uri-list
Linked-Insharetext/uri-list
Huffduffershareaudio/mpeg
Delicioussavehttp://activitystrea.ms/head/activity-schema.html#bookmark
Google Bookmarksavehttp://activitystrea.ms/head/activity-schema.html#bookmark
Clear your current Web Intents

Notes

UPDATED - As suggested by Paul I have change the bookmark type to point at the activitystrea.ms spec and changed the type for Huffduffer example to audio/mpeg

Bookmark is not currently a verb specified on webintents.org yet. I could have used the verb ‘save’ rather than ‘bookmark’, but saving a URL is bookmarking as far I am concerned. Using the most precise terminology for a verb rather than generalist terms provides a better call to action.

In the JavaScript I passed a number of metadata properties as well as the object defined by the mime type in this case a URL. I found that there are 4 common meta-properties required by these types of services URL, title, description and tags. This is not too surprising as these are the common meta-properties in oExchange.

The Huffduffer example brings up another issue, technically we are sharing a URL, but for the service to work correctly the URL has to point to a resource that is a mpeg file. More importantly I would not expect it to be listed with the same service that share URLs. At the moment I don’t believe the current specification allows for an acceptable UX for the Huffduffer example.

Links