WeatherBug Developer Blog

In a recent interview between Jason Coe of AppModo and WeatherBug's own CTO Chris Sloop, AppModo readers had a chance to look underneath the day to day happenings of just what makes WeatherBug tick.

WeatherBug's Background and API

The first part of the interview discusses a bit of history on how WeatherBug came to be the company it is today, in addition to sharing some insights on why WeatherBug provides what some would describe as arguably the best weather data API options available for the world today. Sloop explains that the API was first launched in 2005 and today, is seeing over 15,000 registered developers requesting usage of the API data.

The move to Mashery

During the course of the interview, Sloop explains that the API move to Mashery was one made because it was the next logical step. Sloop explained that he felt like Mashery was offering a quality product, plus with the added requests being made to some of WeatherBug's latest API additions meant that Mashery would be in a position to provide the tools needed to handle these requests. Sloop goes on to explain that after looking at a number of other vendors, Mashery stood out due to its ease of implementation. 

Two new WeatherBug APIs

With the move over to Mashery, came two new API options for developers that provide some exciting new options for application development. The first is JSON API, which is designed to the equivalent of an XML-based feed WeatherBug has always had available. The second API available is a GEO-based API solution enables developers to add in new radar, satellite, plus a number of other cool layers over Google or Bing maps.

The future of WeatherBug API on Mashery

When asked about the future of the WeatherBug API on Mashery, Sloop responded with "We look forward to seeing how well our GEO and JSON APIs are received." He goes on to point out that as data is made available from developer feedback, the community will be among the first to know.