Cross-side network effects—the phenomenon in which growth on one side of a platform increases value on the other—are rarely symmetrical, and treating them as such is a strategic error. Research by Peijian Song, Ling Xue, Arun Rai, and Cheng Zhang, published in MIS Quarterly, found that in a leading web browser platform's ecosystem, growth in platform usage produced long-term growth in both the number and variety of applications, while growth in applications produced only short-term growth in platform usage. For a C-suite executive, that asymmetry is not a footnote to platform strategy. It is the strategy: it determines whether you should spend to acquire users or to subsidize developers, and how you should govern the exchange between them.
The Asymmetric Reality of Cross-Side Network Effects
Most platform leaders learn the basic mechanics early: more users attract more developers, and more applications attract more users. What introductory treatments leave out is that these two loops do not run at the same speed or for the same duration. The underlying study frames this through value creation and value capture as distinct processes—value created by one side of the network may not be captured by the other participants in the way or on the timeline you expect.
The researchers' core observation, drawn from a time-series analysis of a leading web browser platform, is that one side may respond more quickly to the other, and one response may be more durable than the reverse. That difference is what they call temporal asymmetry. A platform whose leadership assumes both loops are identical will overinvest in the weaker, shorter-lived loop and underinvest in the durable one. The browser-ecosystem evidence suggests which is which.
Diagnosing Temporal Asymmetry: User-Side vs. App-Side Dynamics
Why would application growth pay off only briefly, while user growth compounds? The answer lies in how each side creates and captures value. As the study explains, the response of the application side to an increased installed user base "may not be instantaneous. But this response is likely to be lasting, resulting in a long-term user-to-application effect."
Developers do not mobilize the moment a platform crosses a user threshold; they observe it, commit resources, build, and their output accumulates over time. Users, by contrast, respond to new applications quickly—novelty and variety drive immediate engagement—but that response decays unless the app pipeline keeps renewing itself. Neither side is dispensable. But they occupy different positions in your growth engine: one is the flywheel, the other the accelerator.
Strategic Implications of User-to-App Network Effects
The long-term loop runs from users to applications. Sustained growth in platform usage delivers durable growth in both the number and the variety of apps, per the study's empirical findings. This effect is durable and sustained over time. Strategically, that means installed-base building is not merely a demand-side activity—it is your developer-attraction strategy. Every user you retain is an argument you do not have to make in cash to a prospective developer.
The practical consequence is patience in budgeting. Developer-side returns from user growth arrive with a lag, so the quarter in which you acquire users will not be the quarter in which app counts jump. Executives who expect immediate developer-side payoff from user investment will misread the lag as failure and abandon a compounding asset mid-cycle.
Strategic Implications of App-to-User Network Effects
The reverse loop behaves differently. Growth in the number and variety of applications leads to short-term growth in platform usage—a real effect, but one that may not be sustained long-term without continued app innovation or user engagement strategies. New apps move engagement immediately, but the lift fades; the study found no durable user-side payoff from app-side growth alone.
This does not make app investment worthless. It makes it perishable. Applications function as recurring marketing to your user base, renewed through each release, rather than as permanent infrastructure. A platform that subsidizes apps without also compounding its user base is buying spikes rather than building an ecosystem—the two investments must be sequenced with that in mind.
Platform Governance: Shaping Value Creation and Capture
Governance is where these asymmetries can be strengthened or quietly destroyed. The study focuses on two specific levers. First, app review time: long review times weaken the long-term cross-side effect of the user-side on the app-side, but not the short-term effect of apps on users. That is, slow reviews specifically erode the durable developer-attraction payoff of your growing user base—the very loop that compounds—while leaving the immediate user-response loop largely intact. A platform with fast user growth but sluggish reviews is amputating its own long-term effect.
Second, platform update frequency: frequent platform updates weaken the cross-side effects in both directions, disrupting the interdependence between users and developers. And behind both levers sits the broader distinction the researchers emphasize: effective platform governance establishes mechanisms that enable the ecosystem's adaptiveness, and governance policies must balance fostering ecosystem growth with securing the platform's own economic interests. Value created in the network is not automatically captured by you; governance decides who captures what.
Decision Framework: Diagnosing Asymmetric Network Effects
To analyze your own platform, map the reciprocal impacts between your two sides by their temporal nature—short-term versus long-term—before allocating capital. Use this matrix, built directly on the study's findings, to locate your platform's growth dynamics:
| Platform Side | Growth Driver | Observed Effect | Strategic Implication |
|---|---|---|---|
| User-side | Installed user base growth | Long-term growth in number and variety of apps; durable and sustained over time | Treat user acquisition and retention as the developer-attraction strategy; expect lagged payoff |
| App-side | New apps and app variety | Short-term growth in platform usage; immediate but may not be sustained without continued app innovation | Treat app investment as perishable engagement, not permanent infrastructure |
| Governance: app review time | Review process duration | Long review times weaken the user-to-app long-term effect, but not the app-to-user short-term effect | Speed reviews to protect the compounding loop; the short-term loop tolerates delay |
| Governance: platform updates | Update frequency | Frequent updates weaken cross-side effects in both directions | Stabilize the platform to preserve interdependence between sides |
| Governance overall | Governance design | Governance shapes how value is created for the ecosystem and captured by the platform | Balance ecosystem growth with the platform's own economic interests |
The diagnostic question for each row is the same: which loop is durable, which is perishable, and which governance policies are currently strengthening or eroding each? This framework derives from academic research on software platforms and requires adaptation to your specific platform context—the findings come from a browser-ecosystem time-series study, and your sides and governance mechanisms will differ.
Two boundaries on scope: this analysis addresses cross-side effects between user and application sides of a software platform. It does not address direct, same-side network effects, data network effects, or cross-platform effects among users of competing platforms.
Strategic Imperatives for Platform Leaders
The decision that follows from this diagnosis: align investments and governance policies with your platform's temporal asymmetries—prioritizing sustained user growth to attract developers over the long term, and app innovation to engage users in the short term, rather than treating the two loops as interchangeable. The study's evidence points to user growth as the compounding asset and app growth as the renewing one; your governance should protect the former while refreshing the latter.
The measurable indicator to watch is the relationship between growth rates on both sides: track the lag between user growth and subsequent app growth, and the immediate impact of new app releases on user engagement. If user growth is not followed by app growth within your platform's characteristic lag, review your app review times and platform update cadence before concluding the effect does not apply to you. That lag is where asymmetric platforms either compound or stall.
Sources
- Client Challenge — JSTOR
- Questromworld





