Core Data needs to know what to load

We need Core Data to load and save the fugitive information that we need to populate our detailed view. If you think back to DrinkMixer, we used dictionaries to hold our drink information and accessed them with keys, like this:

The problem with dictionaries and plists was that we had to store all our data by using basic types and get to this data with dictionary keys. We could have easily had a bug if we put the wrong type in the Dictionary or used the wrong key, causing lots of problems down the road. What we really want is to use normal Objective-C classes and objects where we can declare properties for the fields, use real data types, etc. You know, stuff you’re already really good at. That’s exactly what Core Data lets us do.