Developer Funnel
Awareness & Conversion
A large-scale quantitative study to understand how developers discover and evaluate Meta Horizon OS — mapping the full journey from awareness to intent to build, and identifying the highest-leverage interventions to grow the developer ecosystem.
A Platform with an Awareness Problem
Meta Horizon OS was positioning itself as the leading XR development platform but the developer growth strategy was operating without a clear picture of the top-of-funnel dynamics. How many developers had even heard of the platform? How did they hear about it? What did they think when they did encounter it? And what was actually driving developers from passive awareness into active consideration and, ultimately, committed development?
The platform's ambition required a larger developer base. But growing that base effectively meant understanding the biggest opportunities for driving growth.
in fieldwork
Without a quantitative baseline of awareness, consideration, and intent, the team had no way to evaluate whether existing outreach was working, which developer segments were most actionable, or what the highest-leverage interventions would be.
Three Questions to Guide the Strategy
The study was designed to answer three core strategic questions:
Where do developers sit across awareness, consideration, and intent? What proportion of the addressable market is at each stage, and how large is the undecided segment?
What is preventing developers who are aware of the platform from moving forward? What specific concerns or beliefs slow down funnel conversion?
What factors — skills, SDK familiarity, value perceptions, community channels — are statistically associated with consideration and intent to build?
A Quantitative Funnel Study Across Five Markets
The study used an online survey distributed via email to a third-party sample of eligible developers — those who had launched Android apps (2D/3D), VR/MR apps, or content on UGC platforms. The geography was designed to capture both established and high-growth developer markets, spanning the US, Germany, India, Brazil, and Canada.
| Dimension | Detail |
|---|---|
| Sample size | 1,441 developers |
| Audience | Developers who had launched Android (2D/3D), VR/MR, or UGC platform apps |
| Markets | US, Germany, India, Brazil, Canada |
| Field period | June 23 – August 25, 2025 (~2 months) |
| Distribution | Email invitation via vendor using third-party survey platform |
Three analytical methods were combined to generate both descriptive and causal insight. Descriptive statistics and column proportion testing established the headline funnel metrics and identified statistically significant differences across subgroups. The most analytically intensive outputs came from a series of logistic regression models — one for consideration, one for intent — which isolated the independent statistical drivers of each funnel outcome while controlling for other factors.
Using logistic regression rather than correlation analysis was a deliberate methodological choice. It allowed the team to move beyond "what's associated with intent?" to answer the more actionable question: "what independently drives intent, after accounting for everything else?" This is what makes the Odds Ratios interpretable and usable as prioritisation tools for marketing and product teams.
A Leaky Funnel with a Mismatched Message
The data revealed a funnel with substantial opportunity as well as a set of structural barriers that meant raw awareness spending alone would not drive growth. Several interlocking problems emerged.
1 — The Awareness Gap
Nearly six in ten developers had never heard of Horizon OS. At 42% overall awareness, the platform's addressable market was being meaningfully constrained before any consideration or intent dynamic even came into play. This wasn't a conversion problem or a messaging problem — it was a reach problem that had to be solved first.
Data directionally representative. Near-term intent = plans to start development within the next year.
2 — The Undecided Middle
Among developers who were aware, 60% expressed some level of consideration — a reasonably strong conversion rate. But the critical finding was in what happened next: only about a third of aware developers planned to start development within the next year. A full 35% of aware developers sat in an undecided state. This undecided segment, not the rejectors, represented the most actionable opportunity.
The undecided segment is the strategic priority. These developers are already aware, haven't dismissed the platform, but have not yet received a compelling enough reason to commit. Converting even a fraction of this group would represent a significant step-change in ecosystem growth.
3 — The Wrong Conversation
The dominant adoption barriers were demand skepticism (46% worried about insufficient users or market traction) and perceived effort to build, rather than actual technical capability gaps. A misalignment between what marketing was emphasising and what developers actually cared about was compounding the problem.
4 — What Actually Moves the Needle
The logistic regression models produced the most actionable outputs of the study, identifying the independent statistical drivers of each funnel stage. The results gave marketing and product teams a clear, ranked set of levers to act on.
Bar lengths are proportional to effect size. Data directionally representative.
5 — Geographic Signal
Developers in India and Brazil showed dramatically higher near-term development intent compared to US and Canadian counterparts — a country-level odds ratio of approximately 5 in the regression model. This was one of the strongest signals in the entire dataset, suggesting these markets represented disproportionate near-term growth opportunity if targeted appropriately.
6 — The Mobile Developer Blind Spot
Mobile developers were identified as a high-value, underleveraged segment. They have existing Android skills that transfer directly to Horizon development, and app porting represents a low-effort path to entering the ecosystem. Yet mobile developers had the lowest awareness of the porting option, with nearly 60% unaware — meaning the most natural acquisition pathway was being systematically undersold.
- Mobile developers have directly transferable Android skills — making them a low-friction entry point for ecosystem growth
- ~60% of mobile developers were unaware that porting their existing app was even an option
- No dedicated messaging or acquisition pathway existed for this segment at the time of the study
Two Strategic Imperatives
The data converged on two clear, sequenced priorities — each grounded directly in the regression findings.
Turn Awareness into Action: Lead with Profit, Provide the Proof. The regression showed that funding access and monetisation clarity were the two strongest drivers of intent, but current messaging was not leading with this. The recommendation was a GTM pivot: answer the business case first, before addressing technical capability.
Activate Mobile Devs to Port: Establish the Opportunity, Emphasise the Ease. A dedicated acquisition strategy for mobile developers built around a clear value proposition: "Generate incremental revenue from a new market with your existing app."
The regression finding that funding access (OR ~3×) and monetisation clarity (OR ~2×) were the two strongest drivers of intent had a direct implication for marketing: the current over-index on technical features was leaving the most persuasive arguments unmade. The GTM pivot needed to answer four questions that undecided developers were asking:
- Can I make money? — Showcase developer success stories and monetisation outcomes prominently in outreach
- Is there a real market? — Publish platform traction reports to directly address demand skepticism (the #1 stated barrier)
- Can I access support? — Make funding and incentive programmes highly visible and easy to apply for
- Is it worth the effort? — Streamline onboarding; mobilise trusted technical voices (Android/Kotlin ecosystem figures) to demystify migration
Mobile developers are a large, skills-compatible, and currently underserved segment with a clear path to entering the ecosystem. The challenge was not capability — it was awareness and perceived effort. The recommendation required a purpose-built acquisition strategy:
| Action | Rationale |
|---|---|
| Porting case studies | Commission and publish case studies that explicitly state the percentage of code change required. Low effort should be the centrepiece of the argument — not a footnote. |
| Interactive porting guides | Create step-by-step tooling that lets mobile developers estimate effort before committing — reducing the perceived risk of exploring the platform. |
| Targeted community outreach | Invest in campaigns targeting mobile developer communities on forums, YouTube, and blogs — the channels developers cited as most trusted for platform discovery. |
On channel strategy: The study found that developers primarily learn about platforms through community-driven channels — YouTube, online forums, and blogs. Prioritising these over paid media was a direct implication of the data, not a default assumption.
Note: Due to confidentiality constraints, all data, percentages, diagrams, and visualizations are directionally representative, not exact reproductions.