From the developer’s perspective
Geckoboard is a platform. Therefore, it’s very interesting to hear from the developer’s point of view. Jonathan Foucher is the one who worked on this integration, here’s his says about it:
Developing widgets for Geckboard is easy and flexible. This is how I developed several widgets for Mailjet in a few days.
First of all you have to read the geckoboard docs to find out the format in which each widgets accepts its input. Then, you’re ready to get started. At Mailjet, we have a single function that returns most of the statistics for an account, and 3PW makes it really easy to adapt it in the format that each widget type expects.
The widgets are made of only two files : a JSON manifest file that specifies some basic info about the widget and its author, and defines one (or several, I haven’t tried that personally) data sources. These are the url(s) of your API that provide the raw data. XML and JSON are accepted.
Once you’ve played with it for a while, it is so obvious and intuitive that you start wanting to develop widgets for every API around!
OK, I think you’ve got the message: we love Geckoboard and we love to deliver actionable metrics. Some other integrations are on our roadmap. To be continued!