Skip to content
This repository

A client side service discovery and execution model.

branch: appengine

This branch is 0 commits ahead and 256 commits behind master

Fetching latest commit…


Cannot retrieve the latest commit at this time

Octocat-spinner-32 assets Changing the logo to something self designed #72 September 05, 2011
Octocat-spinner-32 conf
Octocat-spinner-32 lib first commit June 13, 2011
Octocat-spinner-32 server
Octocat-spinner-32 src
Octocat-spinner-32 tests
Octocat-spinner-32 tools
Octocat-spinner-32 .gitignore
Octocat-spinner-32 LICENSE Start of adding Licence #44 June 30, 2011
Octocat-spinner-32 Makefile
Octocat-spinner-32 NOTICE Start of adding Licence #44 June 30, 2011
Octocat-spinner-32 SpecRunner.html first commit June 13, 2011
Octocat-spinner-32 webintents.idl

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=""></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: NPM: uglify-js: npm -g install uglify-js

Then, run make.


To run the examples:

./ start

Navigate to

To stop the example server:

./ stop


To run the tests:

python -m SimpleHTTPServer

Navigate to:

Something went wrong with that request. Please try again.