Symphony.

I was very curious about this other thread when talk started coming up about working with iPhone development. I downloaded Appcelerator and was messing around with it for awhile yesterday. I was wondering though, how would you guys end up working with Symphony to deliver content into something like Appcelerator?

Would you end up using just basic html pages with forms? Or would you use something like Nick’s REST API? Or simply making get/post requests and whatnot?

Sorry, still trying to figure all this out. Thanks,

@TheJester12: There are really a number of options for how you might use Symphony to power a Titanium-built iPhone app. For the project we’re working on at the moment, we needed the entire app to be offline, so we built an alternative version of the site that responds under a different URL and then wrote a crawler in Ruby to save the pages and their assets to static files for use in Titanium. It’s a fairly simple app that combines WebKit views with a JavaScript “database” for instantiating the views within Titanium.

You could, however, use the Nick’s REST API or write a custom frontend API for fielding requests from your iPhone app. That API could either be used continuously or you could potentially make a single request and then update a local database—Titanium supports SQLite—with the new information.

Thanks, considering how little I know about actual Symphony programming, and actually coding for any sort of mobile phone, I feel a bit like I’m falling into the rabbit hole. But it seems quite fun!