I build apps all the time and while preparing for our recent webcast, From Napkin to App: Rapidly Prototype and Build for Mobile, I built out an Adobe Illustrator file that has all sizes of icons and background screens for various iOS and Android devices. I thought I'd share this collection of pre-sized artboards to use as a template for designing app icons and launch images. It will hopefully save you some time for the tedious task of sizing all your icons and launch images for various mobile devices.
We wrote an API design book! In 2009, a couple of my fellow Apigeeks (@earth2marsh & @gbrail) and I were frustrated with how many bad, inconsistent Web APIs we encountered in the world. So, we started cataloging the bad (and good) things we saw people doing to other people through API design. After three years of discussions, presentations and implementations with technologists all over the world (online & in real life), we are happy to announce the beta version of a new eBook.
Last week I flew from Doha, Qatar to Brussels, Belgium. The fella in the aisle seat fell asleep before takeoff. The road warrior code of chivalry indicates one should never wake a fellow traveler.
So I stayed in my window seat for 8 hours. After a few minutes it became obvious that my armrest (singular, my neighbor had usurped the other one) was uncomfortable. The armrest has many problems. The biggest: you can't rest your arm on it. So, why does such an obviously bad, pain-inflicting design make it into the world? And what does this have to do with REST APIs?
Last time, we looked at why you might consider complementing your API with an SDK or code libraries. In the series so far, we've covered a lot of tips and tricks for designing pragmatic RESTful APIs.
You may be asking - How do I follow all these best practice guidelines and still maintain and iterate my APIs? What should I be thinking from an architectural perspective in terms of implementing these best practices?
Add an API virtualization layer ...
So far in the API design series, I've looked at best practices for designing pragmatic RESTful APIs. This time, I'll talk about complementing APIs with code libraries and SDKs. What to do when building a UI requires a lot of domain knowledge?
In this post in the series, let's think about how app developers use that API you're designing and dealing with chatty APIs. Imagine how developers will use your API. When designing your API and resources, try to imagine how developers will use it to say construct a user interface, an iPhone app, or many other apps.
We've covered singular vs. plural nouns to label your resources, tips for search, handling errors, and more. Now lets take a look at what some API requests and responses look like for our dogs API.