Home/ Questions/Q 6245819
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T12:34:35+00:00

I’m developing an iOS application which deals with constantly changing data which is read

  • 0

I’m developing an iOS application which deals with constantly changing data which is read and written to through a web-based REST API.
I want some data to persist throughout the app’s lifecycle, but I also want it to be reset and reloaded when the user quits the app.

Should I user Core Data for this? If not, is there a simple way to persist data throughout the app’s lifecycle (eg. a singleton class?). What would you guys recommend? Are there benefits to using Core Data? I want to avoid Core Data if possible as it’s a pain to set up.

Thanks in advance

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Core Data isn’t about saving data, Core Data is about modeling data during runtime. Persistence is just an option. If you have no interest in persisting the data to disk, just use Core Data with an in-memory store.

    • 0