CODEWITHSUNDEEP
iosdesign-patternscore-datasingletonapplication-singleton
Keith Gibson
Keith Gibson

Reputation: 13

User info. Use singleton class or not?

My app will be used by one user. However, there will be a lot of user related info. So i have a class called User.h/.m and @property many fields. One one instance will be made of this class since only one user will be using the phone.

My question is,

1.should i adopt a singleton design pattern for this class? I don't want to continuously instantiate this class again and again thru out different view controllers.

  1. I'm saving all info about this class using core data. Having said that, does this compel one to use singleton more?

  2. is singleton design pattern the way to go? or should it be using external json file or plist?

Thank you

Upvotes: 1

Views: 262

Answers (1)

ekostadinov
ekostadinov

Reputation: 6950

Like @iOS Weblineindia said Singleton will do the job just fine. But if you think in different direction, maybe not. Did you consider that your User obj can have more than one Google (lets assume) accounts? How your app wil interact and deal with such social accounts?

Here is the real use case scenario - I have one account when I'm at work (mail, services, drive etc.) and separate one when I'm out of the office. I want them to stay separate. I'm in such position myself now.

Maybe if you hare some more information about your User class logic it'll be easy to answer.

Upvotes: 1

Related Questions