A client side service discovery and execution model.
JavaScript Python Shell
Latest commit b12e8a7 Oct 5, 2012 Paul Kinlan Issue #180 - cleaning up for Share intent
Failed to load latest commit information.
conf Fixes #118 - allow data to be sent on postError Nov 17, 2011
server Issue #180 - cleaning up for Share intent Oct 5, 2012
tools/chrome Fixes #171 - ensures the name of the project is the name of the project Oct 5, 2012
LICENSE Start of adding Licence #44 Jun 30, 2011
Makefile Subsribe fixes Aug 28, 2012
NOTICE Start of adding Licence #44 Jun 30, 2011
README.md Fixing up bookmarks and mememator assets Aug 10, 2012
SpecRunner.html first commit Jun 13, 2011
webintents.idl Fixes #128 - use postFailure instead of postError Jan 16, 2012


Web Intents

Web Intents is a discovery mechanism and extremely light-weight RPC system between web apps, modeled after the similarly-named system in Android. An Intent is an action to be performed by a provider. Intents provides a declarative syntax that allows providers to list the Intents they handle and a registration system that enumerates available providers. A client requests an Intent be handled, the User Agent allows the user to select which provider to use, and the provider performs the action of the Intent, possibly using data passed as input in the Intent. The provider may return data as output to the client.


To use today

No browsers currently support this API natively. To use this system simple drop the following code in to your site:

<script src="http://webintents.org/webintents.min.js"></script>

When browsers start to implement this natively the Shim will defer all its functionality to the native interface.


To register your service application to be able to handle image sharing simply declare an intent tag.

  type="image/*" />

This will register the current page's ability to share images.


To build a client application that can use the share functionality, it is as simple as using the following code:

var intent = new Intent(


When a service is invoked via startActivity, the "intent" object on window will be populated with the data provided by the client.


That's it.

To send data back to the client that invoked it, it is as simple as calling postResult() on the intent.

window.intent.postResult("something cool");


Prerequisites: Node.js: http://nodejs.org/ NPM: http://npmjs.org/ uglify-js: npm -g install uglify-js

./make all

This will build and minify both the server and client components.

Building Tools

The tools are a collection of all the apps and extensions that are currently live and available on the web.

./make tools

Building Apps

The apps are a subset of tools, are fully formed, live web apps such as cloudfilepicker.com

./make apps

Building Extensions

The extensions are a subset of tools and are fully formed extensions for browsers that support intents.

./make extensions


Prerequisites: AppEngine: http://appengine.google.com/ nginx: http://nginx.org/en/

To run the server locally:


The server will not be set up on port 80 or webintents.org so will need to do the following:

  1. Edit /etc/hosts - add the following " webintents.org"
  2. Start nginx using using the configuration in https://github.com/PaulKinlan/WebIntents/tree/master/conf