Study of Agility in Mobile Application Development

Vanessa N. Cooper and Hisham M. Haddad

Department of Computer Science
Kennesaw State University
Building 11, MD# 1101
Kennesaw, GA 30144

Abstract - Not only has Agility infiltrated enterprise
and consumer mobile application development, but it
has also become an integral part of most IT
departments and the standard for younger generation
developers. Despite the numerous benefits of Agile
development, software developers often find out that
there are also several pitfalls to avoid during mobile
application development. In this study, we explore the
potential pitfalls of incorporating agility into the
development of mobile applications. The motivation
behind this work stems from professional and personal
experience of the primary author. As a junior software
developer in the mobile application age, the primary
author has experienced first-hand the demands of a
we want it now market.
Keywords: agile development effects, mobile computing.
I. INTRODUCTION
The year is 2013. Mobile development is the hottest
software skill for the youth. Social media is how everyone
communicates; people now have the option to digitally
share photos and daily schedules with their friends and
family. Almost all software requires substantial consumer
interactivity. The entire world now revolves around how
quickly consumers have access to what they want. We are
living in the We Want It Now era.
where changing requirements is the most faced challenge
in the software industry. Furthermore, frequent and
rigorous testing ensures that a high-quality product will be
delivered to the consumer coupled with heavy customer
involvement and short-term feedback. Ideally, Agile
software development methods are good practice,
allowing the construction of a highly collaborative product,
and accommodate fast development with short-term
feedback. Thats the primary reason that many developers
are now embracing agile development, especially for
mobile application development.
Other reasons why most customers obsess over the
constant tweaks of their mobile apps lie within the profit
margin and popularity of this new craze. Figure-1 [17]
shows the total number of applications and downloads
over a 2-year period between June 2008 and June 2010.
The growth appears to be almost exponential. Figure 2
[16] outlines some estimated figures of mobile application
sales and revenue. With these statistics, its easy to
understand why businesses are rushing to brand
themselves in the mobile application industry.

Smart, mobile devices are the fastest growing

computing platform with an estimated 1.6 billion device
users by the end of 2013 (compared to only 2 billion PC
users) [7]. Even though the mobile industry is a massive,
mobile computing is still relatively new. Since there are
not many open-source mobile examples to follow many
developers must quickly adapt to the environment and the
ever-changing list of mobile devices and their respective
operating systems. Developers have scrambled to find a Figure-1: Growth of Mobile Applications.
suitable development methodology to accommodate for
the fast-growing craze, and the Agile methodology has The case against incorporating agile development into
quickly become an industry-standard. mobile computing does not lie within the pros and good
practices but within the cons and loopholes that many
So why has Agility been adapted, and what exactly is consumers manipulate. When we combine the interactive
agile development? Agile software development is a nature of mobile applications, our situation becomes very
group of methods, which surround the idea of flexible, slippery. Because of heavy customer involvement
iterative, and incremental development with the intent to throughout the development process, there are often
develop high quality applications. Agile development frequent changes to business needs, especially when
places great emphasis on scope creep and change control increment results showcase unintended results. Those
disappointments are quickly uncovered when customers
review a demo of their increments. The idea of short
cycles to complete use cases leads some to rush through
development. This in turn leads to low quality software,
which will require multiple sprints to complete. In
addition, business investors sometimes mistake the
iterative and incremental process of Agility as an
opportunity to alter and negotiate new business needs. In
this study, we will explore the potential pitfalls of
incorporating agility into the development of mobile
application.
Culture
multiple time zones and continents. What makes project
management easier across continents is the designation of
project leaders for Quality Assurance (QA) and
development per site. Having a project manager per site
also decreases the lack of information from superiors but
it also likely increases the costs dramatically. However, it
is important to point out that it is still possible for a lack
of information whenever you have project managers and
development leads at other sites.
Globalization
Communication

Figure-3: Social Issues.

The ability of an organization to adapt to unexpected

