CODEWITHSUNDEEP
iosobjective-c
Alex
Alex

Reputation: 1233

iOS: Dealing with data and a large amount of views

I have a general design question for dealing with data. I currently am working on an app that stores about 100+ different unique properties (mostly integers, some strings) and am currently using a single object of a custom class to manage all of them.

I need the data to be "persistent" throughout the app so I currently pass the object via segues. I have managed to build 20+ views, most with their own view controller. I am very new to Objective-C and iOS development and have a feeling this is a bad practice.

I do not understand that much about core data and am not sure if it would be a better solution for me. I have also read about singletons and have heard mixed things about using them for this sort of solution.

In the future, I will need to permanently store the data that is held temporarily in the custom class I have written.

What is the best way to deal with this situation? Is it standard practice to pass the object around over many different views?

Upvotes: 0

Views: 62

Answers (1)

Fogmeister
Fogmeister

Reputation: 77641

If the data needs to permeate through the entire app then a singleton might be a good way to go.

In game dev there is a pattern called the chalkboard pattern that allows any part of the game to read and write to the chalkboard. This can be used for health points, scores, etc...

This would suit you well too. Rather than pushing your data model around all the time just use the singleton to access each bit/ If the data needs to be updated then store the updates to the singleton.

The thing to avoid is using the singleton just because its there. If a bit of data needs to get from one place to another then don't just use the singleton if it isn't necessary.

Upvotes: 1

Related Questions