Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Should I Use Core Data or not?

I'm developing an application for the iPhone which gets all data from a database from a web service. I receive the information in JSON format and make constant calls to the web service for data. My question is should I be using core data? Right now I just make a request to the web service use the information I need and make calls to data when needed. But should I put the data into core data because I cannot figure if it would help or even make sense to do. Since there are thousands of rows of data on the server I can't imagine constantly saving information into core data in effect copying the database from the server onto the phone. That does not seem to make sense or be a good idea performance wise. Wouldn't I eventually run out of room in the core data database or use up too much room on the device? Maybe I'm not fully grasping the concept.

like image 801
Marlow Charite Avatar asked Dec 27 '13 04:12

Marlow Charite


2 Answers

In my opinion there is no use of Core data as per your requirement. As you are asking your web service, every time you need new data. Your App is a web App, not a native one. Better work on how to speed up communication by using efficient data objects (you are already using JSON, thats good.). No need of CoreData according to me. Here are the links supporting my point:

Why Core Data
Core data features overview

like image 165
Prince Agrawal Avatar answered Sep 28 '22 10:09

Prince Agrawal


Of all of the ways to persist data on the iPhone, Core Data is the best one to use for non-trivial data storage. It can reduce the memory overhead of your app, increase responsiveness, and save you from writing a lot of boilerplate code. According to Tutorial of RayWenderlich and Tutorial of Objc.io, you can get a good start. And personally, using Apple's class is better for version control for your iOS Apps.

like image 21
Danny Xu Avatar answered Sep 28 '22 10:09

Danny Xu