I’ve used EE many times in the past for making websites. As a front end developer I love how easy it is to customize to get exactly what I need.

I’ve recently started making iPhone apps and have an app I’m about to build that will require constant fresh content without having to submit updates to the app store. I need a CMS. Using EE the data could obviously be delivered to the app using JSON.

The main reason I want to use EE is that as I’ll be getting other people to enter all the content, I need the interface to be super easy to use and customize to minimize the risk of any mistakes.

The main reason I’m hesitant about using EE is that it seems like it may be overkill. It’s a huge system and maybe not very well optimized to this type of usage.

Does anyone have an opinion on this?

Thanks, Mark.

EE’s as fast and as big as you make it.

Can do small tasks like this easily, or can scale to bigger jobs.

I think it’s very easy for a client to use - and the cpanel is easy to section off so I’d say yes - why not.

If you do choose EE I’d add a bit of template caching to the JSON for speedier updates, deliver all files gzipped and minimise queries as much as you can - there’s some great documentation about streamlining EE.

I’ve been working on just such a system, using EE to manage data that’s pushed to an app via JSON. Works as expected, the app owner can updates content, and also end users can submit new content.

Thanks for the feedback guys. Helpful and much appreciated.