> where the Rails serves solely as a RESTful API Honestly I can't imagine not doing that, why wouldn't you? I'm not trolling, making the backend RESTful and i

> where the Rails serves solely as a RESTful API Honestly I can't imagine not doing that, why wouldn't you? I'm not trolling, making the backend RESTful and interacting with it only via REST calls is a great way to separate your data from your user interface. You can base mobile on this, web, or even legacy applications and reuse your backend service. So if you didn't do that, what model did you follow? I'll admit, I've flagged this post to read the article later, so if it's addressed in the article, I can read it there.