Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I'm currently in the process of learning iOS Programming by creating a small game. This game is going to be a sports management style game which will mean there's a hefty amount of initial information that needs to be included in the app. For instance, Players, Clubs, Countries; all of which will be pretty large and will be relational.
From there I'll need to store the state of that data when a user saves, for instance a player may have changed club in the save and so the data in that particular save will be different from the initial data.
I've been looking into pLists, CoreData and SQLite but I'm unsure of which to use or how to combine them? Potentially have initial data loaded into the app from an SQLite database and then archive the objects from there?
Any help would be appreciated.
I'll suggest you CoreDate for keeping Players, Clubs, Countries. Your model will be then relational, and it's quite easy to retrieve the infos you need later. For the game settings, user's score, you can use NSUSERDEFAULTS which allow you to store small data individually.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I am beginner to building Apps with React Native + Redux.
I am trying to create an App family budget. It's almost done.
BUT I have two questions for them who already created these kind of apps.
What is the best way to save data? I want to save it (data: expenses/dates/category etc) on devices iOS (not database) if it's possible. I think it does not take a lot of memory. I've read about AsyncStorage, but not sure about it. Is it still present after reloading App/Phone?
How to share data between two users? I want to make a function, like sharing the budget between family members.
I will be very grateful for the recommendations and suggestions, maybe even for some good articles with explanation.
Thanks!
If you are using redux, you can use redux-persist to store your state on devices.
To share data between devices, you probably need to implement a remote server (cloud), which receives budget changes and propagates them to other family members.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I'm developing an iOS app that is going to parse XML from an RSS feed of events and display the details of each event on a table view. Each event has a title, a description (optional), a date and a time. I am able to parse the XML data using NSXMLParser; however, I am not sure how I should store the data and make it so that it persists after the app is closed.
I have read that I can use NSCoder to persist the data but I am not sure if this is the best route forward.
Does anyone have any ideas or suggestions as to what I could do?
Any help is appreciated.
You have several options for persisting data.
NSUserDefaults are meant for user settings - small amounts of data. They seem unsuitable for what you have in mind.
NSCoding is quite a good way to store structured data without the overhead of a database, yet it is slow in comparison to core data.
Core Data is Apples ORM, which is quite powerfull but not as easy to wrap your head around.
I answered a similar question recently, which goes into more detail regarding NSCoding with a complete example and some links for further reading.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am developing an app where I am going to use NSUserDefaults to store some profile variables (name, picture, etc), I think.
I think I need to store some long huge lists of values for each user and I read about Parse and Core Data. What is the best? Can Parse replace Core Data?
What is useful on this case? Both?
Thanks in advance
Parse will store your data on their infrastructure on the cloud. You can enable Parse object caching to keep that data for offline use as well. For most apps I build, I avoid using CoreData (although Parse may be internally using some for of local store, could be CoreData) and use Parse explicitly with caching.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I want to create a searchable database in Xcode - for example, of different trees. The database would consist of the tree name, two images, price, and a short description. What is the best and most efficient way of creating such a database?
I am aware of: Core Data, SQLite3, and Parse. I am leaning towards SQLite3 but have not found a good place to learn how to implement this. Any suggestions?
Seeing as you are new to Objective-C and I doubt this will evolve into something need direct SQL I would suggest using CoreData. Although it is not technically a data base it is an object graph, it is built for exactly what you are wanting to do. Apple was even nice enough to build wrappers for everything you want to do.
CoreData to store your tree name, two images, price, and a short description.
NSFetchedResultsController for grabbing it.
UISearchBarController for letting the user search.
You would want to use Parse if you wanted to save your data to a server. If your doing everything locally I wouldn't worry about Parse. CoreData is what you want.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I'm trying to determine what would be the best route to go for an app idea I have in regards to using a back-end service or not.
The app will not require any sign up / log in steps
The concept does have a part of taking a photo. For example, a photo could be taken every day, or multiple photos per day, equaling 365 + photos.
I'd like for the user to be able to view these photos at any time, and possibly export them all at once in some form (if that is possible) at any time.
What's the best way of doing this to have a good experience in the app?
I supposed you'd define a good experience in terms of photo storage by being quick. You really don't have many options. You could either write 365+ photos into your documents directory or write them into a CoreData store. I'd probably opt for the CoreData store, because I have a feeling you're going to have some metadata associated with the image.
Really though, this question is a bit too specific to your situation. See also Best way to store images in iOS