DOCSLIB.ORG

Why and How to Use Phonelab

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Why and How to Use Phonelab [MOBILE PLATFORMS] Jinghao Shi, Edwin Santos, and Geoffrey Challen University at Buffalo Editors: Sharad Agarwal and Marco Gruteser WHY AND HOW TO USE PHONELAB While smartphone app marketplaces have enabled large-scale app-level experimentation, medium-scale experimentation with the platform code implementing the app interface and providing core device services remains difficult for academic researchers. But this is where many of the ideas currently being explored by the mobile systems community must be evaluated—including new networking protocols, security and privacy mechanisms, storage abstractions, and energy management strategies. To enable these experiments, we built and are operating PhoneLab, a 175-smartphone testbed where real users run experimental Android platform builds on their primary devices. We are eager to make PhoneLab useful to the mobile systems community. To aid in this effort, this article discusses why PhoneLab might be useful for your research and provides an overview of how to use the testbed, including examples drawn from our group’s current projects. 32 GetMobile October 2015 | Volume 19, Issue 4 [MOBILE PLATFORMS] he world’s two billion mobile played a significant role in democratizing enormous number of users, like the Carat2 smartphones together constitute the mobile app development by allowing a single personalized energy management app, which T largest, most powerful, and most developer to easily reach a global audience. was installed more than 750K times. We widely distributed system ever built. In In the same way, these marketplaces are expect app marketplaces to continue to play many ways, the incredible success of the also playing an increasingly important a vital role in allowing the mobile systems smartphone is built on decades of research role in enabling large-scale mobile systems community to evaluate ideas at scale. by the mobile systems community. But new research. Researchers can now make But what about the smartphone platform challenges and opportunities alike await experimental apps available to billions itself? Platform codebases are the millions next-generation mobile apps and systems of users, and rely on the fact that even a of lines of code that are responsible for that attempt to harness this increasingly tiny fraction of citizen scientists willing to performing crucial tasks such as determining powerful and pervasive network, and participate in their project can amount to a the device’s location, choosing which researchers must continue to find ways representative, statistically significant and available network to use, and managing to make these ubiquitous devices even globally distributed sample of thousands limited resources such as energy – tasks more effective. or even tens of thousands of users. As an of obvious interest to the mobile systems An important part of the smartphone example, the Netalyzr tool1 distributed by research community. Smartphone platforms success story has been the emergence of ICSI has been downloaded 24,000 times cannot be altered via apps distributed by app mobile app marketplaces, such as the Google by users in 120 countries. And if the app marketplaces, and they also limit the access Play Store. These distribution channels have provides a tangible benefit it may attract an of these apps to useful information and device capabilities – sometimes for security or privacy reasons, but at other times simply because the information is considered too difficult or not useful enough to expose. Microsoft’s and Apple’s platform codebases are proprietary, making experimentation impossible without insider support. But while the Android Open Source Project (AOSP) makes it possible to create fully functional custom Android platform images for select devices, many roadblocks still await researchers attempting to deploy modified platform images at even modest scale. Experimental participants must be recruited and, if their behavior is to be representative, convinced to swap their primary smartphone for (and port their number to) a new device. Data collection tools must be built and tested, and the platform changes themselves must be developed and deployed. These experimental barriers are making it difficult for today’s academic mobile systems research community to have a real impact on the most important parts of the most successful mobile systems platform: the smartphone. To simplify smartphone platform experi- mentation we are operating PhoneLab, a 1 http://netalyzr.icsi.berkeley.edu/ Photo, istockphoto.com Photo, 2 http://carat.cs.berkeley.edu/ Volume 19, Issue 4 33 [MOBILE PLATFORMS] smartphone platform testbed (https://www. demographics. We do know that we have and location homogeneity, PhoneLab is a phone-lab.org). PhoneLab is both a group participants in many different departments relatively poor environment to investigate of people and an ongoing community effort on campus, providing a reasonable level of this challenge. to maintain a well-instrumented version on-campus spatial coverage which can be of the AOSP useful for research purposes. important to certain studies. EXPERIMENTAL PROCESS PhoneLab consists of 175 participants that To simplify testbed administration, we To use PhoneLab, you first download and run custom Android platform images on operate PhoneLab as a Sprint corporate- modify our fork of the AOSP. Next, you their primary smartphone. Our PhoneLab liable service plan. PhoneLab participants work with PhoneLab administrators and platform image is open to the mobile pay $45 per month for an all-you-can-eat developers to test your changes. After your systems community to instrument and Sprint service plan which includes unlimited changes are validated to be safe and effec- modify. We provide the participants, reliable voice, messaging and data. Technically tive, they are distributed to participants data collection tools, and increasingly well resources are pooled and capped over all and data collection begins. Finally, after instrumented AOSP platform sources. You participants, but in practice the caps are verifying that your experiment has been provide the exciting research questions and generous enough to never limit participant cleared for human subjects compliance, you new ideas that help us learn more about and consumption. Cooperation from Sprint will be provided the data that it generated. improve these ubiquitous mobile devices. allows us to create an attractive price point Here we review each step in the process in In this article our goal is to provide for our participants, while they offload all more detail. an overview of PhoneLab’s capabilities in payment processing and customer support the hope that you will find it helpful in to us. Participants purchase service directly Instrumenting or Modifying enabling your research studies. We start from PhoneLab in six-month installments, the PhoneLab Platform: with some basic information about the with invoice and payment processing done Experimenting on PhoneLab begins with testbed, describe the process of performing using Square. Sprint’s coverage in the Buffalo making changes to the Android platform. a PhoneLab experiment, and then use some area is fairly good, including 4G LTE mobile PhoneLab hosts a mirror of the AOSP examples drawn from our ongoing projects data coverage in many locations. allowing experimenters to use Google’s to provide tangible examples of what Currently all participants use the Google Android well-documented platform build PhoneLab can do. Nexus 5 smartphone running a custom An- process as well as their repo and Gerrit droid platform image based on the Android source control tools. Only the repoURL PARTICIPANTS, PLANS, PHONES Open Source Project (AOSP). Currently used during the process of downloading PhoneLab is a smartphone platform testbed our PhoneLab branch is based on AOSP the platform sources is different – the rest located at the University at Buffalo (UB). version 5.1 “Lollipop,” an upgrade from of the workflow is identical. 175 participants – primarily UB, students, version 4.4.4 that participants received in We divide PhoneLab experiments faculty, and staff – receive discounted Sprint mid-September 2015. In previous academic into two categories: instrumentation and service and a Google Nexus 5 smartphone years participants use the Samsung Nexus S modification. Instrumentation consists of to use as their primary device. In exchange, (2012-13), Samsung Galaxy Nexus (2013- additional logging that records but does not they run a modified Android platform 14), and Google Nexus 5 (2014-15). Com- alter how Android operates. Modifications image containing instrumentation and pared to these previous smartphones the modify Android itself, possibly by altering potentially novel changes and features. Nexus 5 seems far superior, and has helped existing services or adding new features. PhoneLab participants were originally address battery lifetime and network quality Of course, modification experiments will required to be UB affiliates. Recently complaints registered by first- and second- usually need to generate data to evaluate we have relaxed that policy, but almost year participants. their changes, and so will require instru- all participants are still UB students, We are aware that in some ways mentation as well. faculty and staff. We have not yet polled PhoneLab represents an unusually homo- Instrumentation changes are usually the demographics of our 2014-15 geneous environment for smartphone ex- fairly well-contained and unlikely to participants,
Load more