changes is critical to achieving and maintaining a
competitive advantage [15]. Outsourcing does not
particularly benefit from the Agile process because of
Figure-2: Sale and Revenue from Mobile Applications. difficulties in relationship building and coordination
through communication. Poor work dynamics in the
II. AGILITY IN MOBILE COMPUTING workplace often lead to lower levels of trust and a lack of
The problem with Agile development is the lack of team effort [10]. Lower levels of trust often mean that US
quality results and experience in mobile application developers are constantly double-checking source code
development despite being driven by a software from other sites, and offshore sites are constantly
development methodology. There are two main talking questioning or clarifying why something is being done a
points related to the effects of agility in mobile computing: certain way. Furthermore, offsite testers may attempt to
social issues and the development environment factors. test a product that caters to their own culture even when
they are a very small percentage of the mobile
A. SOCIAL ISSUES applications users. The primary author has experienced
Social issues, integral part of all teams, often dictate this constant push and pull in the workplace, and it seems
the flow of a development environment through to be unanimous in all of the companies.
instruction, production, and efficiency. The immersion of
technology into our daily lives has broken many culture In the US, onsite location is normally seen as the main
and communication barriers among civilization, and many branch and the offsite location is normally known as the
companies are globalizing for maximum profits. Figure-3 supplementary branch. What happens in most cases is that
shows how these factors easily blend together on a social US developers are responsible for the bulk of software
front. Here, we address the impact of social issues on development, whereas the offsite employees perform the
mobile development. testing on development. This opens a multitude of issues.
For one, the process of playing catch-up and getting
A.1 Globalization familiar with different parts of the system can be quite
The integration of outsourcing into Agile is another time consuming and labour intensive for both onsite and
hazard that seems to affect mostly all corporate IT offsite locations. The training period ends up attributing
departments. The primary author has interned at a few to even more meetings, which further takes away from
corporate companies, and each company had development development time. In addition, onsite and offsite
teams in India. Those teams were also responsible for employees typically use a mobile device differently.
daily stand-ups and sprint tracking. There is a great effort When we also consider the distance to servers and
on management to coordinate development teams across download speeds, it is easy to see how testing the mobile
application can become very tedious and lacklustre in sites celebrated holidays that the other teams at different
performance. sites did not and this could affect the sprint in either
planning or development. Though these days can be
There have also been constant complaints of more substituted, it is a clear indication of different values and
thorough code reviews for source code developed by the customs. Cultural members always socially construct the
teams in offsite locations. If this were a common meanings and purposes of their activities. Enculturation
occurrence, one would ask why companies continue to thus refers to gaining an implicit sense of those meanings
endure this painstaking task. Despite the high demand of and purposes [11]. Therefore it is very important to have a
software developers in the US, there is still a large unified approach to development and the understanding of
shortage of supply within the US. On the other hand, there how business operations should take place within a certain
is an ample supply within countries like India and China. environment. When you compare developers from
Whereas in earlier years, outsourcing was practiced for different countries such as China, India, and the US, you
economical means, it is now practiced because of the must also take into account their educational systems,
necessity of resources. It is very important to point out the uniquely similar personality traits, and development
poor work dynamics because it is not true that onsite experience and preferences. One size does not fit all
teams are more talented than offsite teams. However, that when you consider the types of culture, and organizational
seems to be a general consensus considering that most of or enterprise agility in this framework represents the
the widely successful apps are developed within the US. developmental culture [11]. Therefore, if the development
We believe that an improvement of work dynamics culture is not stable, the development process will surely
improves the general perception and the effectiveness of operate along the same lines.
quality development, and that will ultimately contribute to
all sites in a very positive way. A.3 Communication
In efforts to create a more unified information source,
A.2 Culture companies have started to create company Wikis and
Culture is also another underestimated factor in the SharePoint sites set aside solely for its IT departments.
corporate world. In this study we focus on two subcultures: This helped to ensure consistency and structure
organizational culture and personal culture. throughout communication as well as the mobile
Organizational culture is especially important because it application development process. Software changes, story
lays the foundation of unspoken rules and business laws specifications, and other guidelines could be added for
within an organization. Though some unspoken rules are quick reference. In Agile, development is done in
not strictly enforced, it does play into the work dynamics increments and those short increments are quickly out-
of a group. For example, Company A may expect all dated. This is very useful because the information can be
software developer employees to eat lunch together on easily changed, and information becomes irrelevant rather
Fridays; however, this could be problematic to a software quickly. In addition to that, operating systems, standards,
developer whom works remotely on Fridays. This affects and features change daily in the mobile world.
team and relationship building within a mobile Incidentally, software developers are often spending a lot
development team. Fitting into the work culture is of their time updating Wikis, Sharepoint sites, and other
increasing becoming just as important as the mobile information mediums in order to keep some sense of
software developers skills. consistency for the development team.. When you
compound this with the Agile structure of daily stand-up
Most job postings have began to list details about meetings, sprint planning, and other meetings, the
regular company events and desired personality traits of development is left with significantly less time for
potential employees. These factors often dilute the options actually completing development. So, what does that
of available software developers seeking employment. mean for those whom create the services and products for
Some developers also feel the pressure to fit into a consumers in a We Want It Now era? This means that
particular work culture, which could ultimately negatively there should be very little time between asking and
affect their overall work performance. By definition, Agile receiving. This also means that consumer complaints and
is a culture and approach to software development. With feedback should be quickly addressed and fixed without
increasing flexibility for the customer, more restrictions much delay or contemplation. Agile greatly impedes this.
and difficulties are often placed on the mobile application
developers. The combination of the Agile methodology B. DEVELOPMENT FACTORS
and the company dynamics often overcomplicates the Most of us understand how a finished product or
simplicity of a software developers primary function in current service must be maintained by the producer in
an organization. order to keep the consumer happy. However, let us also
apply this same logic to a stakeholder and a software
In discussing personal culture, one must also consider developer during the beginning stages of planning new
language, subcultures, and religious backgrounds. Some software. Now, lets picture that the stakeholder is the
consumer, and the software developer is the producer. Is it
smart to handle this consumer the same as we would with
a finished product? Is our decision dependent on the idea
of how a service should be planned and developed, or is it
based on the idea of ensuring that we also satisfy the
consumer within the best of our means? Figure-4 displays
the factors that must be considered when understanding
how to create business agreements if Agility is a
requirement.
Enterprise
vs.
attempting to brand themselves and build more personal
Consumer
Project
Native
vs.
mobile [15]. Consumer applications use a lot of
Management
Web
Development
all functionality for the those exposed features in the
Figure-4: Development Environment.
B.1 Project Management
In the primary authors internships, she has discovered
that each company also used VersionOne, which is a type
of project management software catering to Agile
software development. We believe that VersionOne is an
excellent software utility; however, it should be noted that
it is also new software that employees must learn to use
properly for accurate use. It is unclear if there is a general
consensus as to how that learning curve is built into the
software developers schedule. She also notes that
software training is normally completed during the
software developers own desk time.
The reason we point this out is that each company
normally uses a daily, 6-hour capacity rule under the
Agile methodology. All of this information is tracked in
VersionOne and reviewed by product management during
sprint closing and retrospectives. These 6 hours are for
development, testing, and documentation tasks; it does not
include meetings or product training. This also means that
a two-week (or 10 day work week) sprint would actually
involve 1 day set aside for previous sprint closing and the
current sprint planning, and the remaining 9 days would
be available for actual development at 6-hours per day. A
developer would then enter 54 hours for availability in
their capacity for the sprint. If we consider the fact that
developers are actually in office for 80 hours during that
2-week period, is it economically feasible for the company
to afford the 26-hour net loss per mobile developer per
week in the name of Agile?
B.2 Enterprise vs. Consumer
Most mobile applications tend to be enterprise or
consumer applications. There is a huge difference between
these types of applications. Consumer applications are
geared toward the general public and do not have huge list
of documentation; this is because developers determine
which features are very valuable in the consumer market
and implement those features due to the response from
software releases. Great examples of mobile consumer
applications would be Facebook, Twitter, and LinkedIn.
All of these sites started as web interfaces and were
migrated to mobile because it has become a key device for
consumers. Most of these companies quickly took the
corporate approach to incorporating mobile apps by
relationships with their customers through its presence on
prototyping procedures to ensure that the look and feel of
the application flows well for the average consumer.
Under Agile, the design team will complete the
prototyping process before major development is began
and that leaves developers with the simple task of coding
interface. In this case, agile is a great choice because of
the less general development process.
On the other hand, mobile enterprise applications
target businesses and corporations and require very
specific user requirements. Most of these applications are
related to information security, monitoring, and constant
contact. Customer feedback is initiated throughout the
development process rather than post-release. These types
of applications are great under the Waterfall model
because of its thorough documentation and unchanging
requirements. Under Agile, there is a much longer
development process because of constant changes made
from customer feedback and many meetings despite the
specifics of the documentation. For an enterprise-scale
application, this could extend the development process to
several years before a final product is completed. In
addition, Agile can have devastating affects on the team
morale and focus. Some software developers often find
more excitement in working on various projects in shorter
time intervals. The Agile approach leads architects to plan
for the quickest solution rather than a long-term, more
sustainable approach. Though code may be developed
quicker, it is also more prone to security issues and
inconsistent results and will hence require more changes
over the life of the product as well as development.
B.3 Native vs. Web
When you consider all of these factors, companies
must consider how much they are willing to invest in
third-party software as well as the learning curve for new
mobile application developers in a native platform
environment. Even though most companies expect for
developers to hit the ground running, they must be very
realistic about skill level, the number of available software
developers, and the overall budget of a mobile application.
In addition, with third party software, features are less
likely to change per release of the native OS, and this can III. MATHEMATICAL MODEL
often quickly outdate a mobile application. Table-1 The main factors to consider in the mathematical
outlines the development and social issues which occur model are the social and development issues. Both of
during the use of Agility in mobile computing. these impact the timeline and budget of a mobile
application development project. My formula uses money
Personal culture impact on and time to determine if Agile is worthwhile pursuit for
development project management and developers. If the total result is
Social Issues
Poor work dynamics in the workplace negative, then Agile should be avoided; however, if the
Consistent and unified information
final result is positive, then Agile should not have any
Very restrictive project management
detrimental effects on the project and the development
Lack of fixed user requirements
Development phase.
Lack of available software developers
Factors
Choosing the wrong development
platform In Figure-5 below, t denotes a sprint in a particular
project. N denotes the total number of projected sprints
Table-1: Social Issues and Development Factors. required for successful completion. X denotes the number
Another important concept is to understand the of available software developers while c represents the
importance of the chosen platform when considering current developers time, which is being accessed. P
Agile. During the rush to create mobile applications, most represents the total time that the developer can contribute
companies also have begun to realize the huge shortage of to the project within the current sprint. represents the
mobile application developers well versed in object- total budget for the software development project.
oriented programming languages such as C++, Java, and
Objective-C. For native mobile applications, iOS uses
Objective-C, Android uses Java, and Windows Phone uses
C++. Native platform development allows for better
performance, seamless user interfaces, and it is great for
branding. However, with more options and being free of a Figure-5: Determining Agility feasibility.
standard cross-platform API, it means that developers are
Though this formula seems simple and straightforward,
option expected to do more but in the same amount of
it is often ignored for the sake of creating a highly
time. For very experienced mobile application developers,
customizable, customer friendly type application. Even
this may not be a huge problem. The key thing to
though that it is the ultimate goal of delivery satisfaction,
remember is that there is a very large shortage of
it ignores the necessity for standards and documentation to
experienced developers, and there is also much more
guide project managers and software developers.
demand than available supply for mobile application
developers overall. IV. DISCUSSION
Since we cannot operate without some type of
However, there are certainly several web developers
structure, we must also consider if there is a more suitable
available to increase their skill sets in order to remain
methodology for software development. Surprising,
valuable in this sifting market. Since the third party
Agility is not a new approach to software development;
software normally requires JavaScript or HTML, it
its just that newer programming generations are being
doesnt does require much of a learning curve for web
rapidly exposed to the methodology. Another thing to
developers delving into the software development world.
consider is the difference in the business world. Simply
This has sparked a large market for web-based, cross-
put, most companies have learned their lessons from the
platform software kits. The names PhoneGap and
old way of doing things and are desperately seeking for a
Titanium Studio are very familiar to companies whom
better way of doing things. Early software projects were
want a quick and dirty mobile application to get their
late, over budget, and had low quality. [8]. So naturally,
mobile branding kicking. Though there is a higher cost of
companies have diverted their focus to on-time, under
the software and tools for development through third party
budget, and higher quality software. In order for them to
software, it also offers a quicker turnover rate for
determine if a product meets all of the above, then heavy
development for most companies. Mobile applications,
involvement is necessary throughout the entire planning
developed under a web-based platform, work great with
and development of their software.
the Agile development process, mainly because of the
limited amount of choices. With cross-platform software, A. Waterfall vs Agile
you dont have as many options and the mobile There are two other priorities that can wreak havoc for
applications tend to be very simple. From a developer a mobile development team: the second principle on
standpoint, it could be viewed as a relief because it welcome changing and the agile manifesto statement on
reduces the likelihood of changing requirements under Responding to change over following a plan. Business
Agile development.
investors sometimes mistake the iterative and incremental
process of Agile development as an opportunity to alter
and negotiate new business needs. This is a problem if the
new business need is drastically different from the original
plan. Before Agile development, there was primarily the
Waterfall Model. In the Waterfall model, there were
well-defined phases [3]. Since the Waterfall Model was
a sequential, the requirements were expected to be clear
before going to the next phase of design [2]. Under the
Waterfall method, most consumers felt trapped and were
forced to commit to the documentation before
development. Under Agile, the consumer now has the
option to change requirements and documentation, even if
it occurred in the last stages. In the Waterfall model, the
rigid structure ensured that the quality of the project
was maintained [2]. Though Agile claims, working
software is the primary measure of progress, it does not
address the need for high-quality software.
B. Globalization
Unfortunately, more problems arise when more people
are involved. Multiple working styles, work schedules,
and opinions weigh into this fact; the complexity of
satisfying every single person becomes a constant struggle.
In mobile application development, one person may swipe
the screen for a specific function, whereas another
individual may quickly tap. Incorporating more
functionalities and options dependent upon user touch
quickly adds to the mountain of problems already
persistent in any software development project.
C. Continuously Changing Requirements
Another significant argument is that the lack of
commitment during planning will ultimately disrupt the
development process through numerous changes.
Overhead and continuous changes will always be
prominent problems when using Agile methodology in
mobile computing. This is definitely a problem when
stakeholders favour flexible and ever-changing
requirements, whereas the developer requires a more
structured and detailed approach. When developers are
required to constantly tweak or re-design a use case
requirement, they may never proceed to the next
requirement. When stakeholders fail to see progress, the
developer may appear to be wasting time versus actually
spending unnecessary time on changed requirements that
should have finalized beforehand. Using Figure-5s
formula, one can calculate the project failure caused by
the addition of sprints caused by continuous changes.
D. Lack of Documentation
Agility also requires short development cycles; this is
mandated through the priority of working software over
comprehensive documentation. Unfortunately, this also
causes most to rush through development by producing
modules of the system rather than focusing on the system
as a whole according to the missing comprehensive
documentation. Ultimately, this also increases the
likelihood of low quality software. If this is the case, then
why is there a need to rush in adopting the Agile
methodology into software development? The answer to
that question can be further explored by reviewing the
Twelve Principles of Agile Software shown in Table-2 [1].
1. Our highest priority is to satisfy the consumer through
early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in
development. Agile processes harness change for the
consumer's competitive advantage.
3. Deliver working software frequently, from a couple of
weeks to a couple of months, with a preference to the
shorter timescale.
4. Business people and
5. The most efficient and effective method of developers
must work together daily throughout the project.
6. Build projects around motivated individuals. Give them
the environment and support they need, and trust them to
get the job done.
7. conveying information to and within a development team
is face-to-face conversation.
8. Working software is the primary measure of progress.
9. Agile processes promote sustainable development. The
sponsors, developers, and users should be able to
maintain a constant pace indefinitely.
10. Continuous attention to technical excellence and good
design enhances agility.
11. Simplicity--the art of maximizing the amount of work not
done--is essential.
12. The best architectures, requirements, and designs emerge
from self-organizing teams.
13. At regular intervals, the team reflects on how to become
more effective, then tunes and adjusts its behaviour
accordingly.
Table-2: Agile Principles.
E. Prototyping vs. Development
Understanding the difference between prototyping
and development is also essential for determining if Agile
should be used for mobile application development. Since
prototyping is technically apart of the planning process,
then it should definitely be done beforehand to
appropriately distribute the workload for developers and
allow focus on actual requirements. Some customers have
taken it upon themselves to focus more on the look and
feel rather than the core functionality. Though both are
very important, one must understand the actual process of
prototyping so that it does not delay actual software
development. During most mobile application
development projects, a developer will attempt to
demonstrate a core function of the application through
incremental development. Most customers respond to
these changes as rapid throwaway prototyping results
because of the relatively short two to three week
increment cycles. Prototypes are instruments [9], and
 they are not products or components of the software [3] B. Madhu, M. Jigalur, and V. Lokesha, A Study on
