Is it better for Unity to focus on expanding built-in features or supporting a robust third-party asset ecosystem?

Introduction

The trade-off between expanding built-in features and supporting a robust third-party asset ecosystem is a critical decision for Unity's product strategy. This scenario involves balancing internal development with external innovation, each with its own set of advantages and challenges. I'll analyze this trade-off by examining the product context, stakeholder impacts, metrics, and potential outcomes to provide a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about Unity's current market position and competitive landscape. Could you provide more insight into our market share and primary competitors?

Why it matters: Helps frame the decision in the context of competitive pressures Expected answer: Unity has a strong position but faces increasing competition Impact on approach: Would influence whether we prioritize rapid feature development or ecosystem growth

• Business Context: Based on Unity's business model, I assume we generate revenue from both licensing and asset store sales. What's the current revenue split between these streams?

Why it matters: Informs the financial impact of focusing on either built-in features or third-party assets Expected answer: Revenue is split roughly evenly between licensing and asset store Impact on approach: Would help balance the trade-off to maintain overall revenue growth

• User Impact: I'm considering the different user segments within Unity's ecosystem. Can you share more about the distribution of professional studios vs. indie developers in our user base?

Why it matters: Different user segments may have varying needs and preferences for built-in vs. third-party features Expected answer: A mix of both, with a growing indie developer segment Impact on approach: Would influence which group to prioritize in the short-term while planning for long-term balance

• Technical: Regarding our current architecture, how modular is Unity's core engine in terms of integrating third-party assets?

Why it matters: Affects the feasibility and effort required to support a robust third-party ecosystem Expected answer: Fairly modular, but with some integration challenges Impact on approach: Would determine the level of investment needed in platform infrastructure

• Resource: Considering our current team structure, how are our engineering resources allocated between core engine development and ecosystem support?

Why it matters: Helps understand our capacity to pursue either strategy effectively Expected answer: Currently more focused on core engine development Impact on approach: Would influence whether we need to reallocate resources or hire for specific skills