There is such a thing as too much of a good thing.

Sometimes a simple product is loved because it does something simple quickly and efficiently.  Very few features, not a lot of variations, and basic tools that are wrapped around one or a few simple use cases.

As a developer, it's hard to not say "but it could also..." and start building more onto it, and more functions, and a prettier interface, and so on.  The problem is that more features means more complex.  More complex means more load times and more options, and more options means more clicks and menus just to get back to what I used to do fine before.

Evernote is a perfect example of this.  I used to just take notes in text documents and save them to my desktop.  This worked fine for a while but before long I had way too many notes and most of them were called "note" or something useless because I was in a rush while saving.

Evernote was a simple program to take notes, organize them, put them in folders, and open/edit/save as quick if not quicker than my usual text editor.  Well Evernote went through an overhaul and now takes 30+ seconds to load.  When I'm just jotting down a phone number, I don't want to wait 40 seconds to type for 5, so now I'm looking for another software package that does what I want without the extra features.

The point I'm making is that you should consider what the primary use of your software is, and keep that in the forefront of your development efforts.  If you want lightweight, then stop adding features, for one.

I'm not saying Evernote is a bad software now, but it's not what it was, and that means it's no longer for me.