Last updated May 16, 2025

Overview

You can develop, test, and launch Standard and Advanced editions for your cloud apps, offering differentiated features and pricing to meet diverse customer needs. This page provides a comprehensive guide to your journey.

The journey is structured into three key phases: planning, building, and publishing. Below is a detailed breakdown of each phase to help you navigate the process.

App editions journey

Planning phase

In this phase, you'll lay the groundwork for your app editions by defining your strategy, understanding customer needs, and planning your approach to packaging and pricing. Use the following resources to guide your planning:

  • Planning guide: Step-by-step guidance on defining your editions, identifying target customer segments, and aligning your product roadmap with your app editions strategy.
  • Pricing and packaging guide: Detailed insights into setting prices that reflect the value of your Advanced features, aligning your strategy with market expectations, and leveraging Atlassian’s pricing philosophy to your advantage.

Building phase

During the building phase, you will implement the technical aspects of differentiating between Standard and Advanced editions. This includes adding conditional logic in your code and ensuring that features are appropriately gated by the edition.

  • Build editions for Forge apps: Instructions on implementing app editions in Forge apps, including how to use Forge-specific APIs and features to manage edition differentiation.
  • Build editions for Connect apps: Guidance on adapting Connect apps for app editions, utilizing the Connect License API, Connect conditions, and other relevant tools.

Learn how to introduce and test conditional logic that differentiates features based on the edition a customer is subscribed to. Key considerations include:

  • Incorporating edition-specific logic using capabilities, like installation lifecycle events and license APIs.
  • Managing backend functions and ensuring that edition data flows correctly through your app’s architecture.
  • Testing your configurations across development, staging, and production environments to validate functionality and user experience.

Publishing phase

In the publishing phase, you'll finalize your app editions, submit them for review, and make them available to selected customers. This stage focuses on the steps required to bring your editions to market.

  • Publishing editions: Step-by-step instructions for adding and mapping features to the appropriate editions, setting pricing, and submitting your app for review.
  • Modifying editions: Guidance on updating features and pricing after your initial submission, allowing you to refine your offerings based on feedback and performance.

Once submitted, your editions will undergo a review by the Marketplace support team to ensure compliance with Atlassian’s guidelines and validation of edition-specific functionality. Once approved, editions will appear on your Marketplace app listing.

Customer upgrades/downgrades

Customers will be able to upgrade and downgrade their editions through Marketplace, in-product Marketplace, Admin Hub and Billing console. To learn how customers do this, see Install and manage app access.

Rate this page: