API Updates: Android SDK, GitHub and JSON Support

We've been working hard at improving our API and just wanted to share a few of our recent changes to our developer site with you. First, we've added a new code library for....... Android! That's right, our first mobile library is ready for your mobile applications. Use our Effects API to power your app's photo editing, whether you're looking to provide your users with fun filters or utilities like crop and red eye. You can find the documentation and code in the brand new Android section.

Here are 2 sample screenshots from an Android app built in house

Speaking of code, we've also moved our libraries to GitHub for easier code management by us and code downloading by you. You can check out our profile and libraries at https://github.com/aviaryapi. We've also linked to some user-contributed libraries for node.js and ColdFusion so if you write your own wrapper, please do let us know and we'll add it to the list!

For those of you hackers who are too cool for wrappers or libraries and prefer to access the REST API directly, we've added JSON support to all our API calls. Simply add the parameter "response_format=json" to the querystring of any of your API calls and you'll get a JSON response. To that end, we've updated our documentation to include sample responses in both XML and JSON.

We've also generally revamped our documentation to improve both formatting and content. Reading through the old documentation, we realized that lots of things were not quite as clear as they could have been and we apologize for that. We think you'll find the new docs a lot easier to read and understand.

Lastly: don't forget about our API contest, which ends tonight! Submit your apps while you still can!

Why sharks dont have laser beams

want and need. I want a big-screen, surround-sound home theater system that can be controlled by an iPod Touch. However, I realize that all I need is a dedicated 20Mbps symmetrical fiber optic line to my house and a computer to access it on. See? Its simple!

However, the line between want and need can get blurred when an item in my want column suddenly goes on sale. For example, the iPod Touch that I want is currently out of my range at $300. If for some reason, Apple would decide to slash prices on the coolest MP3 player in history and suddenly make it $200, that want becomes an Itch. Make it $150 and - boom - now I need it!

At this point you may be wondering, "OK, you like toys but are too cheap to pay for them. So?" Well, building software comes down to a lot of the same choices and thought processes as buying crap. The touch-screen, refrigerator mounted, tablet PC becomes a feature that you may or may not implement. On the one hand - it's cool and some of your users may love it. On the other hand, many of your users won't care and implementing this cool feature may push your release date back a few weeks.

Sometimes, we have the real world equivalent of a sale: The situation changes making it more practical and inexpensive to implement a wanted feature. Scenarios include user feedback, competition or a technology breakthrough... anything that lowers the cost to (or raises the price of not) adding the feature. Suddenly, the want becomes a need and will make it into the next release.

The fun part - at least for the coders, is the actual design and implementation of the feature. Careful consideration of methodologies employed in producing the feature comes into play and this is where the programmers are supposed to shine. A good programmer keeps a need from sliding back into the want column, by making the most functionality using the least amount of resources possible.

So the next time you wonder why every household doesn't have a floor-washing robot, your favorite mp3 player doesn't have an FM radio or why your online word processor can't handle outlines, think about whether those products or features are actually needs or merely wants and you can understand why they were included or left out. At the very least, it will help you crystallize an explanation to your spouse as to why you need a PS3.

]]