NO.070 Mobile App Store Analytics

Shonan Village Center

October 19 - 22, 2015 (Check-in: October 18, 2015 )


  • Meiyappan Nagappan
    • Rochester Institute of Technology, USA
  • Ahmed E. Hassan
    • Queen’s University, Canada
  • Yasutaka Kamei
    • Kyushu University, Japan


Description of the meeting

Today, software engineering research focuses on traditional software systems like the Firefox web browser or Microsoft Windows, which take years to develop and teams of designers, developers and testers. Software engineering is rapidly changing though. Emerging domains, such as mobile devices, are growing rapidly and depend heavily on new software operating systems like Android and the applications that they run, commonly referred to as apps. Over the past few years, we have seen a boom in the popularity of mobile devices and mobile apps which run on these devices [3]. Recent market studies predict that the global mobile app economy is expected to be worth $143 billion by 2016 [16]. Thus there exists considerable motivation for the research community to solve the challenges faced by the mobile app developers.

However, unlike traditional software, the distribution mechanism for mobile apps are very different ? they are released through app markets (e.g., Google Play and Apple’s App store). The key differentiating factor in an app store is that it is a democratic platform, i.e., both large companies with established products Adobe Reader from Adobe, and Timberman from Digital Melody (a company with 5 employees1), can release their apps through the same mechanism for the users to download and install. The data that these mobile app markets contain can be used by software engineering researchers to compile new empirical results that can help mobile app developers.

Additionally, the app markets allow users to post reviews of the apps. This is very different from traditional software. Mobile app developers get continuous feedback from users that can be leveraged to help them. For example, prior work leveraged user reviews to extract user-faced issues [11, 10], and new requirements [5]. However, today the review system for mobile apps is identical to that of books sold on an e-commerce website such as Amazon. While books are products too, they are very different from mobile apps in that books are not updated every few weeks like most mobile apps. Therefore in the case of books, the ratings and reviews collected for a book is all with respect to one version of a book, while the ratings and reviews collected for an app are about all the versions of an app. Hence the question arises whether the review systems of books is the best system for mobile apps or not?

Finally, the app stores provide a central location for all the apps, making it easy for researchers to mine the store for meta-data of the apps and the apps themselves [4, 25]. Using the data from the app stores, several companies like App Annie2, and Distimo3 have even built successful businesses selling intelligence gained from observing the evolution of several hundred thousand apps in the app stores.

Although Software Analytics is gaining popularity over the last year, with even a Dagstuhl seminar 4 in June 2014, much of software engineering research today is still focused on traditional “shrink wrapped” software, such as Mozilla Firefox, Eclipse or Microsoft Windows [18]. Recently however, researchers have begun to focus on mobile apps and the related software engineering issues. For example, the 2011 Mining Software Engineering Challenge focused on studying the Android mobile platform [22]. Other work focused on issues related to code reuse in mobile apps [19], monetizing apps through ads [21, 20], mining mobile app data from the app stores [8], testing mobile apps [14, 13], addressing device fragmentation [10, 6], resource usage and optimization [9, 17, 12], and teaching programming on mobile devices [24].

