Published version update in app stores

@RyanL The point of my previous question was that there will also be features that are Premium-exclusive, but not Commercial-license exclusive, and vice versa — so it is necessary to split the table out by plan. For example, file attachments are only available to Premium subscribers; you made the commitment that “all current features are available in both versions”, so presumably, the file attachment feature will continue to be available in the GPLv3-licensed clients for Premium subscribers. Now suppose Bitwarden at some point implements an in-app file viewer for attachments, and decides to make that new feature exclusive to the Commercial license. In this scenario, you will have three tiers of functionality:

  1. Free subscribers can use neither file attachments, nor the file viewer, no matter what license model they choose.
  2. Premium subscribers using GPLv3-licensed clients can use file attachments, but cannot use the in-app file viewer.
  3. Premium subscribers using commercially-licensed clients can use file attachments, and can also use the in-app file viewer.

So the table I posted above must have at least 3 rows. It will need all four rows if Bitwarden ever releases a commercial-license exclusive feature that is made available to free plans (or should this possibility be ruled out categorically?).

1 Like