I'm a single shareware developer and many times i make the mistake of adding too many features into my application. For example different ways to filter and display informations.
One of the reasons is that during programming i often see some ways that might be easy to implement and may give some benefit for the user. But often they turn out to be extreme unlikely to be used at all and more confusing then helping.
Do you have any strategie for this user interface design?
Let someone (or, preferably, several other people) other than you use the program before you release it, as a very informal user test. If they show a hint of being confused (or if they don't touch the features in question at all) you should reconsider if you need those features.
When in doubt, YAGNI.
I think the answer is pretty simple: unless the requirements dictate that a feature exist, don't add it.
Frankly it seems a bit odd that you're adding features that don't really make sense. Talk to your users and actually spend some time using it and you'll pretty quickly realize what they need from your product. Adding in extra features may feel like you're adding value but it's far more likely you're just wasting your time and possibly introducing new bugs.
Okay i found this advice elsewhere and it seems to be pretty good:
"Write the user manual first when you try to explain why a feature exists and how you use it in plain english text you often find that it is too complex or not relevant for the user"