The problem is that each additional features imposes costs on those users who don't need it. An example would be JIRA. JIRA is designed to have every feature possible. But as a cost it is hellishly slow and is hard to find anything in.
Each additional 20% of the features you support cuts the UI and technical effort that can be put into the other 20%s of features.
The end result is the standard big corporate apps that feel heavy weight despite doing what feels like a pretty simple thing.
It makes sense for companies to do it. Because the cost is born by the consumers.
>"But as a cost it is hellishly slow and is hard to find anything in"
There are examples to the contrary. CAD products I think are way more complex than this JIRA abomination but are not slow at all. And for what it worth I went from knowing nothing to producing complete design of a relatively complex piece of equipment (main assembly, all individual parts etc in a form accepted by factory) in less than a month using Solidworks. This says something about quality of this piece of software. Out of fun when I had nothing to do I tried to repeat the design in FreeCAD - never fucking again.
So I think the problem is not the amount of features (the more the better). It is just very hard to design proper ergonomic GUI and workflow.
> JIRA is designed to have every feature possible.
If only that were true. There are several long-requested features that they refuse to implement on "agile purity" grounds (such as the ability to split a story while also distributing points, so you can mark it as partially complete in a sprint, or at least leave behind completed subtasks in the old sprint).
Each additional 20% of the features you support cuts the UI and technical effort that can be put into the other 20%s of features.
The end result is the standard big corporate apps that feel heavy weight despite doing what feels like a pretty simple thing.
It makes sense for companies to do it. Because the cost is born by the consumers.