As part of an early access program (EAP), you can now build standard and advanced editions
of Marketplace apps in the cloud that are Paid via Atlassian. During this stage of the EAP,
participants can build and test editions of non-production apps in development, staging,
and production environments.
EAP features are available to select users for demand, viability, and suitability testing.
Releasing a feature as an EAP helps us gather insights that inform future development decisions.
Overview
Welcome to the early access program (EAP) for app editions on the Atlassian Marketplace!
This program allows selected Marketplace partners to develop, test, and launch standard and advanced
editions for their cloud apps, offering differentiated features and pricing to meet diverse customer needs.
This page provides a comprehensive guide to your journey in the EAP.
Key points for the EAP:
Program duration: The early access program for app editions will be active from DDMMYY to DDMMYY.
During this time, you'll collaborate closely with the Marketplace product and engineering teams
to set up your app editions and offer them to a targeted group of customers selected for this initiative.
Hands-on support: Throughout the EAP, you'll receive high-touch support, including regular check-in
meetings with the Marketplace team to provide guidance, resolve any issues, and gather feedback
on your progress. Our goal is to ensure a smooth and successful transition from development to launch.
Building advanced features: You have the opportunity to create advanced features for your apps.
Current features will be classified under the "standard" edition, while additional features or services
should be categorized as "advanced." The advanced edition is designed to meet the needs of
customers seeking enhanced functionality and support, offering an upsell opportunity from the
standard edition.
Pricing strategy: Your existing pricing will be applied to the standard edition, and you can
further refine pricing for advanced editions based on the additional value provided. Pricing adjustments
for the standard edition can be made independently of the app editions initiative, allowing you
to maintain flexibility in your monetization strategy.
Customer transition: Existing customers will automatically remain on the standard edition,
maintaining the same features and pricing they had before the introduction of app editions.
These customers can be invited to trial the advanced edition and upgrade if they find the
additional features beneficial. Upgrades during the EAP will be managed through Advocate Central,
where Atlassian advocates will guide customers through the upgrade process.
The journey through the early access phase is structured into three key phases: planning,
building, and publishing. Below is a detailed breakdown of each phase to help you navigate
the process.
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:
App editions resource hub:
Centralized access to all resources related to app editions, including strategic guides, documentation,
and updates.
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. Approved editions can then
be shared with customers via a direct link during the EAP.
Customer upgrade path
During the EAP, upgrades will be facilitated by Atlassian Advocates. Customers will explore
the advanced edition’s features through dedicated communication channels, including email outreach
and custom URLs that detail features, pricing, and the benefits of upgrading.