> It's really hard to do frozen updates. The free edition is always kept up-to-date, as it's really part of our marketing and we want to make sure there's the latest and greatest version for people to use. So this approach means for some users, you sign in and then it has to downgrade you to an older version than you're already running. If that downgrade doesn't work or is blocked, you get the latest update anyway. Plus I think on the off-chance there's a Chrome bug that breaks even just very old versions, currently that doesn't matter, but with frozen updates it will cut some people off. I think that would work out very badly: either we have to effectively fork our support and maintain multiple different versions of the codebase for essential fixes, which is a big drag on development, or we just tell users sorry, we're not patching it, and then I'm sure they'll get upset anyway because something they once paid for no longer works.
> It's a great deal easier and simpler just to keep everyone up-to-date.
In my eyes this problem is simple to solve:
- Just provide a frozen version for the offline edition only.
- Keep only the newest versions supported. Warn the users that if they are going to use the frozen version, they won't receive support till they re-subscribe and update again.
This way you would solve the problems you mentioned in your post and also ease the souls of those who fear the lockout (myself included).
Customers would expect bug fixes, and retro fixes for breaking changes. This would be a headache to maintain. Secondly, support would become mired in difficulties with everyone running different versions.