Author
Listed:
- Joe Cox
(University of Portsmouth, Portsmouth PO1 2UP, United Kingdom)
- Paul Crosby
(Macquarie University, Macquarie Park, New South Wales 2109, Australia)
- Jordi McKenzie
(Macquarie University, Macquarie Park, New South Wales 2109, Australia)
Abstract
Backward compatibility is a governance strategy that can be adopted by platform owners to build indirect network effects and encourage owners of older compatible software to update to newer hardware models. Previous research shows backward compatibility has a positive effect on hardware sales. However, there is limited evidence concerning the other associated costs and benefits. In particular, there is a lack of evidence on the effect of backward compatibility on software sales despite its importance in understanding the full range of possible network and sales displacement effects associated with the strategy. Using weekly software-level sales data from the U.S. video gaming industry, we find that backward-compatible hardware associates with increased sales of software released for the previous hardware generation. However, we find that the introduction of backward compatibility may not increase the sales of new hardware if the feature is not available immediately at launch. Further, we show that the increased sales of software for the old hardware platform may cannibalize software sales for the new platform. Overall, our results suggest that backward compatibility is time-sensitive and involves several important trade-offs. We, therefore, conclude that the use of backward compatibility needs to be carefully considered by platform owners prior to implementation.
Suggested Citation
Joe Cox & Paul Crosby & Jordi McKenzie, 2023.
"Don’t Look Back? Backward Compatibility in the Video Gaming Industry,"
Strategy Science, INFORMS, vol. 8(3), pages 387-404, September.
Handle:
RePEc:inm:orstsc:v:8:y:2023:i:3:p:387-404
DOI: 10.1287/stsc.2022.0177
Download full text from publisher
Corrections
All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:inm:orstsc:v:8:y:2023:i:3:p:387-404. See general information about how to correct material in RePEc.
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
We have no bibliographic references for this item. You can help adding them by using this form .
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Chris Asher (email available below). General contact details of provider: https://edirc.repec.org/data/inforea.html .
Please note that corrections may take a couple of weeks to filter through
the various RePEc services.