At Developer Day '22, we’ll be closing out the event with a very special guest: Atlassian co-founder and co-CEO Mike Cannon-Brookes. Mike will answer a few questions from the audience during his pre-recorded remarks.
Post in this thread to submit your question, or you can send me your question in a direct message. Our time for Q&A is limited, but we’ll select a few questions from this list to address during the broadcast.
PS - Developer Day '22 is coming up on June 9th. If you haven’t signed up yet, snag your free ticket here. We’ve just published the full agenda on the event page - check out talks from Anu Bharadwaj, Atlassian COO, Adam Strickland, Principal Solutions Architect at AWS, partners from the Atlassian Ecosystem, and more.
Mike, this is Leo from Move Work Forward.
- What are the App’s monetization plans for Bitbucket Cloud and Compass?
- Is there a way to understand better where Atlassian is moving with products and functionality in order to develop apps that close the gaps?
Mike, this is David from Appfire / Jira Misc Workflow Extensions (JMWE) and Jira Misc Custom Fields (JMCF).
- When will Atlassian start building its own products on the same platform(s) Vendors must use to build apps? This is the only way to ensure the quality of the platform(s), and this is what Salesforce (the role model of many SaaS companies) did when they built the Salesforce Platform (formerly Force.com) concurrently with Wave ten years ago.
Can you please either make a public statement on the immediate deprecation of Connect as a supported platform, or make sure to internally communicate to your engineering teams that they should continue to support it and stop letting the currently dominant platform for creating Cloud apps fade away? The current situation is creating a lot of uncertainty amongst Atlassian Marketplace Partners, as well as overhead for working around either lack of support or silent deprecation of previously supported features.
For reference, see
Mike, this is David (again) from Appfire / Jira Misc Workflow Extensions (JMWE) and Jira Misc Custom Fields (JMCF).
As I’m sure you realize, the customer value delivered by Connect apps still far exceeds that of Forge. And yet, there has been virtually no investment in Connect for the last few years. As Ecosystem partners (vendors), we understand that Forge promises a range of advantages over Connect, but Forge is not yet viable for most apps, and will likely remain so for another few years.
Why isn’t Atlassian continuing to invest in the platform, Atlassian Connect, which is still key to the success of Atlassian’s Cloud strategy? This would allow us to continue to deliver value to our cloud apps rather than thwarting our progress as is the case today. Furthermore, most of these investments (such as REST API improvements but not only) would actually carry over naturally to Forge.