SlashData counted more than 47 million developers worldwide in early 2025. That figure appears in every ecosystem deck, and it is almost useless for anyone running a mini-program catalog. The number that matters is measured in hundreds: the developers whose mini apps get published, updated and used inside a host. A population of 47 million is a market; a few hundred active publishers are a supply chain, and supply chains are what a catalog actually runs on.

The headline total also hides a maturity shift. SlashData put professional developers at 21.8 million in 2022 and 36.5 million in 2025, while growth over the preceding twelve months slowed to 10 percent. By language, JavaScript counted about 28 million users, with Java and Python near 23 million each. Greater China moved from 2.4 million to 5.8 million developers. For a runtime where authoring happens in web languages, the JavaScript figure is the one that predicts how many people can produce a mini app without retraining. The rest is context.

What does a developer relations program do with that? The State of Developer Relations report, cited through Develocity, breaks the discipline into three pillars: community at 93.8 percent, evangelism at 93.8 percent, and developer experience at 90.4 percent. The near-tie is telling. Almost every program says it supports community and spreads the word, while fewer put the same weight on the moment a developer meets an integration error at midnight. Yet developer experience is the pillar that decides whether a first mini app ever reaches a catalog.

Budget decisions suggest the boardroom has noticed. Twilio's developer evangelism effort passed 10 million registered developers and is widely credited with helping the company clear more than five billion dollars in 2025 revenue. Vercel reached a 9.3 billion dollar valuation in its September 2025 Series F. Neither company got there by counting registrations alone, but both made the developer audience legible to investors. Developer relations earns its budget when it can point to a shipped product, not a room full of attendees.

Tooling has changed the job as well. GitHub's 2025 Octoverse reported that nearly 80 percent of new users turned to Copilot in their first week, and that in August 2025 TypeScript overtook both Python and JavaScript as the most-used language. The Linux Foundation established a Developer Relations Foundation in 2025. When assistants handle syntax and typing, the scarce knowledge moves to integration: how a mini app is embedded, how it settles payments, how it behaves across host apps. That is precisely the layer a shared runtime owns.

Here are the figures that describe the funnel:

Signal2025 figureWhy a host catalog cares
Developers worldwideover 47 millionheadline reach, not active supply
Professional developers36.5 millionthe pool with shipping experience
JavaScript usersabout 28 millionthe closest proxy for mini-app authors
Developers in Greater China5.8 millionthe fastest-growing authoring region
Programs citing developer experience90.4 percentthe pillar closest to a working integration

The tempting conclusion is that reach converts. It often does not. Neo4j's APAC developer relations work over three years grew community members by 208 percent and attendance by 165 percent, with third-party conference coverage up 4.4 times, all from nine chapters. That is a strong result, and it also shows how easily activity can be mistaken for output. A program can fill rooms and still leave a catalog empty if nobody follows an event signup with a maintained mini app. The few hundred that matter are identified by version history, not by badge scans.

There is a second reservation. DevRel metrics reward visible moments: talks, launches, hackathon demos. Distribution rewards invisible ones — SDK upgrades, deprecation notices, predictable review cycles. A team measured on attendance will optimize for attendance. A team measured on the number of mini apps that survive six months will write better documentation and answer harder questions, because those are the things that keep a publisher active after the novelty fades. The choice of metric is the choice of strategy.

For a host, the practical question is not how to reach 47 million developers. It is how to recognize the few hundred who already build on the platform and remove the friction they hit. A shared runtime such as Cross Mini App can make those publishers visible through shipped listings and update history, so developer relations starts from real supply rather than a global estimate. Reach is cheap to report. Retention is the part that belongs in the plan.

Sources