I'm writing a simple iOS App to manage Email address, maybe like Contacts. I don't know what is the best way to organize data in iOS and don't know which database that iOS and Xcode support. I just know that iOS supports XML & SQLite, are there other databases supported?
Which is the best database (XML, SQLite,...) for this app?
If you are going to add only email and contacts then my suggestion is you just use plist.
http://developer.apple.com/technologies/ios/data-management.html
You should try CoreData. Have a look here to see what's it about. It offers a great way to handle the things you said you want to achieve.
CoreData is good option. The persistence used by core data is abstracted away while you can still choose SQLite, XML, or in memory for the persistent store.
Related
I have a SQLite database that I want my app to read and load into a UITableView then push to a Detail View.
I am using the FMDB wrapper framework (https://github.com/ccgus/fmdb). I'm confused as to how exactly to do this as I've never used SQLite in an iPhone app before.
Can anyone help get me started? What code do I need to add to I'm assuming viewDidLoad?
I think you should use CoreData framework provided in iPhone SDK. Its pretty simple to use and it manages most of the complex things for us. It provides a way to use Sqlite database as a persistent store for your application. You can just start with it from the documentation provided in iPhone SDK documentation under "Core Data Programming guide" section.
I have a universal app which uses simple pLists for data storage and would like an end user with both an iPhone and iPad have the settings/data synched. I think using DropBox may be the easiest way to do this.
I am wondering if anyone out there has successfully done anything similar to this and might want to share their experience.
Thanks,
John
Use iCloud .... its just perfect for your present problem.
What is the best way to store data for the iPhone? I will be developing an iPhone app in Objective-C which will take data from end users. This data will need to be save and loaded at various points.
Essentially, what is the best combination of languages and frameworks to use in order to develop the above (i.e. should I be aware of any compatibility or like issues regarding the objective-c language)?
EDIT: Are there any particular reasons why to choose sqllite over core data?
Hey, the best way to store and manage data is Core Data framework, you can read about it in official docs.
Two of the most popular and reasonable solutions:
Apple's native solution: CoreData
sqlite3
I used sqlite3 for my applications. If you use mySQL then you'll be very comfortable to use sqlite3. However, people recommend CoreData due to its ease of use and iOS support.
I would also like to add my vote for the CoreData solution. I investigated all the options (CoreData, sqlite3 and plists) and CoreData seemed to be the right option for me.
I found a brilliant tutorial on it for iOS 5 here
I am trying to build an Iphone App client for our CRM solution so our sales people would be able to access the information available in our CRM through an Iphone App.
I am trying to find out what is the recommended approach to architect the application when it comes to the database. I am not sure where should the data reside, should I save a subset of the data on the iPhone, or should I just rely on webservices and pull the information I need from the database whenever I need it. Also, is there any best practices or frameworks to build such applications on the Iphone.
The "best" solution from a data synchronization standpoint is work directly with the web based database, the "best" solution from a user experience standpoint is probably not that, due to latency passing data back and forth from the server.
If you do not have experience doing iPhone apps & you have no desire to learn Objective-C & would like to leverage web development skills I recommend a combination of phonegap + jqTouch.
Hope I helped.
Is your CRM based on Rails? You might find ObjectiveReference handy. It's an Objective-C interface into ActiveResources on a RoR site:
http://iphoneonrails.com
I am planning to develop an iPhone application heavily relying on sqlite DB ,
from different links I have gone through this seems to be a great tool and has some really good support.
As my app is still in the planning process
I would like to ask if there are any Issues with SQLlite database ? from memory management to Queries and data sizes and multiple access etc;
Please share your experience using SQLite DB in iPhone and what problems did you face?
I just want to make a note of these exceptions so that I may plan my App well and do not have any issues raised in the middle of the development process.
Thanx for your contribution.
If you are not looking to support the OS version 2.x or below I would (as the apple and may be the other developers) suggest to use the core-data. Its a lot simpler and easy to handle than sqlite. See the apple support and this sample for more help.
Thanks,
Madhup