After last month’s Dropbox API review, we’re now publishing the conclusions of usability testing SoundCloud API. Tests have again been conducted by API Usability Testing, which offer remote API usability testing performed by a broad range of software developers with different experience and qualifications.
SoundCloud API usability tests were performed by developers with a range of experience of five to twelve years working with all the major programming languages. All tests were performed using Ruby on different platforms.
We’ve teamed up with API Usability Testing to offer you usability reviews for different APIs. API Usability Testing offer remote API usability testing where tests are performed by a broad range of software developers who have different experience and qualifications.
We’re starting with the Dropbox API and we’ll be doing it for other providers on a regular basis. Please get in touch If you’d like to see a review of a specific API.
The first implementable draft of HTTP/2.0 was released on July 8th by the HTTPbis working group of the IETF. The 2.0 version of HTTP is based on the SPDY protocol developed by Google — in fact, the initial draft was a copy of the SPDY specification as a base for diffs.
Photo by Jeffrey Beall
HTTP/2.0 is intended as an alternative to HTTP/1.1, rather than deprecating the old version. There is good reason for this: The new version feels similar to the old, but there are important differences designed to enable more efficient network communication.
Since Google’s announcement of Glass people have been wondering about the possible applications that can be built on it and how it might increase one’s productivity. Well, your wait is over now, because Google has recently released the documentation on how to interact with Glass through their Mirror API.
According to the documentation, the Google Mirror API “allows you to build web-based services, called Glassware, that interact with Google Glass”. Even better is the fact that this functionality doesn’t need that you run any code on Glass itself, since all interactions are done via RESTful endpoints.