New to Rails 3? Check out the Ruby on Rails 3 Tutorial book and screencast.

A book and screencast series showing you how to develop and deploy industrial-strength Rails apps in a direct, step by step way. The screencast series includes 12 lessons over more than 15 hours! Get the best "over the shoulder" experience of following what a top Rails 3 developer does when building an app today. Click here to learn more.

ObjectiveResource: An Objective C port of ActiveResource puts the iPhone on Rails

In Miscellaneous

iphone-on-rails.png ObjectiveResource (or Github repository) is a framework for iPhone developers (or, conversely, Rails developers who want to branch their app out to the iPhone) that allows you to interact easily between iPhone and Rails apps.

In essence, ObjectiveResource s a port of Rails' own ActiveResource - the library that enables RESTful communication of model data between apps. In this way, OR makes it easy to interface iPhone and Rails apps (or other apps that support an ActiveResource-esque protocol) in both directions.

There's a 6 minute screencast to bring you up to speed along with some brief Getting Started documentation. A sample application is provided that enables you to be up and running quickly, especially since it includes both an iPhone app and a Rails app.

If iPhone development is your bag, or if you're just curious, and you want to stay on top of iPhone developer news, check out MobileOrchard, a sister site of Rails Inside that focuses on the iPhone and iPod Touch development community.

Post to Twitter Tweet This Post

Vaguely Related Posts (Usually)

2 Comment Responses to “ObjectiveResource: An Objective C port of ActiveResource puts the iPhone on Rails”

  1. #1
    JT Says:

    Just a small style guide request that would help for clarity. If you are going to use an acronym (such as OR for ObjectiveResource, please put it in parentheses after the first use of the full word.

    In the second paragraph of this post, I was briefly confused by the line "In this way, OR makes ..." thinking OR was some kind of bit OR or something like that.

    I think if you had started the story "ObjectiveResource (OR)..." I would have picked up your acronym quickly.

    Love your work! I swear I'm not trolling!

  2. #2
    Peter Cooper Says:

    Thanks for the pointer. I do try :)

    In this case it probably would have made more sense just to stick with ObjectiveResource since it's not known as OR - I was just using it as a handy shortcut.

Leave a Reply