Show HN: JSON CMS

I see two potential target groups here. One focuses on the developer and tries to solve the data storage and synchronization procedure. In that field, I'm not sure what the benefits of your solution are. Could you elaborate on how it is different to CouchDB[1] or even Amazon's storage service[2]?<p>The other market I'm seing targets users of the CMS system, i.e. the people who actually maintain the data. In most data centric projects I've been working on, you could be sure that the client will at some stage ask, how (not whether) he can change the existing data and add datasets after development has finished. This usually involved creating a CRUD user interface, which was tedious and in almost all cases, was never used.<p>Your front page focuses a lot on the former target group (create general datastructures, update and query them) whereas I think you might be offering more value in the latter group ("see how simple it is to add another recipe into your cooking app"). If you could combine the client's desire to control his money and time investment while making the solution easy to integrate for the developer, that might be good enough.<p>[1] CouchDB for iOS devices - <a href="http://news.ycombinator.com/item?id=2310863" rel="nofollow">http://news.ycombinator.com/item?id=2310863</a><p>[2] Amazon S3 for iOS: <a href="http://aws.amazon.com/sdkforios/faqs/" rel="nofollow">http://aws.amazon.com/sdkforios/faqs/</a><p>[3] Earlier discussion on StorageRoom: <a href="http://news.ycombinator.com/item?id=1847115" rel="nofollow">http://news.ycombinator.com/item?id=1847115</a>

This is a nice idea.<p>We build a lot of mobile apps, and we use a combination of the Django admin, and django-tastypie. This gets a JSON API up and running with authentication in very short order, but a product in this space would be very welcome, especially as it allows the data model to be built with a GUI. Our programmers spend a lot of time on model development and being able to delegate that to less technical staff would be a big benefit.<p>White-label would obviously be a very strong requirement.

I think this will be useful for a lot of developers of iPhone/Adroid apps. Many don't have the know how (or time) to develop, run and maintain backend systems and it pushes the development cost way way up for clients and complicates our own applications.<p>We just integrated a purpose built CMS with a bunch of iPhone apps for a client and it was not a lot of fun so I'll give your product a try for sure.<p>As for feedback - the one thing with the UI is that having three different types of save buttons is a bit confusing at first but I'm not sure if there is a more efficient way to do it. Also, a big win would be if you added an etag along with the JSON with the location of the images to download. I do like very much that collections can be attached to multiple applications.<p>If your are ever in the Bay Area come by our weekly iPhone Meetup Monday nights in SF. (search iPhone in sf on meetup.com - our logo bleeds six colors...) or shoot me an email (profile)

I'm a little confused about why this is targeted specifically to mobile. I've been looking for a back-end only CMS for years now. Originally, I didn't mind just having my front-end share a database with my CMS, but it would be even better if it used a RESTful API like you've got here.<p>Maybe I'm missing something? The closest thing I've found to what I'm looking for is: <a href="http://www.pureedit.com/" rel="nofollow">http://www.pureedit.com/</a> and storageroomapp.com seems very similar (although much better) judging by the Introduction Video.

I definitely dig on the core concept of making it easier to get content to mobile devices. However, having done this exact type of work for an agency in the past, more often than not content was shared between web and mobile platforms. Do you have a plan to support importing content from popular CMSes or some other way of sharing data between CMSes?

Seems to be a good idea. You'll have to market this a lot to agencies building mobile apps (I would think). Easy tutorial etc.

I love this idea. Fantastic job. I'm going to give it a shot myself for an app I'm prototyping.

Clickable: <a href="http://storageroomapp.com" rel="nofollow">http://storageroomapp.com</a>

I like the idea, but I want have a lot more than 20GB available. I think it would be more inclined to buy this as traditional software (instead of SaaS).

I feel it can be very useful. How does it differentiate with MongoDB, CouchDB etc?