jeffbcross

lukekarrys, how long would it take you to build this?

What do you have against TODO-lists? IMHO the world needs more varieties of task management tools.

Actually, the example apps don't really do the platform justice. We (at deployd) use it in consulting projects for building big APIs with complex roles and business requirements. The design of deployd is driven more from lessons learned designing those APIs than from our experiments in TODO-lists.

(I work at deployd) Yes, it's perfect for prototyping. We use it extensively for prototyping on projects where the ultimate API has to be supported in another stack. Saves tons of time compared to developing the API as you go in Java or the like.

We're working on updated content for the site, and details about the underlying stack and requirements for self-hosting will be more prominent.

The site's up now.

(I work at deployd) Yes, the cycle is funny. We don't usually focus on the GUI when talking about deployd; someone outside the company posted with this headline.

Open source was a no-brainer for us. There are some other key concepts that make it a compelling tool, particularly how easily extensible the platform is.

You can, it's open source. The environment just needs to support Node and Mongo.

We made it open source so anyone can run it anywhere. We and others have deployed it to EC2, Heroku, Joyent, Azure, Koding, and I'm sure some others.

With MongoDB, there's a concept called Sharding, that divides a collection based on a property in the collection the developer selects.

http://www.mongodb.org/display/DOCS/Sharding+Introduction

Each shard can be either a single node, or can be divided among nodes in a Replica Set for distributed reads.

http://www.mongodb.org/display/DOCS/Replica+Sets

Not an untypical predicament you're in. Best advice is to minimize features and release something to someone asap. That takes a lot of discipline to do, but starting simple and iterating has lots of benefits. Just a few: 1. Instant feedback, so you can validate your assumptions about the product. (see: Lean Startup, Eric Ries) 2. It's easier to keep releasing once you've already released. 3. With a simple, limited feature set, your product is easier to understand to your early adopters.

Yeah, androids can endure the lengthy flights without getting bored...unless we make them too human-like.

This is probably your best bet https://twitter.com/#!/nReduce

I know... get the timezones right, people; it's not rocket science!

There are some nice new tools emerging to solve this problem, but don't force front end devs into an entirely new platform. One of my projects is an open source server (https://github.com/deployd/deployd) that's totally un-opinionated on the front end, but makes it really easy to add robust backends to client apps.

I was thinking Apple had this technology patented...maybe they have a licensing agreement that requires use of App Store.

If it's any consolation, Chord Buddy was my first thought :).

Is it open source? If so, I'd love to check it out. We've been working on an open source server for JavaScript developers, that has some of the modularity of Wordpress: https://github.com/deployd/deployd