Database options and app design advice

hi all,

start building database-oriented application company. have experience developing ios applications, first application using quite big databases , appreciate design advice.

purpose of app display , market inventory. inventory contains between 200-1000 items. each item has around 20-30 fields. inventory doesn't change often, change need update database on user's device every few weeks. can download csv file our server, pretty straight forward task, debating best way go storing database. planning build search engine well, want fast.

firs thing need decide database use. did research , narrowed down 3 options: sqlite, property lists, , nscoding (quite confused last).

way recommend? choosing database, architecture of app , objects, appreciated.

 

plists , nscoding same, or @ least related. while sounds have modest amount of data use sqlite project this. it's more scalable , use less memory , faster plist strategy. core data other option. don't use @ wouldn't use project. it's complicated learn.

data static? ever change on device?

ship pre-built database app , download updated database sqlite file server periodically. write downloaded db app sandbox, either in documents folder or application support folder, or perhaps caches. there's issue backups icloud have deal in case.

should possible build database using sqlite on mac or other oses read on device. can script sqlite command line tool build or edit sqlite db updates.

 

Forums iPhone, iPad, and iPod Touch iOS Programming

• iPhone
• Mac OS & System Software
• iPad
• Apple Watch
• Notebooks
• iTunes
• Apple ID
• iCloud
• Desktop Computers
• Apple Music
• Professional Applications
• iPod
• iWork
• Apple TV
• iLife
• Wireless