I like the main idea here, but the points listed are a bit extreme. Specifically this one: > should never update a user interface without allowing the previous one to be used as the default Are you ready to pay for the ongoing support of all legacy interfaces, including the ones you're not using and which are possibly not used by anyone in the world (no telemetry)? Are you ready for all the bugs and security issues t…
If the UI is changed:
* for no reason (other than justify the salary of the designers team)
* just for the sake of "give the impression of evolution", but really it's just hiding or moving buttons and menus and changing font sizes, colors, layouts...
* or to intrusively insert new and unrelated products, in the middle of the original workflow
* or to remove (or change) basic and intrinsic product functionality
* or to prevent to continue the (intended) workflows acquired with previous usage
then I'm not so fine...
anyway, what is mentioned is just that automated updates (and this does not apply to web applications I think), shouldn't do that change, without an "option to stick to the previous" UI. At least in minor version updates, I totally agree.
Edit: format and verb tenses