One of my Apps uses a collection of data for musicians. I want to make the bulk of that data be an IAP now that it has grown to a decent size, but I don't want to take anything away from existing users. I have a theory but I wanted to check first.
I was thinking or creating a userDefault like a boolean called existingUser or whatever.
Then make that apart of a new update for like a week so just about everyone has a chance to update.
Then remove the code in a second update so new users don't have that boolean value stored but the old users do.
For the premium feautres to function it will check for the IAP only if the boolean value for existingUser is false.
Seems like that should work fine right?
I'm sure someone has done something like this before.