[jporta]

I don't see any obvious benefit in using it.

Relying on the the platform to handle the user authentication and document storage is something I wouldn't be comfortable with, though I'd use it as an option (as facebook connect, google or any other authentication service out there).

In general, I think this would have been a hit 5 years ago. Now, with services like heroku, phpfog, app engine, even github having free plans, the "hosting" part seems to be solved, and something pretty similar can be done these days with some sparkle from FB Connect and a bit of rails/php for the client side storage.

Don't get me wrong, I like this kind of services because [I think] they push innovation in different directions. It's just that I think there are a few pretty well stablished and provide similar (or equivalent) functionality and I just don't see any obvious advantage between this service and the others, though I see a few drawbacks.

[mckoss]

Good feedback. What I'm aiming for (and trying to see if there are others that this resonates with), is a higher level of abstraction for HTML5-centric application development.

There's a lot to learn to build applications that span database/web server/client - so I'm trying to build a "generic" backend, and let the application developer concentrate on the client side only.

Maybe it's really only applicable to "toy" or "prototype" applications. Like this one, for example:

http://wiki.pageforest.com/

[drcode]

Sure, all those services let you write server code for free, but why write server code at all if you don't have to?

[jporta]

Because I can. No, seriously, I didn't mean that server code should be written. You can use those services to serve static pages as well.