Various thoughts on a desktop environment concept.
Because the interface itself is so customizable, development can start out with many less features in order to reach version 1.0.
The design of the interface allows for continuous expansion of features along with a continuous development pace.
The profile sharing and customization allow for a gradual and less centralized selection process to take place instead of a necessity for a bottle-necked and compressed design process.
A looser restriction around design limitations allow for features to rise in importance on their own merits, such as integration with a particular workflow, or increase in efficiency over another similar tool.
These capabilities require an initial investment of time in order to develop the GUI framework itself, and connect it to a sharing platform. However, the framework produces an environment that ends up being more conducive to the real life contributions of disparate development resources.
The design of a user-customizable interface and shareable profiles means that the maximum amount of control is also given to users who have no idea how to edit json/xml configuration files, let alone how to program a plugin or extension.
Yet, those who can edit json/xml configuration files and creation plugins still have added value to their individual contributions, because they can also distribute toolbars and gui profiles along with their tools, to show how they can be integrated into the main application gui.
What this means is that what otherwise had to go through a centralized process of decision making and several layers of acceptance by people up a chain, now only has essentially one layer of acceptance to get into the lowest tier of the tool bank.
This possibility of smaller portions gaining mainline acceptance makes development and contribution to one single larger project more enticing and more feasible by a larger number of developers simultaneously, thus consolidating valuable contributions of developers.
This approach also inspires less redundancy to program for instance, five separate audio applications, because one set of developers merely prefers a different kind of featureset on the primary gui. Such decisions inspire developers to have to re-program an entire set of features over and over again.
