Leaderboard

On charging for updates to XP12 there are two sides to that. If developers do not update their product then they will have nothing to sell going forward. Sales of XP11 only product once XP12 is released will likely plummet There’s a balance between providing a service for existing customers in providing the update and using your existing client base to fund making your product sale able to new customers. If developers do charge a fee will they be transparent about the work that was needed to justify the charge? My view is the developers with older product, say the IXEG 733 (I know its not in the Org store) would have a case to charge a fee. Something newer, lets say the Inibuilds A300 or the Toliss A340 are so recent (XP12 was already on the horizon) then them charging would be less justifiable. If developers do charge a fee then they will also have to make some development choices. Going forward only the XP12 versions will get updates and bug fixes? Will they need to maintain two code sources for the Org store, the XP11 only version and the XP12 version for new customers and those who have paid for the upgrade? Messy. And then there’s the whole issue of protecting their product. Product key verification becomes more complex when there is the key for the original purchase and presumably a key for the upgrade (or some other sort of workaround).