Advanced app editions are now generally available
Disclaimer: This announcement is intended for developer who are interested in building editions for their Marketplace cloud apps. For more resources, please visit the App Editions Resource Hub.
If you’re a customer, note that advanced editions are now GA and you can view whether or not any of your current apps or potential new apps have advanced editions by checking the overview or pricing tab on the app listing to see if both standard and advanced options are available.
App editions offer developers the ability to build one app product and tailor it to various market segments. Editions provides developers with a more unique way to price and package their apps, enabling them to create both standard and advanced versions of their app(s).
In fact, Appfire, one of the Marketplace partners who participated in our early access program stated that, “App Editions will drive revenue growth by both upselling existing customers with premium offerings and developing new product editions that address untapped market segments.”
With general availability (GA) now here, developers can designate an existing app to standard and build an advanced version. However, we’re working to enable developers to designate their existing app as either a standard or an advanced edition and create free editions sometime in the second half of calendar year 2025.
In this blog, we will walk developers and Marketplace partners through:
- How to build editions on both Connect and Forge
- How to publish your edition
- How customers can discover editions
Related content: Curious to learn more about App Editions and how you can plan for it? Check out Partner Preview: App editions are coming to Marketplace – Work Life by Atlassian
How to build edition(s) on Connect or Forge
Developers will need to revise their code to incorporate conditional logic tailored to each edition’s specific features to effectively utilize both Connect and Forge, as follows:
Forge
- Context object will start containing a new field
capabilitySetwhich will have value standard or advanced based on subscription - Both Custom UI and UI Kit will now have
capabilitySetas an additional property or constant to the license information in theLicenseDetailsobject. - Forge native
node.jsruntime that provides appContext will now have thelicenseproperty within that context for Forge functions, which will evaluate the license state andcapabilitySetdefined for each edition. - Requests to your remote backend will include a Forge Invocation Token (FIT) as a bearer token in the authorization header. The FIT includes important information about the invocation context, which will now include the
licenseproperty. Thislicenseproperty will evaluate the license state andcapabilitySetdefined for each edition.
More information: Editions for Forge apps
Connect
- To introduce conditional logic for relevant requests in your app, you need to add the new parameter
capabilitySetand set the value to eithercapabilityStandardorcapabilityAdvancedaccordingly.
http://....?lic=active&capSet=capabilityAdvanced- Lifecycle callbacks contain a JSON data payload with important tenant information that you will need to store in your app in order to sign and verify future requests. For editions, we’re adding the
capabilitySetproperty, which you can then set to eithercapabilityStandardorcapabilityAdvancedto introduce conditional logic in your app.
More information on capabilitySet
capabilitySet: 'capabilityStandard' | 'capabilityAdvanced' | null;- Context is a JavaScript module that provides functions for the current product context. Depending on how your app is using Context methods, you will be able to read the new property
capabilitySetunder thelicenseobject - Atlassian Connect provides a set of REST APIs specifically designed for use by cloud apps. Requests to these resources are made against the Jira or Confluence Cloud instance, not the Marketplace API. You will be able to read new property
capabilitySetunder thelicenseobject with a value of eithercapabilityStandardorcapabilityAdvancedaccordingly
More information: Editions for Connect apps
How to publish your edition(s)
We will be using a particular key:value paid in-app versions to determine the support of editions for an app. Developers have to set a field editionsEnabled: true in their descriptor for Connect apps and manifest for Forge apps, which will enable the publish experience flow of editions in the Marketplace experience. Developers will then be able to publish editions for this app, and any version going forward will have to support editions, and this flag cannot be reverted. This will create a micro version for Connect and a minor version for Forge.
Features can be included for each edition, accompanied by concise descriptions. These details will be presented to customers during the evaluation phase, particularly for comparison purposes.
During the creation of an edition, the price can be updated for both the standard and advanced editions. The checks for advanced pricing are consistent with those for standard pricing, with the key difference being that the prices for advanced tiers are higher than or equal to those of their corresponding standard tiers.
Post-creation, developers are required to submit their editions, which will undergo approval by the Marketplace operations team before editions go live.
The approval flow is as follows:
- With the addition of
editionsEnabled:truein the descriptor/manifest, the version approval flow will be triggered with the creation of a new ECO-HELP ticket directed to the marketplace operations team. - This ticket will be accessible to developers via the versions and editions tab.
- Upon approval, the status will be communicated via the editions listing tab, with the advanced edition subsequently made publicly available.
How can customers discover app editions
Customers will be able to discover all the editions of an app on various Atlassian surfaces. These surfaces will enable customers to understand the features that are available in an edition and the cost for each edition. Customers will be able to discover editions via MARKETPLACE PORTAL as well as IN PRODUDCT MARKETPLACE.
On the MARKETPLACE PORTAL:
- Customers will have the chance to effortlessly navigate through all the features available in the application via the overview tab. Additionally, they will be able to identify which features correspond to each edition. This distinction will encompass the feature list supplied by developers during the development of the editions.
- The pricing tab on the Marketplace will enable customers to distinguish between different editions by presenting features in a clear tabular format, as illustrated below.
- Since the level of support can serve as a differentiating feature for various editions, the support tab will showcase a banner to highlight this potential distinction.
In product Marketplace
When it comes to the in-product Marketplace:
- The updated overview tab will look the same as the Marketplace Portal
Get started building app editions now
With 25 advanced editions successfully built by developers and a lot of great feedback from those who participated in our Early Access Program (EAP), there’s no better time than now to get started.
According to Amoeboids, a Marketplace partner who participated in the EAP, “The implementation was straightforward, requiring just an additional license flag, and Atlassian’s documentation made the process seamless.”
If you’re interested in developing an edition for your app, get started now. To ensure that new editions go live as swiftly as possible, we will prioritize the approval of apps submitted by the end of June.
If you’d like to learn more about app editions, please visit the App Editions Resource Hub in the Developer Community.