When to Be Agile: Ratings and Version Updates in Mobile Apps

Gad Allon, Georgios Askalidis, R. Berry, Nicole Immorlica, Ken Moon, Amandeep Singh
{"title":"When to Be Agile: Ratings and Version Updates in Mobile Apps","authors":"Gad Allon, Georgios Askalidis, R. Berry, Nicole Immorlica, Ken Moon, Amandeep Singh","doi":"10.2139/ssrn.3476286","DOIUrl":null,"url":null,"abstract":"Lean and agile models of product development organize the flexible capacity to rapidly update individual products in response to customer feedback. Although agile operations have been adopted across numerous industries, neither the benefits nor the factors explaining when firms choose to become agile are validated and understood. We study these questions using data on the development of mobile apps, which occurs through the dynamic release of new versions into the mobile app marketplace, and the apps’ customer ratings. We develop a structural model estimating the dependence of product versioning on (a) market feedback in the form of customer ratings against (b) project and work-based considerations, such as development timelines, scale economies, and operational constraints. In contrast to when they actually benefit from operational agility, firms become agile when launching riskier products (in terms of uncertainty in initial customer reception) and less agile when they are able to exploit scale economies from coordinating development over a portfolio of apps. Agile operations increase firm payoffs by margins of 20% to 80%, and interestingly, partial agility is often sufficient to capture the bulk of these returns. Finally, turning to a question of marketplace design, we study how the mobile app marketplace should design the display of ratings to incentivize quality (increasing app categories’ average user satisfaction rates by as much as 22%). This paper was accepted by Jayashankar Swaminathan, operations management.","PeriodicalId":82888,"journal":{"name":"Technology (Elmsford, N.Y.)","volume":"56 1","pages":""},"PeriodicalIF":0.0000,"publicationDate":"2019-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"7","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Technology (Elmsford, N.Y.)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.2139/ssrn.3476286","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 7

Abstract

Lean and agile models of product development organize the flexible capacity to rapidly update individual products in response to customer feedback. Although agile operations have been adopted across numerous industries, neither the benefits nor the factors explaining when firms choose to become agile are validated and understood. We study these questions using data on the development of mobile apps, which occurs through the dynamic release of new versions into the mobile app marketplace, and the apps’ customer ratings. We develop a structural model estimating the dependence of product versioning on (a) market feedback in the form of customer ratings against (b) project and work-based considerations, such as development timelines, scale economies, and operational constraints. In contrast to when they actually benefit from operational agility, firms become agile when launching riskier products (in terms of uncertainty in initial customer reception) and less agile when they are able to exploit scale economies from coordinating development over a portfolio of apps. Agile operations increase firm payoffs by margins of 20% to 80%, and interestingly, partial agility is often sufficient to capture the bulk of these returns. Finally, turning to a question of marketplace design, we study how the mobile app marketplace should design the display of ratings to incentivize quality (increasing app categories’ average user satisfaction rates by as much as 22%). This paper was accepted by Jayashankar Swaminathan, operations management.
何时变得敏捷:手机应用的评级和版本更新
产品开发的精益和敏捷模型组织了灵活的能力,可以根据客户反馈快速更新单个产品。尽管敏捷运维已经被许多行业采用,但是企业选择敏捷的好处和原因都没有得到验证和理解。我们使用手机应用开发的数据(游戏邦注:包括在手机应用市场中动态发布新版本)和应用的用户评级来研究这些问题。我们开发了一个结构模型来估计产品版本控制对(a)市场反馈的依赖,这种反馈以客户对(b)基于项目和工作的考虑为形式,例如开发时间表、规模经济和操作约束。与从运营敏捷性中获益相比,公司在推出风险较高的产品时变得敏捷(就初始客户接收的不确定性而言),而当他们能够通过协调开发一系列应用程序来利用规模经济时,就不那么敏捷了。敏捷运维使公司的收益增加了20%到80%,有趣的是,部分敏捷性通常足以获得这些收益的大部分。最后,我们将转向市场设计问题,研究手机应用市场应该如何设计评级显示以激励质量(将应用类别的平均用户满意度提高22%)。这篇论文被运营管理的Jayashankar Swaminathan接受。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信