We used http://middlemanapp.com/ http://middlemanapp.com/ to build http://pollev.com/ http://pollev.com/ (view this on a android or iPhone). Our entire mobile w

We used http://middlemanapp.com/ http://middlemanapp.com/ to build http://pollev.com/ http://pollev.com/ (view this on a android or iPhone). Our entire mobile website compiles out into 3 files: JS, CSS, and a tiny html file. This works out awesomely for a few reasons. First, our deploys for our mobile app is just rsync. No fancy cap scripts. Second, its super easy to put the mobile app behind a CDN. One wrinkle in this approach is how to deal with dependencies between the Rails API and a completely separate JS app. We hack around that be packaging up our mobile app as a rubygem so that we can manage the dependencies through bundler. I highly recommend this approach. Its a great way to separate out an API team from a front-end app team. All of our future apps are going to be written this way, including an HTML5 rewrite of all of our visualizations (from flash). We plan on writing up a bunch of blog posts on the workflow, so stay tuned :)