A phone screen asked how you design data models on the backend and how you handle them on mobile. If you use the server's response JSON structure as your local database entity as is, what goes wrong when the response format changes later?
The server schema changes for the server's reasons, so using it as your entity turns every field change into a local migration, and storing a nested response as it arrives duplicates the same object in several places and they drift apart.
PersistenceShort answerIntro
A new iOS project has to store a favorites list, the login session, downloaded PDFs, and…
#swiftdata
PersistenceShort answerBasics
Which requirements push you to Core Data (or SwiftData) instead of UserDefaults or a…
#swiftdata
PersistenceShort answerBasics
Say you're building a to-do app with SwiftData. What do @Model, ModelContainer…
#swiftdata
PersistenceMultiple choiceBasics
Select all the correct statements about SwiftData.
#swiftdata