Avoid to the extent posible changing existing ui when you add new features.
As a developer we tend to want to put new features in the most prominent place often at the cost of hiding existing features. In most cases the new feature were more important than an existing feature it would already have been done and not be a new feature.
Therefore when adding a new feature an effort should be made to consider where it should go in the UI that it does not interfere with existing UI. This is especially true of reskining... reskinning often appeals to marketeers and novice users but alienates existing users.
anon
shared this idea
We generally agree and put a lot of effort and care into preserving experience for existing users. We don’t reject changes per se, but make sure that the changes allow smooth transition.
However the provided statement is not actionable.
If you can tell specific recent examples of where you think the changes broke your experience – we can review them more carefully.
Without examples we will have to close the request.
UPD: We have to close the request as no details were provided.