Why prototype an application before building it? The common answer to this question is well known: to get more accurate requirements. But what’s behind this? Does a project that develops a prototype produce better requirements than one that doesn’t?
Google Livable was a prototype I built with the Google team at R/GA. The idea was to use the Google Places API to give a score to a specific area.
It was never actually released but the prototype won an AICP Next Award. Here’s a video explaining the idea:
Miyamo was my first real production iOS app. I was the Technical Lead for the development team. We built an iOS app as well as a Facebook app. The idea was that it would read your music listening tastes and create a flower that represented it. It was released in the app store in Mexico and nothing really happened to it since. But it worked great and looked beautiful.
A post a wrote a couple years ago. I thought I invented something cool, turns out it was already called “Rubber Duck Debugging”
Since I started working at R/GA I’ve been working on the Nike+ platform off and on. From 2005 to 2007 I was on the team that built and launched the first version of Nike+. I was a technical lead and backend Java developer building the services the Flash front end used. I also spent time working with Apple on the integration with the iPod and iTunes as well as how to secure the communication.
A few years later I also worked on a major Google Maps integration with the site.