Hello,
I am working on a subscription based tab-bar app. I have been looking into CoreData but believe that is overkill to store one UNIX timestamp for a future date. I have started to look into NSData to write a simple text file. That seems like a logical approach given the single value I need to store, but my concern is the update process. If I develop a program that stores a unix timestamp in a text file, will that just get overwritten when the app is updated? Anyone have a suggestion for a better method?
FM
I am working on a subscription based tab-bar app. I have been looking into CoreData but believe that is overkill to store one UNIX timestamp for a future date. I have started to look into NSData to write a simple text file. That seems like a logical approach given the single value I need to store, but my concern is the update process. If I develop a program that stores a unix timestamp in a text file, will that just get overwritten when the app is updated? Anyone have a suggestion for a better method?
FM
