If your implicit attitude is It’s my way or the highway, then I’ll be on my way.
it’s not something I would consider doing for every feature.
I am neither rebuking you, nor being pedantic, yet, if you choose to communicate with me in the future, I would appreciate it if you would keep an open mind. Absolute assertions, such as the one I quoted immediately above, make my blood run cold.
If you choose to communicate with me in the future, I hope you will assert things like , “it’s probably not something I would consider doing for every feature.” The word “probably” might seem like, “no big deal” to you; but it’s a big deal to me.
The overwhelming majority of FOSS engineers with whom I worked, have been arrogant and angry men who craved being a Benevolent dictator for life (BDFL). If you are one of them, then it’s unlikely I will be willing to work with you to improve Vikunja.
Please understand, in such a case I wouldn’t be upset. After all, you didn’t ask for my help. Nonetheless, I don’t intend to squander my time proffering suggestions to you, if indicate you dislike them, yet fail to properly refute their value.
If it had a vastly improved UI/UX, then Vikunja would likely become a much more popular application. Currently the UI/UX Vikunja is too clunky and difficult. It also lacks many features. The UI/UX you have designed for Vikunja thus far is not terrible, but it’s not good. The problem isn’t merely that you haven’t had time; no, the problem is that like most engineers, you are bad at designing UI/UX.
If you were to properly argue against my UI/UX suggestions, and, gasp… actually occasionally defer to my expertise in UI/UX, I could help you to vastly improve the UI/UX of Vikunja.
My argument for “more knobs”
I essentially reiterate Mark Suster’s point: give novices very few knobs; give experts many knobs. That is good advice, which you have essentially ignored in the design of Vikunja and which you have failed to explicitly acknowledge.
Essentially I am talking about feature flags. For a novice, most features would be hidden behind a feature flag; for experts all features would be exposed (no features would be hidden behind a feature flag).
Imagine a user was assigned a scale of expertise for each feature. Imagine the scale began at 1 (novice level) and ended at 10 (expert).
Let’s imagine User 1 has an Expertise of 3 for Feature 6. Tersely we could express that as U1E3F6. In that case, User 1 would see the Level 3 knobs for Feature 6.
Then U2E7F1 would describe User 2 who has an Expertise of 7 for Feature 6; U3E9F5 would describe User 3 who has an Expertise of 9 for Feature 5.
Therefore, U83391E4F9629, would describe User 83391 who has an Expertise of 4 for Feature 9629. In such a case, User 83391 would see the Level 4 knobs for Feature 9629.
Who decides the level of expertises for a particular user, for a particular feature? To make it easier for you, I suppose initially the application would allow the user to manually choose his own level of sophistication for a particular feature.
At some point something like ChatGPT could be used to help automatically determine the levels. Nonetheless, the user should probably always have an option to manually choose his level of expertise for a particular feature.