Create new com.snowplowanalytics.snowplow/user schema

[yalisassoon]

This is part of a set of upgrades for our mobile SDKs.

The schema should contain the following fields:

• userType
• subscriptionDate
• subscriptionType
• paymentType
• paymentFrequency

[bogaert]

We treat the subscription entity separate from the user entity in our implementations. It can also be helpful to add an optional field for the expiryDate.

[yalisassoon]

Thanks @bogaert - so to clarify - you'd recommend we called this entity "subscription"? (It looks like all the fields relate to the subscription...) Or would you keep userType as a user-level property, and move the others to a subscription entity?

[bogaert]

I'd keep userType as a user-level property (perhaps adding more optional user properties), and moving the others to a subscription entity. Separating the entities allows for a user to have multiple subscriptions.