Hi, As a vendor with apps in both Jira and Confluence we’re overall impressed with the idea of cross-product apps. As some vendors had mentioned the primary and secondary context makes it feel awkwardly still product specific. Either build a “Jira app with a side job in Confluence” or a Confluence app that can also work with Jira.
I’m sure the design team considered just making 'Atlassian Cloud" apps that had a compatibility flag for Jira, Confluence, Compass? Can I ask why that didn’t work? It would seem to simplify some of the marketplace admin items (e.g. the app shows up everywhere its compatible), and remove the complexity of primary vs secondary.
And as a few people mentioned, this current primary/secondary is going to prevent omni-directional installs (e.g. Jira first, or Confluence first). A true “Atlassian Cloud” app could be installed and enabled for any product first. But also gives the customer (and vendor) an opportunity for an easy upgrade sale.
And then billing would be done equivalently… assume you would just make the pricing tier configuration available for all “compatible” products. If they had 10 Jira users and 1000 confluence users the customer is charged for both sides.
Just a thought… thank you for reading.
Chris
Digital Rose