I answered your questions, but I think you should probably change your questions. You guys have very specific assumptions of what a "project" is (when does a project begin and end? What if I consider an API integration a project in itself?) without making that explicit, so the answers you get are going to diverge wildly because of that ambiguity.
We were aiming for gut feelings, which is why we went with percentages in the poll.
These are definitely important questions that the poll didn't take into account, that we'll most likely need to address in the near future.
As for external services, we were really looking for anything you did to bring in external data, which could be anything from writing the connectors yourself to just loading a module and passing through some API keys.
Hey all, just wanted to give you a heads up. There are three of us working on this, I'm on the west coast, sick as a dog, and highly medicated, and the other two are on the east coast and already asleep. We'll reply to you all, but realistically it'll be in the morning!
We're trying to reduce the friction between applications and user content. In other words, to do away with all the unnecessary plumbing that most people build every time they want to access a user's 'stuff.'
That plumbing looks like a ton of CRUD-like operations that repeat themselves (auth, query, normalize into your own data dictionary, health check, etc.).
We're at first targeting content APIs (the 'stuff' mentioned above), trying to create a query mechanism so you can do broad queries with a user, without needing to know or care about what endpoints the user's stuff resides in. i.e. get all photos tagged dog, regardless of whether those photos live in facebook, flickr, picasa, or some other web service you've never heard of.
We're having a blast and even have the photo bit work.