The Terminology Shift
Atlassian recently made a subtle but significant change to their admin panel: what was once called "Products" is now labeled "Apps." This seemingly minor terminology shift has sparked considerable discussion in the Atlassian community.
The Change in Context
Before
- "Products" included Jira, Confluence, Bitbucket, etc.
- Clear distinction between Atlassian products and third-party apps
- Products had their own dedicated section in admin
After
- Everything is now under "Apps"
- First-party and third-party apps share the same space
- Unified management interface
Arguments for the Change
1. Platform Thinking
The shift reflects Atlassian's evolution into a platform company:
- Core products are now "first-party apps"
- Equal footing with marketplace apps
- Encourages ecosystem development
2. Consistency
Users now have:
- One place to manage all applications
- Unified settings and permissions
- Consistent user experience
3. Future Flexibility
The change allows Atlassian to:
- Easily add new capabilities as apps
- Bundle and unbundle features
- Offer more flexible licensing
Arguments Against the Change
1. Brand Dilution
Critics argue:
- Jira isn't just an "app"—it's a platform
- The term "app" diminishes perceived value
- Enterprise customers expect "products"
2. Confusion
The change has caused:
- Uncertainty about what's included in licenses
- Questions about support levels
- Difficulty distinguishing core vs. optional
3. Market Perception
There are concerns about:
- How competitors might leverage this messaging
- Customer confusion during sales processes
- Perceived commoditization
Our Analysis
After careful consideration, we believe this change reflects a broader industry trend and Atlassian's strategic vision:
The Platform Strategy
Atlassian is positioning itself as a platform for work management, not just a product vendor. This means:
- Core capabilities (Jira, Confluence) become foundational layers
- Additional functionality comes from apps (internal and external)
- The ecosystem becomes the differentiator
Customer Impact
For most customers, the practical impact is minimal:
- Same functionality, different label
- Better unified management
- More integration possibilities
Long-Term Vision
We expect Atlassian to:
- Continue investing in platform capabilities
- Make it easier for customers to customize with apps
- Potentially offer more modular licensing
Conclusion
Is it a vision or an error? We lean toward vision—but with caveats.
The change makes strategic sense for Atlassian's platform ambitions. However, the execution could have been smoother with better communication about what hasn't changed (licensing, support, commitment to core functionality).
Time will tell whether customers embrace this new mental model or continue to think in traditional product terms. Either way, the underlying value proposition remains strong.