MétaCan
Menu
Back to cohort

Three things about mobile app commissions

2024· article· en· W4404402840 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueInformation Economics and Policy · 2024
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicDigital Platforms and Economics
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsMobile appsBusinessComputer scienceEconomicsWorld Wide Web

Abstract

fetched live from OpenAlex

Mobile app commissions paid by app developers to a monopolist device maker/app store operator are examined. Three results are demonstrated. First, unregulated app commissions are set at a level that maximises consumer surplus. Second, eliminating app commissions will likely lead to higher device prices. Third, requiring a menu of options for consumers as to how device makers receive subsidies from app developers constrains app commissions in a way that provides a more equal balance between consumer versus app developer interests. • Consumer Surplus Maximisation: The paper argues that in a monopoly setting, the app commission rate set by the device maker will be the rate that maximises consumer surplus, not total welfare. By maximising consumer surplus from apps, the device maker can charge a higher price for the device itself, thus maximising its own profits. • Zero Commission Leads to Higher Device Prices: The paper demonstrates that eliminating app store commissions will lead to higher quality-adjusted device prices if the profit an app developer makes from a single consumer is greater than the surplus that consumer receives from that app. • Required Menu as a Regulatory Mechanism: The paper proposes a regulatory mechanism requiring device makers to offer consumers a menu of options: paying standard prices for the device and apps with a commission, or paying a premium for the device to get discounted app prices.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScholarly communication, Insufficient payload (model declined to judge)
Consensus categoriesScholarly communication
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.838
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0030.017
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.001

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.010
GPT teacher head0.211
Teacher spread0.201 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it