Well yes, that depends on the project goal.
And of course no obligation from developers.
As a developer myself (time ago from that) implementing the solution that i could use was the âeasyâ part. When it reaches a broader audience is where things get difficult.
You know what you are doing and the limitations, other people are more in the dark side and would use the interface in other ways, sometimes unexpected ones.
So I fully understand what aureliene is talking about, and understand what he says.
But if you want to widen the audience, just expecting people reads the manual and understand it is not realistic.
Concepts exposed in the manual are quite technical and nobody without a good mathematic and color science formation is going to understand them in depth.
Making it more easy and understandable for common photographers is not easy.
Nakibg then easy and versatile enough to be used for the moee advanced users with good understanding of color science is even harder.
I am aware of the efforts of aureliene to explain the use of the modules and color concepts to us.
In my case with mixed results: it improvex my knowledge but not enough to u derstand what i am doibg with the modules, due to my limitations in color science.
May be time given other people with better knowledge in color science finds ways to make the concepts more understandable.