RFCs are a way for Atlassian to share what we’re working on with our valued developer community.
It’s a document for building shared understanding of a topic. It expresses a technical solution, but can also communicate how it should be built or even document standards. The most important aspect of an RFC is that a written specification facilitates feedback and drives consensus. It is not a tool for approving or committing to ideas , but more so a collaborative practice to shape an idea and to find serious flaws early.
Please respect our community guidelines: keep it welcoming and safe by commenting on the idea not the people (especially the author); keep it tidy by keeping on topic; empower the community by keeping comments constructive. Thanks!
We are making changes to the category taxonomy and introducing the concept of keyword tags to improve the discoverability of apps in Marketplace.
- Publish: Oct 20, 2023
- Discuss: Nov 3, 2023
- Resolve: Nov 10, 2023
We understand that the current categorization system in the Atlassian Marketplace is complex and disoriented with 37 categories. This offers a disjointed experience for customers who are trying to discover apps that align with their needs.
The existing categories are inconsistent with some being too broad and some being too specific based on use cases, functions, and/or features. The current system also lacks clear guidance for Marketplace partners on how to categorize their apps, leading to potential misalignment and confusion. Below are the issues that have been identified due to this complexity:
- Only a small percentage of customers use categories as they do not find value in them
- The same apps are found in multiple categories, thus impacting app discoverability
- Apps are shown in categories which they don’t fully align with
- The number of use case-based categories is limited, and as a result, customers cannot refine their search based on the use cases they are looking for
- Current categorization is broken and hampers proper segmentation of apps. This is a blocker for proposing recommendations like ‘similar apps’ to customers
Categories and Keywords
The Atlassian Marketplace will feature industry standard categories and use-case-based keywords. We will reduce the number of categories to 10, which will be exhaustive enough to cover all existing categories while being inclusive at the same time. Along with categories, we will also provide 60+ keywords that can be used to showcase use cases supported by an app. In the newly proposed taxonomy, partners will be able to tag their app to 1 Category and 3 keywords. The limited number of categories will make it easier for customers to navigate, while the higher number of keywords will provide flexibility in refining their selection based on their needs and requirements. For example, an app can be categorized as Project Management and have additional keywords such as Issue Tracking, Dashboard Gadgets, and Data Visualization.
New taxonomy for categories
Currently, when people click on a category (for example, time tracking) they are taken to a filtered page of search results for that category. We will instead create pages that provide context and showcase content about the specific category. Thus, each category will have a dedicated page in the navigation. Partners can map their apps to one category and detailed documentation on how to categorize will be provided to support the partners in this process (tentatively by Dec 1, 2023). The app would be discoverable on other surfaces based on the keywords provided by Marketplace partners which will be searchable.
Here is the list of categories along with a brief description of each of them:
Keywords are a new concept that we are introducing in the Marketplace. Partners will have the opportunity to choose up to three keywords for their apps. A comprehensive list of keywords will be provided for easy navigation for the partners. The pre-defined list is curated to ensure clarity and consistency without any duplication.
We understand that we might not be able to cover every possible use case that aligns with app offerings on the Marketplace. For this, we will be sharing a detailed process for Marketplace partners to get new keywords added in case use-cases supported by their apps are not provided in the list of keywords.
Here is the list of pre-defined keywords:
Customers will derive value from the quick and efficient discoverability of the apps. Previously, customers used to see the same set of apps in multiple categories and they didn’t have a way to filter the results based on different use cases. The new experience will encourage intent-based discoverability and customers will be able to find the right apps that suit their needs and requirements. The new taxonomy and keyword strategy will support effective search and filtering experiences for customers.
Partners will be able to reach their target customers by accurately defining keywords for their apps. The new system offers a wider range of use cases that precisely represent the customers’ needs. For instance, an app that supports notifications for JSM can be easily discovered by users if it is categorized under ‘IT support and service’ and has a keyword called ‘Notifications’. The new experience will help partners connect their apps to the right audience and the apps will be aptly discoverable under the selected category.
For smooth transition of all apps from the old system to the new category taxonomy, we will have a change management period of 3 months (tentatively December - March). Throughout this period, we will offer support for the old categories and ensure that there is no disruption to the customer experience. Customers will still be able to navigate the Marketplace using the old categories.
For existing apps, partners can go to the app details page and edit the information by choosing the new category and three keywords. Apps that are not categorized will not be displayed on the new category pages that will be created as part of customer-facing launch, which is scheduled post the change management period in March 2024 (tentatively).
New categorization on App Details UI
Once the change management period concludes, we will start transitioning to the new category taxonomy on the customer side. The customer experience will take the users to dedicated category pages with keyword filters so that they can find the app they need.
While we would appreciate any reactions you have to this RFC (comments, questions, or concerns about the proposed changes), we’re especially interested in learning more about:
- Are there any concerns with the proposed taxonomy? Do you foresee any edge case scenarios that we have missed, which have the scope to be a separate category?
- Are there any concerns with the keywords shown in the RFC? Are we missing any keywords that don’t overlap with those listed above?
- Any feedback regarding change management?
We appreciate your time and any feedback you could provide, whether it be on the specific points highlighted above or anything else outlined in the RFC. Your valuable insights will play a significant role in shaping better app discoverability on the Marketplace.