In relation to the "Entitlement Code" examples given in the WWDC 2020 "Architecting for subscriptions" video (here), we plan have a couple of differences in our app, and have some questions about best practice.
We intend to offer monthly and annual subscriptions.
And we intend to offer different levels of subscription (for example: personal / professional / elite), which can all have both monthly of annual subscriptions.
Is it recommended therefore to add more digits (i.e. "4.1.1" or "4.11") in order to cover these different product variants?
Or should the 2 digit (i.e. "4.1") structure be able to cover all our possible subscription states for all our subscription periods and product levels?
If so, do you have a recommended approach to this?
Thanks in advance,
Adrian
We intend to offer monthly and annual subscriptions.
And we intend to offer different levels of subscription (for example: personal / professional / elite), which can all have both monthly of annual subscriptions.
Is it recommended therefore to add more digits (i.e. "4.1.1" or "4.11") in order to cover these different product variants?
Or should the 2 digit (i.e. "4.1") structure be able to cover all our possible subscription states for all our subscription periods and product levels?
If so, do you have a recommended approach to this?
Thanks in advance,
Adrian
