Seeking clarification on full page module with multi app compatibility

Forge
1

We are genuinely excited to see the original Forge platform vision of one Marketplace app being compatible with multiple Atlassian apps slowly but steadily coming to life, with the most recent steps being these two previews:

  1. Build Forge apps compatible with multiple Atlassian apps (Preview)
  2. Confluence full page module elevated to Preview

That being said, there are several known unknowns still that complicate resp. portfolio roadmap planning, and based on painful experiences as an early Forge adopter, likely some unknown unknowns as well :sweat_smile:

So given the encouraging mid-term vision for 1 is to “abandon the ‘required’ installation context”, and the Atlassian app context already being abandoned for 2 via a promising “New Preview URL (Forge Apps UI Service)”, I’m wondering why confluence:fullPage is a Confluence specific module in the first place that is now getting a sibling module for Jira (I’ll assume jira:fullPage), rather than this being a say core:fullPage module right away (similar to other platform app modules like core:action, rovo:agent, or dashboards:widget)? Specifically:

  1. Will either confluence:fullPage or jira:fullPage work in a current app with a required installation context, or do I need to use the one matching the required context?
  2. Can I use either confluence:fullPage or jira:fullPage in a future app without a required installation context, or are they not equivalent in subtle ways?
  3. Will there also be dedicated full page modules for other Atlassian apps like Compass and Bitbucket, or will those Atlassian apps be excluded from offering a full page UI for the time being, or can I use the Confluence/Jira modules as per 1/2 eventually (I realize Bitbucket is not yet multi-app enabled)?

Of course, I’m assuming there are technical constraints requiring these modules being Atlassian app specific rather than on the platform app level, but as always, providing at least a high level explanation would go a long way enabling mechanical sympathy and helping us make informed decisions about our multi app compatible architecture and portfolio composition in turn :slightly_smiling_face:

3 Likes
2

Hey Steffen,
Thank you so much for your feedback, it’s incredibly valuable to receive these kinds of questions and sentiment from our partners. Our current architecture requires modules to be defined within a product context. Our long term vision and engineering roadmap enables installation contexts outside of our core products, so you can expect this to evolve to be independent of product. This is where we see future and most value of full page module experiences. Our platform teams are doing foundational work to support this, but we cannot commit to timelines at this stage.

In terms of how Jira and Confluence full page modules will work:

Full page modules will need to be used with the required app context, which can be provided in two ways: either the app has the corresponding product as a required installation, or it adds the corresponding product context via cross-context apps.

  • e.g. Confluence full page module can be used in an app with Confluence as a required context

  • e.g. Confluence full page module can be used in an app with Compass as a required context if Confluence is defined as a cross-context app in the manifest.

I hope this gives you some insight into our direction and thinking. Let me know if you have any more questions.

Vicky, Product Manager for Forge UI

1 Like
3

Thanks for the detailed response @VickyHu, much appreciated! That provides sufficient guidance on how to proceed, though for the sake of clarity:

Given existing cross-context Forge modules like function, when you say “Our current architecture requires modules to be defined within a product context”, presumably you mean “requires UI modules”?

1 Like
4

Yes it means the full page UI modules!

1 Like