Aprove answer

Depending on your target you can specify the kind of resources you want to use. For images, you could for example images named:

  • alert_image_1_
  • alert_image_2_

And depending on your target, you could get the correct image by appending the name of it. So if you had a target called DemoApp, you could append that name to the image like:

  • alert_image_1_DemoApp
  • alert_image_2_DemoApp

And use that one. For custom messages, usually the .strings file is more than enough, so you can localise your application. For themes, I am not exactly sure what you mean. I am quite sure, based on what you said, that core data, wouldn't be necessary. Finally you can create a bundle, and based on your target, you can use the correct one.


For the third option, if you are going to actually store the data, you cannot use classes. There is an option of Core Data in iOS. It acts like a database containing much more features. Since its an embedded framework, works really fast and will answer to your most storage needs.

More Answer related to the Same Query


This all depends basically on type of data and its size. It may also depends on the ease of access.

1) NSUserDefaults is used to store some data which might be helpful for the user most of the times.

2) Plist file can be used as local store normally for average sized data.

3) Creating a class for common usage can be good. But if the size of data increases then it will be not good.

Other store can be by coredata and sqllite for large and relational data.

Hope this might help :)

Credit Goes to: stackoverflow.com

Related question with same questions but different answers