Recommended publications
  • Ten Steps to Smartphone Security
    Ten Steps to Smartphone Security Smartphones continue to grow in popularity and are now as powerful and functional as many computers. It is important to protect your smartphone just like you protect your computer as mobile cybersecurity threats are growing. These mobile security tips can help you reduce the risk of exposure to mobile security threats: 1. Set PINs and passwords. To prevent unauthorized access to your phone, set a password or Personal Identification Number (PIN) on your phone’s home screen as a first line of defense in case your phone is lost or stolen. When possible, use a different password for each of your important log-ins (email, banking, personal sites, etc.). You should configure your phone to automatically lock after five minutes or less when your phone is idle, as well as use the SIM password capability available on most smartphones. 2. Do not modify your smartphone’s security settings. Do not alter security settings for convenience. Tampering with your phone’s factory settings, jailbreaking, or rooting your phone undermines the built-in security features offered by your wireless service and smartphone, while making it more susceptible to an attack. 3. Backup and secure your data. You should backup all of the data stored on your phone – such as your contacts, documents, and photos. These files can be stored on your computer, on a removal storage card, or in the cloud. This will allow you to conveniently restore the information to your phone should it be lost, stolen, or otherwise erased. 4. Only install apps from trusted sources.
    [Show full text]
  • SMS “Virtual Collection Center” Smartphone
    Feed the Future Innovation Lab for Livestock Systems INNOVATION SUMMARY: SMS “VIRTUAL COLLECTION CENTER” SMARTPHONE APP The Virtual Collection Center (VCC) is an innovative short message service (SMS) mobile application (app) for improved goat marketing. Through the use of the VCC app, inventory updates flow from cooperative members to leaders, while cooperative leaders use the VCC app to share price information with members and fill orders from traders by inviting members to sales events. The VCC app improves the goat value chain by reducing transaction costs, which should strengthen cooperatives and benefit small livestock producers by increasing trade volumes. Lead Implementing Institution: University of Florida Category: Marketing & Distribution Applied in: Nepal The VCC app is implemented by Heifer International Nepal whose Innovation Type: Technology New/Adapted: New field personnel assist cooperative members in downloading the app while providing training and Created for: Mainly Women Nutrition Linkage: Dietary Quality monitoring in the initial stages. The app is designed to be intuitive, eliminating the need for intensive training. Within cooperatives, the In Nepal, goats are an essential source of income and nearly every rural Nepali household app is accessed by “VCC owns at least a few goats. To buy goats, traders often travel over large areas characterized managers”, who are members of cooperative self-help groups by rugged terrain and poor infrastructure, making multiple visits to individual households necessary to complete sales. The resulting high transaction costs can stifle the value chain. (subgroups within the Cooperatives can reduce transaction costs by allowing for bulk purchases of animals. But cooperatives), and cooperative cooperatives may struggle to coordinate sales by members spread out over large areas of leaders.
    [Show full text]
  • The Classic Blackberry – Supercharged
    COMING SOON! The classic BlackBerry – supercharged. BlackBerry® Curve™ 3G smartphone The new BlackBerry Curve 3G smartphone from AT&T is BlackBerry Curve 3G powerful yet affordable. This BlackBerry classic now gives smartphone you 3G speed and everything you expect from the popular The first 3G Curve BlackBerry Curve family, with a QWERTY keyboard, work and from AT&T. personal email, powerful personal management capabilities and much more. A superior connection. • Be at the forefront. With simultaneous voice and data when using the 3G or Wi-Fi network, you can check the facts on email or the web while talking on the phone with clients or colleagues. • Work with speed and confidence. The BlackBerry Curve 3G • Speed with flexibility. The BlackBerry Curve 3G smartphone has a powerful 624 MHz processor, 256 MB flash smartphone allows you to quickly download and upload memory/256 MB SDRAM and an included 2 GB microSD™ card content and surf the web faster on the nation’s fastest for storage, expandable up to 32 GB. broadband mobile network.* And with built-in Wi-Fi® • Focused applications. Keep up-to-date and informed of your (802.11 b/g/n), access the information and download the work and life – explore BlackBerry® App World™ and pre-loaded large files you need at Wi-Fi speeds. applications including LinkedIn™, My-Cast® Weather, Bloomberg® • Automatically unlimited. The new BlackBerry Curve 3G Mobile, AllSport GPS™, WHERE®, City ID®, Facebook®, MySpace™, smartphone automatically connects to AT&T Wi-Fi Hot Twitter™ and more. Spots in the U.S.** for unlimited usage on the AT&T Wi-Fi • Capture the moment.
    [Show full text]
  • Mobile Phone from Wikipedia, the Free Encyclopedia
    Mobile phone From Wikipedia, the free encyclopedia Siemens AX72. Galaxy Nexus, an example of a smartphone A mobile phone (also known as a wireless phone, cell phone, or cellular telephone[1]) is a very small portable radio telephone. The mobile phone can be used to communicate over long distances without wires. It works by communicating with a nearby base station (also called a "cell site") which connects it to the main phone network. As the mobile phone moves around, if the mobile phone gets too far away from the cell it is connected to, that cell sends a message to another cell to tell the new cell to take over the call. This is called a "hand off," and the call continues with the new cell the phone is connected to. The hand-off is done so well and carefully that the user will usually never even know that the call was transferred to another cell. As mobile phones became more popular, they began to cost less money, and more people could afford them. Monthly plans became available for rates as low as US$30 or US$40 a month. Cell phones have become so cheap to own that they have mostly replaced pay phones and phone booths except for urban areas with many people. Many mobile phones are "smartphones". As well as making voice calls, they can be used as computers. Contents [hide] 1 History 2 Technology 3 Shapes 4 How mobile phones work 5 Networks and payment 6 Smartphones 7 References History[change | change source] Mobile phones in the 1950s through 1970s were large and heavy, and most were built into cars.
    [Show full text]
  • A Comparative Analysis of Mobile Operating Systems Rina
    International Journal of Computer Sciences and Engineering Open Access Research Paper Vol.-6, Issue-12, Dec 2018 E-ISSN: 2347-2693 A Comparative Analysis of mobile Operating Systems Rina Dept of IT, GGDSD College, Chandigarh ,India *Corresponding Author: [email protected] Available online at: www.ijcseonline.org Accepted: 09/Dec/2018, Published: 31/Dec/2018 Abstract: The paper is based on the review of several research studies carried out on different mobile operating systems. A mobile operating system (or mobile OS) is an operating system for phones, tablets, smart watches, or other mobile devices which acts as an interface between users and mobiles. The use of mobile devices in our life is ever increasing. Nowadays everyone is using mobile phones from a lay man to businessmen to fulfill their basic requirements of life. We cannot even imagine our life without mobile phones. Therefore, it becomes very difficult for the mobile industries to provide best features and easy to use interface to its customer. Due to rapid advancement of the technology, the mobile industry is also continuously growing. The paper attempts to give a comparative study of operating systems used in mobile phones on the basis of their features, user interface and many more factors. Keywords: Mobile Operating system, iOS, Android, Smartphone, Windows. I. INTRUDUCTION concludes research work with future use of mobile technology. Mobile operating system is the interface between user and mobile phones to communicate and it provides many more II. HISTORY features which is essential to run mobile devices. It manages all the resources to be used in an efficient way and provides The term smart phone was first described by the company a user friendly interface to the users.
    [Show full text]
  • Practicalizing Delay-Tolerant Mobile Apps with Cedos
    Practicalizing Delay-Tolerant Mobile Apps with Cedos YoungGyoun Moon, Donghwi Kim, Younghwan Go, Yeongjin Kim, Yung Yi, Song Chong, and KyoungSoo Park Department of Electrical Engineering, KAIST Daejeon, Republic of Korea {ygmoon, dhkim, yhwan}@ndsl.kaist.edu, [email protected], {yiyung, songchong}@kaist.edu, [email protected] ABSTRACT 1. INTRODUCTION Delay-tolerant Wi-Fi offloading is known to improve overall mo- Wi-Fi has become the most popular secondary network interface bile network bandwidth at low delay and low cost. Yet, in reality, for high-speed mobile Internet access on mobile devices. Many we rarely find mobile apps that fully support opportunistic Wi-Fi mobile apps support the “Wi-Fi only” mode that allows the users to access. This is mainly because it is still challenging to develop shun expensive cellular communication while enjoying high band- delay-tolerant mobile apps due to the complexity of handling net- width and low delay. In addition, cellular ISPs are actively de- work disruptions and delays. ploying Wi-Fi access points (APs) to further increase the mobile In this work, we present Cedos, a practical delay-tolerant mobile Internet access coverage [1, 2, 3]. network access architecture in which one can easily build a mo- However, current Wi-Fi usage is often statically bound to the lo- bile app. Cedos consists of three components. First, it provides a cation of mobile devices. While this “on-the-spot” Wi-Fi offloading familiar socket API whose semantics conforms to TCP while the is still effective, recent studies suggest that one can further extend underlying protocol, D2TP, transparently handles network disrup- the benefit of Wi-Fi access if we allow delay tolerance between net- tions and delays in mobility.
    [Show full text]
  • Maxphone—Multi-Access Extension for Smartphones Fact Sheet
    Completed DHS Science and Technology Directorate MaXphone—Multi-Access Extension for Smartphones Providing devices that embrace Land Mobile P25, cellular/Public Switched Telephone Network voice, Radio (LMR) and broadband cellular networks and Voice-over-IP. It also allows for enhanced security by The First Responder Network Authority (FirstNet) is providing end-to-end P25 encryption across LMR and charged with creating a nationwide public safety broadband broadband networks. network that provides the public safety community with a Enabling customizable, affordable applications boost in network capacity and capability. Still, commercial MaXphone leverages rapid development in commercial cellular broadband networks (e.g., 4G LTE and 3G) will broadband networks and smartphone capability. Open likely remain the dominant option to support first responder application development environments (e.g., Android) broadband applications for the immediate future. enable novel, innovative, customizable and affordable first Broadband networks do not provide first responders with responder applications. An open source, fully functioning mission critical voice capabilities (i.e., radio-to-radio or P25 software package will be available on the Android one-to-many communications) that are available on LMR environment. MaxJacket will be based on COTS networks. However, application and service development in components and contain the necessary functions for the P25 the LMR domain stand in stark contrast to the explosive solution. growth in the commercial broadband sector. Therefore, a reasonable, cost effective approach to creating more capable first responder devices embraces existing LMR networks Legacy P25 handset and commercial broadband cellular networks by using open P25 platforms to encourage application development. IP25 P25 Network Gateway Access The Department of Homeland Security Science and Technology Directorate and U.S.
    [Show full text]
  • Taxonomy of Cross-Platform Mobile Applications Development Approaches
    Ain Shams Engineering Journal (2015) xxx, xxx–xxx Ain Shams University Ain Shams Engineering Journal www.elsevier.com/locate/asej www.sciencedirect.com ELECTRICAL ENGINEERING Taxonomy of Cross-Platform Mobile Applications Development Approaches Wafaa S. El-Kassas *, Bassem A. Abdullah, Ahmed H. Yousef, Ayman M. Wahba Department of Computer and Systems Engineering, Faculty of Engineering, Ain Shams University, Egypt Received 13 September 2014; revised 30 May 2015; accepted 3 August 2015 KEYWORDS Abstract The developers use the cross-platform mobile development solutions to develop the Cross-platform mobile mobile application once and run it on many platforms. Many of these cross-platform solutions development; are still under research and development. Also, these solutions are based on different approaches Interpretation approach; such as Cross-Compilation approach, Virtual Machine approach, and Web-Based approach. There Cloud computing; are many survey papers about the cross-platform mobile development solutions but they do not Compilation approach; include the most recent approaches, including Component-Based approach, Cloud-Based Component-Based approach, and Merged approach. The main aim of this paper is helping the researchers to know approach; the most recent approaches and the open research issues. This paper surveys the existing cross- Model-Driven Engineering platform mobile development approaches and attempts to provide a global view: it thoroughly introduces a comprehensive categorization to the cross-platform approaches, defines the pros and cons of each approach, explains sample solutions per approach, compares the cross-platform mobile development solutions, and ends with the open research areas. Ó 2015 Faculty of Engineering, Ain Shams University. Production and hosting by Elsevier B.V.
    [Show full text]
  • Nexus S 4G: First Pure Google 4G Device with Android 2.3 in the US 22 March 2011
    Nexus S 4G: First Pure Google 4G Device with Android 2.3 in the US 22 March 2011 outdoors, so videos, pictures and games look their best and the sun won't wash them out. Sprint Nexus S 4G customers will be among the first to receive Android software upgrades and new Google mobile apps. In many cases, the device will get the updates and new apps as soon as they are available. Nexus S 4G features a 5 megapixel rear-facing camera and camcorder and front-facing VGA camera. In addition, Nexus S 4G features a gyroscope sensor to provide a smooth, fluid gaming experience when the user tilts the device up or down or pans the phone to the left or right. Sprint extends its 4G device innovation with the upcoming availability of the 20th 4G device and Additional key features include: fourth 4G phone, Nexus S 4G from Google. Coming to Sprint this spring, it will also be able to • 3G/4G Mobile Hotspot capability, take advantage of the controls and services supporting up to six Wi-Fi enabled devices enabled by Google Voice integration built into the simultaneously Sprint Network. • Android Market for access to more than 150,000 applications, widgets and games available Manufactured by Samsung, Nexus S 4G comes for download to customize the experience packed with a pure Google experience using • Google mobile services such as Google Android 2.3, Gingerbread, the fastest version of Search, Gmail, Google Maps with Navigation, Android available for smartphones. It is powered syncing with Google Calendar, Voice Actions and by a 1GHz Samsung application processor that YouTube produces rich 3D-like graphics, faster upload and • Corporate email (Microsoft Exchange download times and supports HD-like multimedia ActiveSync), personal (POP & IMAP) email and content along with a dedicated Graphics instant messaging Processing Unit (GPU) to make playing mobile • Near Field Communication (NFC) games, browsing the Web and watching videos a technology, which allows the device to read fast, fluid and smooth experience.
    [Show full text]
  • Critical Capabilities for Successful Mobile App Development
    7 Critical Capabilities Your Mobile App Development and Deployment Platform Must Include Speed Mobile App Development and Ensure Wide User Adoption Executive Summary In today's mobile business environment companies are scrambling to quickly mobilize hundreds of B2B and B2E business processes or legacy applications. There are three main approaches developers can use to build mobile business apps: - Responsive web apps - Native app development - "Native quality" hybrid apps This whitepaper explains important differences between these three approaches, outlines 7 mobile capabilities that real-world business apps require today, and identifies the most productive development approach for getting these mobile business apps to market FAST. 1 | P a g e High Demand for Mobile Apps For competitive and productivity reasons, businesses and organizations are embracing mobile more than ever. Gartner forecasts enterprise application software spending to double from $300B in 2013 to over $575B by the end of 2018.1 Yet, Gartner also predicts demand for enterprise mobile apps will outstrip available development capacity by five to one.2 Forrester warns: “The CIO who fails in mobile will lose his job.”3 As a result, companies are trying to find new ways to enable their employees to develop business apps. Everyone from young IT or business workers with basic HTML5 skills, to IT developers with limited mobile experience and business analysts are exploring how to build apps to get routine things mobilized faster. Rising End-User Expectations Complicating the problem is the rising expectations of an increasingly mobile workforce. Employees are adopting mobile devices exponentially and demanding more business apps to do their work.
    [Show full text]
  • Rapid Growth in Rugged Phones September 2017
    RAPID GROWTH IN RUGGED PHONES SEPTEMBER 2017 Rapid Growth in Rugged Phones How the market for robust mobile devices is going from strength to strength August 2017, Bullitt Group Research 1. Market dynamics Recent shipment volume estimates for the rugged smartphone market, by independent industry analyst firm CCS Insight, show that 17.7 Growth in the global smartphone market has million rugged smartphones shipped in 2016, slowed significantly in recent years, and is globally. This is forecast to grow to 22.2 million forecast at 6.8% year-on-year for 2017, taking units in 2017, representing a year-on-year shipments for the year to 1.6 billion units.1 increase of 25%. Continued year-on-year Within this vast global market, numerous smaller increases are forecast at a compound annual niche segments exist, servicing the specific growth rate (CAGR) of 18.9% (2016-2021), with needs of their target customer groups with the market set to reach 54.5 million units by differentiated products. 2021.2 Smartphone market year-on-year growth rates The market comprises devices clearly positioned 41.4% as ‘rugged’, and incorporates two sub- categories: 29.6% Consumer rugged smartphones: these devices 12.2% 6.8% are consumer-oriented and retain key 3.3% characteristics of a conventional smartphone. But, they usually carry an ingress protection (IP) 2013 2014 2015 2016 2017(f) rating of 68, and are drop tested onto a hard Source: Strategy Analytics surface from a minimum of 1.2 metres (4ft) – usually as part of support for the MIL-STD-810G One such niche – the rugged smartphone standard.
    [Show full text]
  • Factors Influencing Quality of Mobile Apps: Role of Mobile App Development Life Cycle
    International Journal of Software Engineering & Applications (IJSEA), Vol.5, No.5, September 2014 FACTORS INFLUENCING QUALITY OF MOBILE APPS : R OLE OF MOBILE APP DEVELOPMENT LIFE CYCLE Venkata N Inukollu 1, Divya D Keshamoni 2 , Taeghyun Kang 3 and Manikanta Inukollu 4 1Department of Computer Science Engineering, Texas Tech University, USA 2 Rawls College of Business, Texas Tech University, USA 3 Department of Computer Science Engineering, Wake forest university, USA 4Department of Computer Science, Bhaskar Engineering College, India ABSTRACT In this paper, The mobile application field has been receiving astronomical attention from the past few years due to the growing number of mobile app downloads and withal due to the revenues being engendered .With the surge in the number of apps, the number of lamentable apps/failing apps has withal been growing.Interesting mobile app statistics are included in this paper which might avail the developers understand the concerns and merits of mobile apps.The authors have made an effort to integrate all the crucial factors that cause apps to fail which include negligence by the developers, technical issues, inadequate marketing efforts, and high prospects of the users/consumers.The paper provides suggestions to eschew failure of apps. As per the various surveys, the number of lamentable/failing apps is growing enormously, primarily because mobile app developers are not adopting a standard development life cycle for the development of apps. In this paper, we have developed a mobile application with the aid of traditional software development life cycle phases (Requirements, Design, Develop, Test, and, Maintenance) and we have used UML, M-UML, and mobile application development technologies.
    [Show full text]