This story was originally published on HackerNoon at: https://hackernoon.com/ios-data-storage-classify-your-data-before-you-choose-a-database.
Learn how to design iOS storage by data type, using UserDefaults, Keychain, databases, Application Support, Caches, and sync metadata where each fits best.
Check more stories related to programming at: https://hackernoon.com/c/programming.
You can also check exclusive content about #ios-app-development, #ios-storage-architecture, #swiftdata-keychain, #ios-local-data-persistence, #ios-app-storage, #data-persistence-architecture, #first-data-synchronization, #hackernoon-top-story, and more.
This story was written by: @element. Learn more about this writer by checking @element's about page,
and for more stories, please visit hackernoon.com.
An iOS app rarely stores one kind of data. A travel planner stores six: preferences, secrets, domain entities, user files, disposable cache, and sync metadata. Five of the six get placed without naming a persistence framework at all, which makes the SwiftData versus Core Data question the last one to ask rather than the first.
▎
▎ Along the way: which accessibility class a Keychain token needs, why the ThisDeviceOnly classes are not about keeping secrets out of backups, which file protection class an attachment needs, when the system may delete your cache (never while the app is running), and what to do when the store refuses to open.
