I am looking for a term or principle that describes software or a website that has many:
"Features" that are not really features that no end users want or will ever use.
"Features" that are so poorly implemented that no end users are able to use.
"Features" that have never been successfully implemented before elsewhere.
All of the "features" create a lot of unnecessary testing and bugs with no reward.
Research: I have read through other sites and on Wikipedia: Feature Creep , Software Bloat and Code Bloat. They are not quite right in that some or a few users are actually happy that the features are present. They might cost a lot of coding time, have a performance cost for the other 99% of users and clutter the UI but some users do want the features.
Use Case: "The new website is full of Non-Features," or "the App suffers from Principle XYZ."