Comments on: pico projects

By: Jeff Lindsay

Jeff Lindsay — Tue, 14 Apr 2009 01:21:24 +0000

Matt, this is sort of what web hooks are about. Web hooks + API + pico apps = composable web.

Ariel, this is really cool. I’ve been thinking about this genre of applications from an infrastructure standpoint. I’d been calling them micro web services. Maybe pico apps?

By: Tarek

Tarek — Tue, 14 Apr 2009 00:45:44 +0000

I think the rise of Pico Projects is due to the introduction of new easy to use web development frameworks like Django, CherryPy, Rails etc. Also most of Web services have their own API’s and Widgets, so for me to give people the ability to have Avatars on my service, I can rely on Gravatar, on to let them upload files, I can use Amazon Services (like Baconfile), and to grab their location from their mobile phones, I can rely on FireEagle and its mobile clients. So it is really easy now to focus on your main idea and outsource the other fancy features to external services.

The cool thing about Pico Project (beside the terminoligy itself) that they are dynamic, the one or two developers there are always ready to add new features to their projects upon request. But their main problem is that are lack the marketing experience, and sometimes if the only developer is more into Coding than UX, the interface and usability are not that clean.

By: Matt

Matt — Mon, 09 Mar 2009 18:39:15 +0000

It would be really cool if there was a way to link all of these together. It would be like having actually useful facebook apps without having to deal with facebook messing it up. Is there an API or some kind of framework that would allow interaction across sites?

By: freegabe

freegabe — Sat, 07 Mar 2009 07:44:57 +0000

Great article!
xoxo, gabe

By: Ian Gilman

Ian Gilman — Sat, 07 Mar 2009 04:12:19 +0000

True indeed! Here’s mine:

http://gimmeshiny.com/