Even with all the above papers on mobile apps, there is no central venue to bring all the cross-disciplinary researchers together. There is therefore, a dire need for a community to be built around the line of research with respect to mobile app store analytics.
Hence, with a strong recent body of work like the one’s stated above, and the lack of a venue to build a research community around the challenges and opportunities, now is the time for a Shonan meeting on the issue of `Mobile App Store Analytics’. The proposed seminar would focus on research where the Mobile App Stores, and the data that they have are mined for insights into mobile app development. We intend to bring researchers in multiple disciplines from around the world in one place to discuss the future directions in the area of mobile app store analytics. Each of the researchers we intend to invite (Section 5), has conducted research and published papers on deriving insights from mining mobile app stores. Additionally the three organizers have prior experience in organizing successful workshops [15], research summits 5 6, and Shonan seminars. 7

4.1 Emerging Challenges to be Discussed in the Meeting

In addition to the mobile app challenges that are currently being addressed in the research community, there are several emerging challenges that we plan to discuss at the NII Shonan meeting.
App development paradigm. Mobile apps are developed using several different paradigms – native to the mobile device platform, JavaScript based app engines, and HTML5. By analyzing collections of apps from several different paradigms, researchers can recommend
the paradigms that provide the best user experience.

1 team

Feedback Mechanism. Given that users can directly provide feedback to the developers via the app stores (such feedback is publicly available for anyone to mine), how can the developers leverage this feedback? What tools can we build to help the developers digest the feedback and transform the user reviews into development tasks (fixing issues or building features).

Fragmentation. A major challenge that mobile app developers have to face is to deal with the fragmentation among different devices and OS platform versions, especially when dealing with Android devices [7]. We plan to discuss how fragmentation impacts mobile app developers and what software engineering researchers can do to help mobile app developers cope with fragmentation.

Changing role of developers. Unlike traditional software, mobile apps are often developed by very small or single-developer teams [23]. Therefore, the role of mobile app developers is very different than developers working on desktop applications, such as Windows and Eclipse. For example, mobile app developers often need to play the role of architect, designer, developer, tester, maintainer and even marketer or business manager. Therefore, we plan to discuss on how we can help developers effectively choose a business model (advertisement or in-app purchases based) considering both the reliability of the technology needed to implement the business model (libraries) and the revenue that it can generate.

Legal issues related to mobility. One issue that mobile apps have to deal with is that mobile devices frequently move to different locations. This mobility can cause legal issues (e.g., an app may be licensed to work in Asia, but not North America). Therefore, developers need to design their apps to deal with such legal issues. Can we learn from other apps in the store that dealt with such issues?

4.2 Academic Impact

As described in subsection 4.1, we intend the NII Shonan meeting to have lively discussions about the various challenges in order identify the key issues that can be solved by academics. We also expect the software analytics researchers to be able to find suitable collaborators for the problems they decide to work on, among the other invitees that we plan to invite. As presented in Section 5, the researchers outside the domain of software analytics have worked extensively on research related to mobile apps ranging from static analysis to testing tools to energy analysis. We expect that these collaborations will push the boundaries of research with respect to mobile apps through many strong publications.

4.3 Industrial Impact

It is estimated that 1 in 8 software developers, develop mobile apps [16]. Such developers have developed over 1,200,000 apps in the Apple App store and over 1,300,00 apps in the Google Play store [2]. There are over 230,000 developers for the iOS platform alone in the United States [1]. With billions of dollars in revenue benefitting millions of developers and hundreds of millions of users, the impact of research on mobile app store analytics, and how developers can learn from other developers is considerable.


[1] Creating jobs through innovation. Online:, Last accessed Aug 2014.
[2] Number of apps available in leading app stores as of July 2014. Online:, Last accessed Aug 2014.
[3] Berg Insight. The mobile application market. Online:, Last accessed Oct 2013.
[4] S. Dienst and T. Berger. Static analysis of app dependencies in android bytecode, 2012. Tech. Note, available at
[5] L. V. Galvis Carre~no and K. Winbladh. Analysis of user comments: an approach for software requirements evolution. In Proceedings of the 2013 International Conference on Software Engineering, ICSE ’13, pages 582-591, 2013.
[6] D. Han, C. Zhang, X. Fan, A. Hindle, K. Wong, and E. Stroulia. Understanding android fragmentation with topic analysis of vendor-speci c bugs. In 20th Working Conference on Reverse Engineering (WCRE), pages 83-92, 2012.
[7] D. Han, C. Zhang, X. Fan, A. Hindle, K. Wong, and E. Stroulia. Understanding android fragmentation with topic analysis of vendor-speci c bugs. In Reverse Engineering (WCRE), 2012 19th Working Conference on, pages 83-92, 2012.
[8] M. Harman, Y. Jia, and Y. Z. Test. App store mining and analysis: Msr for app stores. In Proceedings of the 9th Working Conference on Mining Software Repositories (MSR ’12), Zurich, Switzerland, 2-3 June 2012.
[9] A. Hindle. Green mining: A methodology of relating software change to power consumption. In Mining Software Repositories (MSR), 2012 9th IEEE Working Conference on, pages 78-87, 2012.
[10] H. Khalid, M. Nagappan, E. Shihab, and A. E. Hassan. Prioritizing the devices to test your app on: A case study of android game apps. In 22nd ACM SIGSOFT International Symposium on the Foundations of Software Engineering (FSE 2014). ACM, 2014.
[11] H. Khalid, E. Shihab, M. Nagappan, and A. Hassan. What do mobile app users complain about? A study on free ios apps. Software, IEEE, 2014.
[12] D. Li, S. Hao, W. G. J. Halfond, and R. Govindan. Calculating source line level energy information for android applications. In Proceedings of the 2013 International Symposium on Software Testing and Analysis, ISSTA 2013, pages 78-89, 2013.
[13] A. Machiry, R. Tahiliani, and M. Naik. Dynodroid: an input generation system for android apps. In Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering, ESEC/FSE 2013, pages 224-234, 2013.
[14] H. Muccini, A. Di Francesco, and P. Esposito. Software testing of mobile applications: Challenges and future research directions. In International Workshop on Automation of Software Test, pages 29-35, June 2012.
[15] M. Nagappan, E. Shihab, and A. E. Hassan. Challenges in mobile apps: a multi-disciplinary perspective. In Center for Advanced Studies on Collaborative Research, CASCON ’12, Toronto, ON, Canada, November 18-20, 2013, pages 378-381, 2013.
[16] A. Pappas. Developer economics: App market forecasts 2013-2016. Online:, Last accessed Oct 2013.
[17] A. Pathak, Y. C. Hu, and M. Zhang. Where is the energy spent inside my app: fine grained energy accounting on smartphones with eprof. In Proceedings of the 7th ACM european conference on Computer Systems, EuroSys ’12, pages 29-42, 2012.
[18] B. Robinson and P. Francis. Improving industrial adoption of software engineering research: a comparison of open and closed source software. In Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement, ESEM ’10, pages 21:1-21:10, 2010.
[19] I. J. M. Ruiz, M. Nagappan, B. Adams, and A. E. Hassan. Understanding reuse in the android market. In IEEE International Conference on Program Comprehension (ICPC), page To appear, June 2012.
[20] I. M. Ruiz, M. Nagappan, B. Adams, T. Berger, S. Dienst, and A. Hassan. On ad library updates in android apps. IEEE Software, 2014.
[21] I. M. Ruiz, M. Nagappan, B. Adams, T. Berger, S. Dienst, and A. Hassan. On the relationship between the number of ad libraries in an android app and its rating. IEEE Software, 2014.
[22] E. Shihab, Y. Kamei, and P. Bhattacharya. Mining challenge 2012: The android platform. In MSR, pages 112-115, 2012.
[23] M. D. Syer, M. Nagappan, B. Adams, and A. E. Hassan. Revisiting prior empirical ndings for mobile apps: An empirical case study on the 15 most popular open-source android apps. In Proceedings of the Conference of the Center for Advanced Studies on Collaborative Research, Nov 2013.
[24] N. Tillmann, M. Moskal, J. de Halleux, M. Fahndrich, J. Bishop, A. Samuel, and T. Xie. The future of teaching programming is on mobile devices. In Proceedings of the 17th ACM annual conference on Innovation and technology in computer science education, ITiCSE ’12, pages 156-161, 2012.
[25] N. Viennot, E. Garcia, and J. Nieh. A measurement study of google play. In The 2014 ACM International Conference on Measurement and Modeling of Computer Systems, SIGMETRICS ’14, pages 221-233, 2014.