I'm making an app which will allow the user to purchase either a subscription or consumable which allows them to access data on a monthly basis. Once the new data for the next month is available they will download that and the previous data is invalid and actually illegal to use so it will be removed. So I'm not sure which to choose. A subscription model or a consumable model? From what I see either one would work. Any reason to choose one over another?
+1
A:
a consumable item, if the user makes a restore the item will not be restored. Whereas subscription it can be if it is still valid.
CiNN
2010-02-07 22:05:40
Yes, and since with the subscription I have to make a server that keeps track of all that the consumable is easier for me. I'm kinda leaning towards a consumable, since that's more or less what it is in my mind.
jamone
2010-02-08 00:36:43
+2
A:
I'd go with consumable in this case. Although it sounds like a monthly subscription model, it is not as the access to the previous item essentially runs-out or is consumed. The consumable model makes more sense.
Plus from a developers point of view, not having to make the content available across multiple devices (a requirement of the subscription model) can make things a little easier.
Eoin
2010-02-08 01:20:11