Thank you so much for taking the time to respond. We collected data on 356 apps, which is fantastic and is helping us better understand the blockers you are experiencing in the shift to the cloud. As promised, I’ve read each response carefully and surfaced this information to the teams to help understand your blockers in the transition to cloud. We are currently exploring the implications of this information.
Although not an exhaustive list, some of the most frequent challenges we heard expressed in this survey:
We heard that limits such as the 10s Forge runtime timeout and storage size are blockers for Forge adoption, especially those developing more complex apps.
More sophisticated data storage capabilities is an essential requirement for Forge, particularly relational capabilities. We heard that at least 31% of apps that store data require relational capabilities.
Many of you shared that the lack of extensibility parity between Connect and Forge was a blocker for Forge development. Confluence & Jira capabilities were also the clear blocker for most partners attempting to close the gap in features between on-premise and cloud apps.
Parity of UI extensibility
UI extensibility does not yet support the requirements of more complex apps.
Tech stack limitations
Lack of Forge’s support for various tech stacks, particularly language can be a blocker for some of you.
We’ve heard your concern about the future of Atlassian’s focus on the cloud:
- What this means for migrating your app to the cloud
- And for the migration of customers’ data.
Especially for smaller teams, we heard that it could be challenging to keep up with the number of asks we make of you. Forge and the move to the cloud are yet another ask, and we understand that you need to make trade-offs when deciding priorities.
Value of Forge to you and your organisation
Many of you shared that you weren’t sure of the value that Forge would bring to your organisation and app(s), especially how building your app on Forge compares to the value of spending your time on other efforts. We understand that Forge may not be ready for every partner now, but it will be in the future.
Extension points for Bitbucket and JSM
We heard that many of you intend to develop a Forge app for either Bitbucket & JSM but are limited by what you can build and whether you can monetise your apps developed for these products.
Once again, we appreciate your taking the time to share this feedback. The teams are currently discussing how we address these challenges.
What do you think of this list? Let us know if there are any significant omissions. If you missed the survey, let me know your thoughts in the comments below. Or feel free to share your thoughts on your app(s) in the survey link, I will keep this open and review any new data. We will be asking you for more technical information on your apps in the near future and this information will help us build in the right direction.
Something that we were surprised by was the absence of a few requests that we heard were important in our conversations with many of you:
- End-user consent
- Team ownership of an app
So tell me, how do those requirements weigh up against that list? Are they blockers we should be prioritising as well? I’d love to hear what you think.
Your friendly neighbourhood researcher,