11

I am developing an application that needs to perform expensive calculations at start up. So, the first time the application runs, the application do the calculations and store the result in a file.

If the user decides to uninstall the application and to re-install it later, the calculations have to be done again and I would like to avoid to re-calculate. Notice that I am not talking about updates of the application but about uninstall / re-install.

I was wondering if there is a way to persist data accessible only for my application but that can survive uninstalls.

The solution can be inside the device (using kind of files / preferences / ...) or based in a server. For example, a possible solution could be to send the device id with the result to a server and to store it there, but as the device id has been deprecated in iOS 5, is not a valid solution anymore.

Thank you for your answers.

Jaime

masta
  • 113
  • 1
  • 4

5 Answers5

11

You don't say how much data, but the following would be options:

  • iCloud
  • Keychain
  • Dropbox

The only "universal" option, that all devices will have and that cannot be disabled, is the Keychain though you are limited by the amount of space you can use.

Personally, I would do nothing. If the user deletes the app I think it's fair game to have to recompute stuff on reinstallation.

Stephen Darlington
  • 51,577
  • 12
  • 107
  • 152
  • 7
    Doing nothing is a valid option that many forget. Just because you do nothing does not mean you have not considered the problem it just means that nothing is the best or most practicable solution to the problem you are facing. I love suggesting nothing as a solution. Great time-saver. – Damo Apr 13 '12 at 09:32
  • UIPasteboard, could be a alternative – CarlJ Apr 13 '12 at 09:40
  • Thanks for your answers. I agree with you that doing nothing is a valid option and even the best in many cases, what I did not write in my question is that the cost of the calculations can be economical also, so to have to calculate twice the initial data is twice expensive in terms of money – masta Apr 13 '12 at 09:56
4

The way I have achieved this to date is with the keychain. Basically anything that complies to NSCoding can be stored in the keychain. It's a good idea to use the keychain sparingly even if only from a 'good personal practice' standpoint. After all once it's in the keychain it is there until you specifically delete it and presumably only your app will know the key to use to access the data you store.

A really good starting point for implementing something which stores data structures into the keychain can be found on the Use Your Loaf blog here by Keith Harrison.

In summary, this is the only transparent method I know of that can guarantee persistence of data past an uninstall. Other options such as 3rd party repositories (Dropbox) or iCloud do rely on some level of user participation.

Damo
  • 12,840
  • 3
  • 51
  • 62
1

Keep in mind, that Apple wants it this way: removing an app means removing all data of this app. I would prefer iCloud to save small amount of data.

Tobias
  • 1,220
  • 17
  • 35
0

Let the user connect to their DropBox account and you can save the data there - their API is really straight-forward to use, and you won't have to worry about how Apple may decide to implement data persistence in the future.

SomaMan
  • 4,127
  • 1
  • 34
  • 45
  • Thanks, the only problem I see is that the functionality of my application is depending on the fact that the user has an account on dropbox, isn't it? – masta Apr 13 '12 at 10:00
0

One option apart from the keychain and iCloud is Apple's UIPasteboard. Here is the class reference. Some people think it unreliable, so it depends on how important data retention is for you, I guess.

Suchi
  • 9,989
  • 23
  • 68
  • 112