Question

I’ve been reading up on saving objects, preserving state etc, but I’m still a little confused on the route I should take when saving objects that are created from my app. I have built an app where a user can create a Radio Station with the Genre, name and frequency. Once a user hits save, a “RadioStation” object is created using a custom class and is stored in an NSMutableArray that is placed in the RootViewController. While RadioStation objects can be stored in this array and are displayed correctly in the table view, it’s obvious that once the application quits, these are no longer going to be held by the application.

At this point I’m not sure how I should begin to architect this design. Do I need to set up a plist? Should I use Core Data with a SQLite DB? Do I need to research iOS object serialization for both these scenarios? Or is there an more straight forward way that I’m not aware of?

Answer 1

The most powerful approach is to make your custom object a subclass of NSManagedObject, and store it in an NSManagedObjectContext using Core Data. On iOS this will always use an sqlite database, on Mac OS X you can use sqlite, xml, or a proprietary binary format (smaller/faster than xml).

Depending on how complicated your data structure is, and how likely it is to change in future, this technique may or may not be too complicated for your app. It’s a lot of work to setup, and the API is very complicated, but it’s the best choice if you need to store tens of thousands/millions of objects in a file.

For your app, I would have a single sqlite file containing all of the radio stations in the app.

---

The simplest option, is to implement the NSCoding protocol in your custom object’s class. Documented here:

http://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/Archiving/Articles/codingobjects.html#//apple_ref/doc/uid/20000948-BCIHBJDE

The basic theory is your object writes or reads all it’s data to a “coder”, and then passes the coder on to any child object(s). Outside of the class, you use an “archiver” or an “unarchiver” class to coordinate everything.

Once your custom class implements NSCoding you can read/write it to the disk with:

myObject = [NSKeyedUnarchiver unarchiveObjectWithFile:filePath];
[NSKeyedArchiver archiveRootObject:myObject toFile:filePath];

This is a very simple approach, but it has a few drawbacks, for example you will need to figure out your own way to support different versions of the file format (perhaps with a different file extension for example).

Many classes in Cocoa/CocoaTouch already implement NSCoding, so they can be written to a file in this fashion (including NSArray, NSString, NSNumber, etc).

For your app, i would use this to store each radio station in a single file. When the app launches, load all the radio stations from a directory. You should consider enabling iTunes drag/drop filesharing for your app, so users can easily share radio station files with their friends or between devices.

This would also fit in well with iCloud for syncing between devices, I haven’t looked into iCloud much, but I expect one file per radio station will be the ideal way to implement iCloud syncing.