PUBLIC MARKS with tags api & mobile

But the W3C saw, or was made to see, the writing on the wall and built a set of standard APIs into HTML5 for just this case and most modern browsers have picked it up. The draft for the spec is http://dev.w3.org/geo/api/spec-source.html if you want to read it through or need further info. The API is pretty marvelously simple. This implementation changes the URL to return latitude and longitude when they are available, which we can use in our Django view. Plus, the same code works on mobile devices (at least the iOS ones I carry) with no changes.

The W3C Resource Timing API provides an expanded set of events for capturing individual resource timings on a page, which is essential for deep analysis. However, this API is still in the early design stages and there seems to be a lot of ongoing debate about how much information can and should be exposed through JavaScript, e.g., for privacy reasons.

GeoAPI services include a reverse geocoder; deep data about 16 million businesses and tens of thousands of points of interest; a writable layer for developers to annotate the world and do complex geo-queries; and location-enabled media layers (e.g., Twitter and Flickr). We've also recently added an iPhone SDK to speed up mobile development.

It's also possible to create some APIs that would tell a website how much bandwidth is available to it, so the developer could adjust its features accordingly. This idea is being tossed around between web companies and operators, but I don't know how much is actually being done about it.

It's the ecosystem, stupid The success of a developer program is not driven just by the beauty of the APIs or the store, but by how the overall ecosystem works to enable developers to prosper.

One place I see the desire to separate the two webs is in geolocation. Location is often billed as the next killer-app of the mobile world, and people generally assume that it is a feature that will be bound to mobile devices.