@scottohara i think the same is true for background scripts in Jira.
1 Like
Just need to clarify a few things:
-
There has been some references in the description to the Standard app and Advanced app as though they are seperate, but the developer experience section refers to the distinction being based on some additional information, seamingly taking a feature-flag approach (the example being a new field called âcapabilitySetâ). Just want to confirm that the intention is the latter feature-flag based approach and there is no need for app developers to package different editions of their apps.
-
The Publish experience mentions a new tabbed section âEditionsâ, containing details and feature breakdown of the available editions. If an app only has the Standard edition, does this new âEditionsâ section appear in the Marketplace?
@SeanBourke can comment on Part 1 of the question.
Coming to the Part 2 - The tabbed section âEditionsâ will be visible for all paid cloud apps in the partner app publish screens. However, unless both a Standard and Advanced version of an edition is configured, it does not allow those details to go live. At this point, we are not building a mechanism in the descriptor/manifest or elsewhere to declare if an app has editions for us to power the visibility of this tab based on such a declaration.
2 Likes
How will this present in the Marketplace license report? And what is the maximum delay in the reports? If we were to have some external provisioning system based on automation received on the marketplace api - what should we be expecting?
3 Likes
Hello @SarahAllen, @PremankuChakraborty, @SeanBourke, and thank you for a thorough RFC plus quick turnaround to questions from the Marketplace Partners!
I appreciate weâre all going on a journey here, exploring this space and learning together. With that in mind here are a few of the questions and thoughts that Easy Agile are reflecting on at present:
- Should our DC subscriptions contain all of the features of the Advanced edition? How would we communicate differences in functionality between DC and the two Editions on Cloud on our website, Marketplace, etc?
- How does a DC customer migrate to Cloud? Presumably they need to migrate to an Advanced Edition based on the above. For example, we would likely accept the data from DC via JCMA and it would be stored in Cloud, yet if they are on the Standard edition then they would lose access to that functionality and data.
- How do we enable end users to experience functionality of an Advanced edition when they do not have administrator permissions? Ideally we can surface additional functionality in product and enable end users to request Advanced from their administrator.
- What would the revenue implications be of an uncapped user tier for the Free edition? How would we model with the information we have today? Our preference at this stage is to continue with the Free Starter Tier to avoid changing too many things at one time, as with lots of changes at once it hinders our ability to ascertain attribution on financial metrics.
- A Free Edition adds friction to the buying process as it is different from Atlassianâs existing pricing structure. For example, Atlassian uses a Free Starter Tier for their products, so introducing something different requires someone (Atlassian? Marketplace Partners? Solution Partners?) to educate customers, and that all takes time.
- Is this a precursor to Atlassian offering an uncapped user tier Free edition for their products too?
- Will we be able to apply different promotion codes to each edition separately, so we can promote the Advanced edition without the promo code being used on Standard?
- What are the implications of app editions with respect to license decoupling?
- What does Atlassianâs GA / comms plan look like? Does this get announced at TEAM '25? How does Easy Agile tell a good news story around App Editions?
- Can we get a commitment to be notified of the GA timeframe and comms at least 2 months in advance so we can prepare our own messaging?
- Can Atlassian provide a pricing calculator tool to enable us to plan, model and then communicate pricing for each edition at each tier? This would be an exact copy of the pricing tool you will create for setting the pricing ahead of it being live in the admin portal. Without this we will not be able to accurately plan, model and communicate pricing changes and options.
- How does Easy Agile classify an Evaluator if the Free Starter Tier is phased out? Our financial and product metrics currently look at how many Evaluators become paid Customers. Basically, we need to consider the internal reporting / management accounting ramifications and change those reports to reflect the new reality. Again this is something that makes comparing present vs past periods difficult (like pre vs post Server EOS).
- How do we direct evaluators to the right Edition for them? Is an end user able to request the Advanced edition? Can we deep link to the Marketplace so an end user can start or request an evaluation of an Advanced edition?
If you have thoughts around any of these weâd love to hear them.
Thanks so much, have a great day,
Nick Muldoon
CEO, Easy Agile
3 Likes
Hi Atlassian team! Thank you for the detailed RFC on the topic. The Gliffy team is glad to see App Editions moving again!
As a few other Marketplace vendors have mentioned, we too would love to see the ability to shift our existing user base into the Advanced edition. This is the most important factor for us to be able to implement App Editions.
We would also like to echo that including editions in AP.context.getContext() would be valuable to us.
With regards to the notion of using product support as an additional differentiator between standard and advanced editions, would it be required that both Standard and Advanced meet the Cloud Fortified 24/5 requirement? Or, could we offer a local business hours term to Standard and maintain 24/5 (or 24/7) for Advanced and still be in compliance?
Thank you, team!!
2 Likes
HI @PremankuChakraborty is there any update on expected timelines for Milestone 1 and Milestone 2?
2 Likes
Hi All - apologies for the delay in responding to the comments from last week. I will get back on the responses by Monday. Thank you!
We are happy about this RFC and canât wait to explore the concept of App Editions further!
At Seibert Media, we would prefer the flexibility to shift customers to different App Editions based on the maturity of each app. For instance, for apps with enterprise-level features on the roadmap, transitioning customers to the standard plan would be suitable. But for more mature apps, shifting customers to the advanced plan (while also offering a new simplified version as a standard edition) would be ideal.
Looking forward to your next steps.
Cheers,
Sarah
Product Manager @ Seibert Media
3 Likes
Hello there!
Thanks a lot for this RFC, we have been waiting for App editions for a time so we are really excited for them.
In general, thanks for the current approach, it almost satisfy all our current expectations about it.
For us it will be no problem to move all our current customers to the Standard edition. For Advance edition we are evaluating / thinking on:
- Adding some extra advance features for them in the following months
- Be less restrictive with some usage limitations in some features
- Support Data Residency
- Give an extra help from our support
But we understand that maybe the better approach may be to give to every app the change to select their default edition.
Iâm curious too about the Marketplace license API changes to add the edition of customers. This is definetely something to track.
Have a nice day!
@PremankuChakraborty - great RFC. Weâre very excited that this program is coming back. This type of commercial flexibility is very welcome.
A few notes:
- We like the idea of offering Free for any size of customer. Admittedly, thatâs maybe easier for us since we donât currently participate in the Free Starter version today.
- We are planning right now to take our current customers/entitlements and grandfather them with the current functionality/price. Then weâll offer different entitlements for new Standard customers and new Advanced customers.
A few questions:
- How will discounting work? Will we be able to apply different discounts for Advanced vs Standard?
- Nice to have: Allow us to choose whether a new customer gets Advanced vs Standard.
- Will there be in-app facilities for trialing/upgrading from Standard to Advanced?
- Will there be ways for users to request an admin to upgrade from Standard to Advanced? (similar to how a user can request an app be installed)
In this license report API, we will be sharing the current Offering name against each license i.e. whether the offering is Standard or Advanced. Our recommendation is not to build a provisioning system around the reporting APIs because this will a) have the delay that the reporting APIs have today of ~3-6 hours and b) the ideal APIs to be used for provisioning are the ones mentioned in the Developer Experience section of the RFC. The license report API is recommended to be used for reporting purposes only.
1 Like
As a few other Marketplace vendors have mentioned, we too would love to see the ability to shift our existing user base into the Advanced edition. This is the most important factor for us to be able to implement App Editions.
@SamieKaufmanGliffy , @SarahSchmitt, @alvaro.aranda - This functionality is being considered but will not be available for Milestone 2. For milestone 3, i.e. when we go GA, we will have the ability to make this happen either self serve by partners or via a high touch Marketplace support/operations team assisted mechanism. Thanks for sharing your interest about this.
With regards to the notion of using product support as an additional differentiator between standard and advanced editions, would it be required that both Standard and Advanced meet the Cloud Fortified 24/5 requirement? Or, could we offer a local business hours term to Standard and maintain 24/5 (or 24/7) for Advanced and still be in compliance?
@SamieKaufmanGliffy - For Milestone 2, we are relaxing Cloud Fortified requirements. Internally we are still discussing how to plan this for General Availability. So please stay tuned on this as we get closer to Milestone 3.
HI @PremankuChakraborty is there any update on expected timelines for Milestone 1 and Milestone 2?
@awignall - Milestone 1 is a documentation only Milestone. This RFC is included as a deliverable of the Milestone and you will see documentation related to how to think about editions, etc. keep landing until September. Milestone 2 is the Early Access Milestone for select partners and apps to participate. This milestone will land in early Q4 calendar year 2024.
Iâm curious too about the Marketplace license API changes to add the edition of customers. This is definetely something to track.
@alvaro.aranda - Marketplace license API will indicate as to customer is on which edition. Exact details will come in closer to the Milestone 2 release.
- We are planning right now to take our current customers/entitlements and grandfather them with the current functionality/price. Then weâll offer different entitlements for new Standard customers and new Advanced customers.
@adam - I would like to discuss more over a meeting with you about this use case. I will try to find some time for us.
- How will discounting work? Will we be able to apply different discounts for Advanced vs Standard?
- Nice to have: Allow us to choose whether a new customer gets Advanced vs Standard.
- Will there be in-app facilities for trialing/upgrading from Standard to Advanced?
- Will there be ways for users to request an admin to upgrade from Standard to Advanced? (similar to how a user can request an app be installed)
@adam - #1 - For now, itâs a single discount at an app level irrespective of the edition. However, in our backlog we do have a requirement to get discounts to a edition level granularity but that will come in a future release as we have to assess the feasibility and the work required around that. #2 - answered above - yes, we will have this for Milestone 3, GA. #3 - If I understand your Q correctly, will we offer something within your app to upgrade, I think the answer is No. But you can build your own capability in app to nudge a customer to upgrade if they are on standard and land them to a upgrade action on Marketplace. #4 - Yes, this is being considered for Milestone 3, but we havenât still nailed down the details. But this is a really good suggestion - thank you!
Thanks a lot for your interest and support and the inputs. This definitely helps us how we shape our requirements and what we prioritise.
2 Likes
Hello @nick - thanks for your Qs - here are responses -
-
The data center can contain different features than the cloud. How you communicate that on your website will be your choice. In terms of Marketplace, we are still working through the designs for Milestone 3, when this information will be surfaced. This is something we can provide guidance on. A related question: are there cases today where DC and Cloud could have different features, and if yes, how is that represented on Marketplace?
-
The question regarding migrations is great. It is not something I have given enough thought to. I will get back to you about this and also check if we have any parallels or guidance with our Atlassian products that we can use here.
How do we enable end users to experience functionality of an Advanced edition when they do not have administrator permissions? Ideally we can surface additional functionality in product and enable end users to request Advanced from their administrator.
Yes - this can be done.
- What would the revenue implications be of an uncapped user tier for the Free edition? How would we model with the information we have today? Our preference at this stage is to continue with the Free Starter Tier to avoid changing too many things at one time, as with lots of changes at once it hinders our ability to ascertain attribution on financial metrics.
- A Free Edition adds friction to the buying process as it is different from Atlassianâs existing pricing structure. For example, Atlassian uses a Free Starter Tier for their products, so introducing something different requires someone (Atlassian? Marketplace Partners? Solution Partners?) to educate customers, and that all takes time.
We will consider this feedback and take it into account as we plan for Milestone 4. While we are not sharing a strong recommendation on this yet, the discussion in this RFC will be helpful as we begin to think about it.
- Is this a precursor to Atlassian offering an uncapped user tier Free edition for their products too?
No, please donât interpret it that way. This was solely a Marketplace consideration, as Marketplace offers free for all products, unlike Atlassian.
- Will we be able to apply different promotion codes to each edition separately, so we can promote the Advanced edition without the promo code being used on Standard?
In Milestone 2, we will not differentiate promo by edition but this is something we are thinking about offering in a future release. We still have to work through the details, feasibility etc.
- What are the implications of app editions with respect to license decoupling?
We will share more guidance around this as we get closer to thinking about license decoupling. I gather you are trying to ask if, within a site, a particular user can have an advanced version of the same app while another user has the standard version. If yes, thatâs an interesting viewpoint, but it is too soon to comment on that.
- What does Atlassianâs GA / comms plan look like? Does this get announced at TEAM '25? How does Easy Agile tell a good news story around App Editions?
- Can we get a commitment to be notified of the GA timeframe and comms at least 2 months in advance so we can prepare our own messaging?
We havenât forecasted a GA date yet. It depends on the success of Milestone 2, but we definitely anticipate it will be before Team '25. We will share more details about the date later, and yes, partners will be informed at least two months in advance, if not more.
- Can Atlassian provide a pricing calculator tool to enable us to plan, model and then communicate pricing for each edition at each tier? This would be an exact copy of the pricing tool you will create for setting the pricing ahead of it being live in the admin portal. Without this we will not be able to accurately plan, model and communicate pricing changes and options.
If you are talking about the pricing calculator we display on the pricing tab of marketplace app page, then yes, it will have a way for customers to see and calculate the pricing at an edition level. It will be available starting Milestone 3. But I think there is probably a part of this Q which I am not answering accurately. Can you share more details @nick ?
- How does Easy Agile classify an Evaluator if the Free Starter Tier is phased out? Our financial and product metrics currently look at how many Evaluators become paid Customers. Basically, we need to consider the internal reporting / management accounting ramifications and change those reports to reflect the new reality. Again this is something that makes comparing present vs past periods difficult (like pre vs post Server EOS).
As mentioned, we will rethink our strategy on Free about Milestone 4. This RFC has been a great source of feedback on free and we will think how to best bring Free editions to life.
- How do we direct evaluators to the right Edition for them? Is an end user able to request the Advanced edition? Can we deep link to the Marketplace so an end user can start or request an evaluation of an Advanced edition?
Yes - this should be possible most likely in Milestone 3.
Thank you! Please lmk if I am misinterpreting any Q and happy to provide more details.
2 Likes
Thank you @PremankuChakraborty
1 Like
Thanks Ryan, this approach means that an app can have a single listing within the marketplace, but provide differing capabilities through feature flagging/toggling based upon the defined capabilitySet which represents the edition selected by the partner.
Thank you all for your feedback, weâll explore what would be involved to also provide the this in the ACJS context.
1 Like
Hello Team,
Thanks a lot for entertaining this post and sharing your feedback. We are glad about the reception of this RFC as well as the live feedback from Team '24. Itâs wonderful to learn that we are broadly aligned in the direction.
A few key takeaways are the introduction of the ability to tag a current app to advanced directly and allowing an app with a subset of features to become standard. This is not something we will accommodate for the EAP but will be incorporated either as a fast follow or for GA. The other feedback regarding Free Edition is valuable too and will help shape our thinking when we get closer to Milestone 4 for Free Editions.
The team continues to stay focused on Milestone 1 (documentation releases) and Milestone 2 (EAP for Editions) for now. You will continue to hear from us through various channels as we make further announcements. Thank you and stay tuned. The RFC is hereby closed, and we hope we were able to answer most of your questions.
Thank you!
3 Likes