First of all, I would like to commend the Trello team for the superlative work done in developing this application. From concept to implementation, you guys have demonstrated what it takes to produce a comprehensively and flexibly functional app without sacrificing usability and learnability. It is as if you analyzed what cognate applications were doing wrong and ensured you did the opposite. My sincerest adulation to you guys.
That said, there are a few things (lacking features) I found limiting with the app, which are expounded on below in order of importance:-
Feature 1 - Custom ordering of control artifacts/widgets
Labels are one of the most useful widgets in Trello. Due to their ease of use and the fact that they quickly add organization and presentation to cards, they are potentially the most commonly used items in the application. It has been discovered that the label colors, although originally designed with predefined meaning in mind, can be repurposed to suite a target domain semantic with the aid of custom label names.
The limitation arises in a situation where labels are classed into enumeration groups (such as Card Type or Card Status), and are expected to be displayed in a fixed card label position according to the designated class. Due to the rigid alphabetical ordering enforced by the Labels menu, which governs the ordered placement of labels on a card, labels are rendered impervious to any such fine organizational control.
The same can be said for Card Buttons, which are very cool action widgets, if I might add; however, they suffer from lacking the convenience of being ordered in a user-defined manner (e.g. by similar functionality), instead of just alphabetically.
Automation Rules could also provide benefit to the user in this way. Naturally application performance will be impacted as the rules catalogue becomes larger, manifested by delayed background action executions. By enabling rule trigger executions to be prioritized by the author could help alleviate lags for critically acclaimed rules.
Feature 2 - Auto-populate current Tigger/Action settings on edit
Typically, when editing an item or model possessing a particular configuration in a UI , it is usually expected that its particular settings would be auto-populated into the UI configuration console for modification/tweaking. However, the editing mechanism provided by Trello works in such a way that the UI only remembers the last saved configuration, regardless of the rule being edited. This makes making small adjustments the already created rules unnecessarily difficult and prone to user error.
Feature 3 - Multiple triggers per rule
Just as a single rule may have multiple actions, a rule should also be able to have multiple triggers. Each trigger would be ORed together to form the ultimate predicate. This would alleviate the redundancy in creating multiple rules with the same action(s).
Feature 4 - Do more with Board Buttons
Board Buttons are a good idea! Surpassing Card Buttons as a more panoramically scoped set of action widgets, these control artifacts have the potential to do more.
Suggestion
Enable board buttons to enable and disable command libraries, providing even more dynamic automation to the board. This, and other board exclusive actions can be categorized under a "Board" (or something similar) action tab.
Well, that's my 2 cents guys. There are more I could have mentioned but I suspect you guys have a lot on your plate so I only wanted to present short-listed items.
Again, great job on the Trello app, I hope you keep the same spirit going as what got you this far, and I hope this post adds a fair contribution towards its improvement.
Best Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.