product.
F. General Consensus
Without sounding negative, the authors think of Agile [4] P. Maher and J. Kourik, Agile Software Development
software development as being the parent that desperately
seeks to win over their children by not teaching them
about delayed gratification. The explanation may be
somewhat exaggerated, but many software developers are
now being forced to accept these realities. The main [5] G. Galal-Edeen and M. Seyam, Traditional versus
argument against Agile methods is the asserted lacks of
scientific validation for associated activities and practices,
as well as the difficulty of integrating plan-based practices [6] A. Spataur. Agile Development Methods for Mobile
with Agile ones [6]. Table-3 outlines the discussed pitfalls
of using Agility in mobile application development.
Agile Pitfalls:
Lack of fixed user requirements lead to constant
changes and tweaks during development.
Confusion between mobile app prototyping and
development.
Globalization introduces many culture and
communication problems during development.
Project management tends to micromanage
development time
Table-3: Issues with Agility in Mobile Computing.
V. CONCLUSION
Despite the numerous downloads and high profits
made in the mobile industry, we must also ask ourselves if
Agile-driven software is better software. We must also ask
if the standard of quality software has also changed with
the change in generation. Sturdy code functionality is
being replaced every day by user-friendly, pretty
functionality. The usability factor seems to be the only
extreme positive in favour of incorporating Agility into
mobile application software development. As we have
discussed in our findings, using Agility in mobile
computing is a very slippery slope. The fast-paced
development is definitely desired for the we want it now
era, but the pitfalls greatly outweigh the long-term effects
on the development process.
REFERENCES
[1] T. Way, S. Chandrasekhar, and A. Murthy. The Agile
Research Penultimatum. Software Engineering
Research and Practice, CSREA Press, (2009), page
530-536.
[2] S. Balaji and M. Murugaiyan, Waterfall Vs V-Model
Vs Agile: A Comparative Study. International Journal
of Information Technology and Business Management,
June 2012, Volume 2, Number 1, page 26-30
Agile Software Testing: Emergence and techniques.
African Journal of Mathematics and Computer Science
Research. Volume 3 Number 11, page 288 - 289
in Evolving Business Environments: Integrating
Modern Techniques into Computer Science Curricula.
ASBBS Annual Conference: Las Vegas. February
2011, Volume 18 Number 1, page 248-254
Agile: The Tragile Framework for Information
Systems Development.
Applications. (2010).
[7] J. Dehlinger and J. Dixon, Mobile Application
Software Engineering: Challenges and Research
Directions. (2011).
[8] R. Shriver and D. Birckhead, Delivery Business Value
with Lean and Agile. Dominion Digital.
[9] B. Boehm, T. Gray, and T. Seewaldt, T. Prototyping vs.
Specifying: A Multi-Project Experiment. IEEE
Transactions on Software Engineering Volume 10
Issue 3, May 1984, page 290-302
[10] S. Chinbat and A. Agahi, Lessons Learned in Virtual
Teams from Global Software Development. (2010).
[11] J. Iivari and N. Iivari, The relationship between
organizational culture and the deployment of agile
methods. In Special Section on Best Papers from
XP2010, Information and Software Technology.
Volume 53 Issue 5, page 509-520
[12] D. Batra. Modified Agile Practices for Outsourced
Software Projects. Communications of the ACM.
Sep2009, Volume 52 Issue 9, page 143-148.
[13] A. Ganguly, R. Nilchiani, and J. Farr, Evaluating
agility in corporate enterprises. International Journal of
Production Economics. Volume 118 Issue 2, page 410-
423.
[14] D. Fernandez and J. Fernandez, Agile Project
Management Agilism versus Traditional Approaches.
Journal of Computer Information Systems.
Winter2008/2009, Volume 49 Issue 2, page 10-17.
[15] V. Jyothi and R. Nageswara Rao, Effective
Implementation of Agile Practices Incoordination
with Lean Kanban. International Journal on Computer
Science & Engineering. Jan2012, Volume 4 Issue 1,
page 87-91.
[16] C. Foresman. Apple responsible for 99.4$ of mobile
app sales in 2009.
http://arstechnica.com/apple/2010/01/apple-
responsible-for-994-of-mobile-app-sales-in-2009/
[17] AB Mobile Apps. Developing a Mobile Application
for Small Business.
http://www.abmobileapps.com/developing-a-custom-
mobile-application-for-a-small-business/