CloudKit Public Database as a Backend
summary
Uses CloudKit public database as the app backend to serve barcode nutrition lookup, ingesting Open Food Facts raw TSV and filtering 4.2M rows down to 2.7 million records of usable food items. A Mac uploader converts rows to CKRecords and pushes in batches of 150, with the full import taking 44 hours to finish. Barcode scanning uses VisionKit data scanner; CloudKit handles read-heavy static content well but limits relevance of search, offers no server-side logic, and is Apple-only.
AI-written summary · about
chapters (13)
- 0:00Introduction and background
- 3:16Why avoid a backend
- 8:10CloudKit public database overview
- 12:03Choosing Open Food Facts
- 14:12Filtering the food database
- 16:59Building the CloudKit schema
- 18:04Uploading data to CloudKit
- 21:18Production environment setup
- 22:45Barcode scanner integration
- 23:46Limitations with search
- 25:13CloudKit public database boundaries
- 26:39Costs and trade-offs
- 27:00Conclusion and final thoughts
related talks
41mSyncing and Collaboration with CloudKit
01h 13mChallenges of developing a client for cloud storage on iOS
38mClassKit and Schoolwork
14mBuilding a SwiftUI app with Firebase
31mPower-Up Your App With Apple’s Machine Learning Frameworks
19mPDFKit Basics
27mDocument Indexing and App Search in iOS
40mNeedle in a Haystack: iOS Search
