Before Submitting Your Power-Up to be included in the Power-Up directory, review these guidelines to ensure that your Power-Up is as awesome as Trello's users expect it to be!
We hold all Power-Ups to the same standards that we use internally when adding new features to Trello. Your Power-Up should work well, be easy to use, and provide delight to all users–just like Trello!
Below is the general list of things we'll go through when reviewing your Power-Up. Every Power-Up is different, so not all of these may apply and there may be other things we look at.
Guidelines
Do what it says on the tin: Your Power-Up should do what it says it does! It shouldn't do anything unexpected or undocumented.
Be Speedy: Your Power-Up should respond to requests as quickly as possible. Power-Ups that timeout on requests will be rejected. Make use of asynchronous requests, if possible, when you need to get data from non-Trello services.
Meet User Expectations: Your Power-Up should take actions only when a user expects them to–no surprises! For instance, opening a board bar or modal should only occur if a user has clicked on something to which the Power-Up is responding.
Documentation: Be sure to fill out the Overview and Description fields in the Power-Up admin portal–they're used to populate the Power-Ups directory's listings. The Description should make it clear what the Power-Up does and why a user should enable it. Great Power-Ups include gifs of the Power-Up in action!
User on-boarding: Make it clear and easy for a user to get started with your Power-Up. If your Power-Up needs setup or requires an explanation of how to use it once its enabled, we recommend using the on-enable capability to open a modal (using t.modal()) to walk a user through getting started.
Doesn’t infringe Trello trademarks: Trademark infringement is an automatic rejection, so be sure to read Trello and Atlassian's brand guidelines before submitting your Power-Up. This includes visual assets as well as naming conventions. For example, Trello Power-Up X would be rejected.
No pop-in chats or ads: Your Power-Up should be free of ads, pop-ups, and pop-in chats and notifications. Documentation on getting started and support information, should be included in the on-boarding experience of the Power-Up.
Clear Paid/Service Requirements: If your Power-Up requires a separate third-party account (that is a user must login to another service) this must be made obvious to the user in the description and overview of the Power-Up and during the on-boarding experience. Additionally, your Power-Up should give the user the opportunity to disassociate their third-party account via the show-settings capability. Require the user to copy and paste API keys and tokens from other services into Trello; the authorization flow should be a fluid, integrated experience for the user.
Security: Your Power-Up should act responsibly with user data, and, especially, with Trello user tokens. Any Power-Up requiring login should make use of the authorization-status and show-authorization capabilities and must provide a way to disassociate the user account via the show-settings capability.
Communication: Your Power-Up should not contain typos nor grammatical errors.
Provides Shared Perspective: Trello is all about providing a shared perspective on anything. Every person who can see the board sees essentially the same thing. Make sure to follow this principle wherever possible. Consider what will happen when your Power-Up is viewed on a public board, or on a board to which the user is not a member. It's okay to restrict functionality to certain groups of users if you have complex permissions or licensing. As a general rule, your Power-Up should not show different views to different users without a good reason.
Extend Trello: The best Power-Ups make Trello able to do something that it was not able to do before; they are simple but powerful. They fit in naturally and complement Trello in delightful new ways. Your Power-Up should provide complementary and useful functionality to Trello, look and feel like Trello (using the provided Trello styles wherever possible), and not simply embed an existing web app. Nor should your Power-Up rely on a browser extension for functionality.
Styling: Your Power-Up should include relevant, appropriately colored and styled icons. Power-Ups should respect Trello and Atlassian design guidelines and not make use of Trello assets except for the Trello logo and colors when appropriate.
No Bugs or Visual Spam: Your Power-Up should not have Javascript errors in the console or any other bugs. Elements in the Power-Up should be sized correctly and have a design that is intuitive. Too many badges, buttons, large attachment sections are a bad thing. Your Power-Up should not store data in other Trello fields like card descriptions or comments.
Granular Consent: Your Power-Up should not automatically bulk add itself or other Power-Ups on the user’s boards and workspaces. Power-Ups must be enabled on boards individually by a user.
Reasonable pricing: If your Power-Up is paid, it should be reasonably and competitively priced.
Sustainable Hosting: Your Power-Up should be ready to support a large number of users after it is listed in the Power-Up directory.