Exploring the Development of Micro-apps: A Case Study on the BlackBerry and Android Platforms
Authors:
- Mark D. SyerMSMark D. Syer
- Bram AdamsBABram Adams
- Ying ZouYZYing Zou
- Ahmed E. HassanAHAhmed E. Hassan
- 1 September 2011
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 55-64
Abstract
The recent meteoric rise in the use of smart phones and other mobile devices has led to a new class of applications, i.e., micro-apps, that are designed to run on devices with limited processing, memory, storage and display resources. Given the rapid succession of mobile technologies and the fierce competition, micro-app vendors need to release new features at break-neck speed, without sacrificing product quality. To understand how different mobile platforms enable such a rapid turnaround-time, this paper compares three pairs of feature-equivalent Android and Blackberry micro-apps. We do this by analyzing the micro-apps along the dimensions of source code, code dependencies and code churn. BlackBerry micro-apps are much larger and rely more on third party libraries. However, they are less susceptible to platform changes since they rely less on the underlying platform. On the other hand, Android micro-apps tend to concentrate code into fewer files and rely heavily on the Android platform. On both platforms, code churn of micro-apps is very high.Keywords
This publication has 8 references indexed in Scilit:
- Android: Changing the Mobile LandscapeIEEE Pervasive Computing, 2010
- Development Platforms for Mobile Applications: Status and TrendsIEEE Software, 2010
- Mobile Application Development: Essential New Directions for IT2010
- Visiting Mobile Application Development: What, How and Where2010
- Beanplot: A Boxplot Alternative for Visual Comparison of DistributionsJournal of Statistical Software, 2008
- Towards a Theoretical Model for Software Growth2007
- Architecture recovery of web applications2002
- An experimental investigation of software metrics and their relationship to software development effortIEEE Transactions on Software Engineering, 1989