More subscription stuff
This commit is contained in:
@@ -555,7 +555,8 @@ PRICING AND PLANS THIS IS OFFICIAL HERE REPLACES ANYTHING WRITTEN ANYWHERE ELSE
|
||||
- PRICING, must figure that out sooner than later, spend some time and give it a think, read joyce's docs keep in mind new licensing scheme worked up with joyce
|
||||
Once I have an idea run it past Joyce for final confirmation then shareit codes and purchase pages etc for website
|
||||
|
||||
5 days trial
|
||||
PERPETUAL = 5 days trial
|
||||
SUBSCRIPTION = 48 hours trial
|
||||
Flat price per license regardless of how many no discounts for bulk price to be xx.xx
|
||||
Includes 90 days support and updates after which they're on their own. In this way they don't feel coerced into a subscription which must be a turn off for a lot of people
|
||||
Separately they can purchase a support and updates subscription within 90days they get a discount of the ongoing price, after 90 days it's full price
|
||||
|
||||
@@ -30,8 +30,6 @@ THINGS HOLDING UP PERPETUAL RELEASE
|
||||
|
||||
WIP >>>>>>>>>>>>>
|
||||
|
||||
NEXT:
|
||||
todo: active users in terms of license data should not show in log only on boot but also in the about page (not license because it would confuse people) since it's relevant and we need to know it right away
|
||||
|
||||
Once the above item is done then move to testing:
|
||||
|
||||
@@ -40,6 +38,7 @@ todo: TEST subscription and perpetual license code
|
||||
Correct date range?
|
||||
Does a trial request for perpetual work?
|
||||
correct date range?
|
||||
Can I bump a trial subscription and / or perptual expiration date if a trialer needs more time!!! IMPORTANT, this way can keep it brief but allow for wiggle
|
||||
Does new boot code still work when no database?
|
||||
Does new boot code work to prevent running if wrong build or maint date expired vs build date?
|
||||
Does it prevent changing a user to active?
|
||||
|
||||
Reference in New Issue
Block a user