Saving Data in iOS

Heads up... You've reached locked video content where the transcript will be shown as obfuscated text.

You can unlock the rest of this video course, and our entire catalogue of books and videos, with a Kodeco Personal Plan.

Unlock now

Property lists and JSON are two interesting formats. You can think of plists as the outgoing format and JSON as the newcomer. Apple relies heavily on plists for a lot of things in your project, like the info.plist file when creating and extracting an application binary via the command line instead of Xcode. The truth is when it comes to performance, size and flexibility, JSON is the clear winner. Pretty much any modern web API you encounter nowadays will use JSON when returning data or information to you. JSON files are also more commonly shared and used than XML files nowadays. They're smaller in memory size, easier to read, and can handle just about anything you wanna store in them. We wanted to show you how to use both formats as Apple still uses plists and because Xcode can make editing and working with them really nice. If you plan to work on Apple platforms, then using plists over JSON is a valid choice. In reality though, it's rare to find anything but JSON nowadays, especially when communicating with web servers. In either case, you now have the knowledge to work with both. And Codeable makes it easy and seamless to encode or decode from either format.