Adapting Agile Practices to Mobile Apps Development

Author(s):  
Alberto Heredia ◽  
Javier Garcia-Guzman ◽  
Roberto Esteban-Santiago ◽  
Antonio de Amescua

Mobile app markets have experienced remarkable growth during the last year. The increasing number of apps available on the market and the revenue that developers and companies obtain is significant enough to seriously consider the way apps are developed. The ever-changing environment in which apps are developed makes agile methodology convenient to follow. Although agile methodologies allow the development team to quickly adjust the requisites to the new customer’s needs, there is a lack of research on how they can be explicitly adapted to develop mobile apps. There are many Websites that explain how to code a mobile app, but there is not enough information about other stages in the development process. Adapting an agile methodology for mobile apps would provide development teams with a clear guide to successfully develop an app without missing any step in the development process. This chapter proposes an agile mobile app development process, including processes and activities to be followed as well as the roles involved in these activities. Marketing issues are also considered in the proposed development process as they are necessary to publicize the mobile app. This process has been applied for over two years in the development of the institutional apps at Carlos III University of Madrid.

2021 ◽  
Author(s):  
Nicole E Werner ◽  
Janetta C Brown ◽  
Priya Loganathar ◽  
Richard J Holden

BACKGROUND The over 11 million care partners in the US who provide care to people living with Alzheimer’s disease and related dementias (ADRD) cite persistent and pervasive unmet needs related to all aspects of their caregiving role. The proliferation of mobile applications (apps) for care partners has potential to meet the care partners’ needs, but the quality of apps is unknown. OBJECTIVE The present study aimed to 1) evaluate the quality of publicly available apps for care partners of people living with ADRD and 2) identify design features of low- and high-quality apps to guide future research and app development. METHODS We searched the US Apple and Google Play app stores with the criteria that the app needed to be 1) available in US Google play or Apple app stores, 2) directly accessible to users “out of the box”, 3) primarily intended for use by an informal (family, friend) caregiver or caregivers of a person with dementia. The included apps were then evaluated using the Mobile App Rating Scale (MARS), which includes descriptive app classification and rating using 23 items across five dimensions: engagement, functionality, aesthetics, information, and subjective quality. Next, we computed descriptive statistics for each rating. To identify recommendations for future research and app development, we categorized rater comments on the score driving factors for each item and what the app could have done to improve the score for that item. RESULTS We evaluated 17 apps (41% iOS only, 12% Android only, 47% both iOS and Android). We found that on average, the apps are of minimally acceptable quality. Although we identified apps above and below minimally acceptable quality, many apps had broken features and were rated as below acceptable for engagement and information. CONCLUSIONS Minimally acceptable quality is likely insufficient to meet care partner needs. Future research should establish minimum quality standards across dimensions for mobile apps for care partners. The design features of high-quality apps we identified in this research can provide the foundation for benchmarking those standards.


2013 ◽  
Vol 411-414 ◽  
pp. 420-424
Author(s):  
Qian Xing

With the popular of smart phone, mobile APPs have been developed largely. This paper, firstly introduces business model and market mechanism, then in terms of development technology, portal model, device set, platform integration, analyses mobile OS as well as influence on mobile APPs, at last gives a trend of mobile APP development.


2018 ◽  
Vol 17 (3) ◽  
pp. 207-224
Author(s):  
Roslyn Layton

Abstract Net neutrality or “Open Internet” rulemaking has been ongoing for more than a decade. Some 50 nations have adopted formal rules including the US (then repealed), the European Union, India, and many countries in Latin America. Among other arguments, it is asserted that net neutrality rules are necessary for application innovation. While the focus for policymakers has largely been to make rules, there is less attention on how to measure the impact of such rules and how well they achieve their innovation goals. The article summaries a specific research investigation to what degree the introduction of rules in a given country stimulates innovation in that country’s mobile app ecosystem. The focus in on mobile networks because it allowed the most consistent data across countries. The study covered 53 countries, their net neutrality policies (or lack thereof), and the results to the respective mobile application ecosystems of the countries adopting rules between the period of 2010–2016. This investigation tests the proposition that countries which adopt net neutrality rules should experience an increase in mobile app development innovation within their national economy. To test this, a statistical methodology was developed based upon measuring the number of locally developed mobile apps in the country for relevant periods before and after rules are imposed and the corresponding app downloads, usage, and revenue. Measurement was conducted with two independent toolsets and adjusted for the sophistication and penetration of advanced mobile networks in the country. To make more meaningful comparisons and avoid inevitable heterogeneity across the countries, the investigation focuses on two similar countries with different rules, Denmark with soft rules (self-regulation) and Netherlands with hard rules (legislation). The study reviewed the leading theories of innovation as well as the foundational papers in net neutrality to explain the observed discrepancies. The research finds significant statistical support for “soft” net neutrality measures adopted on a voluntary basis. Hard rules adopted through legislation and regulation were not associated with greater mobile app development for the given country. Denmark increased in local mobile app development while Netherlands decreased. Additionally, the explosion of mobile apps from countries with no net neutrality rules and the general dearth of mobile apps from countries which have had hard rules for years runs counter to expected results. This suggests that policymakers revisit their assumptions and expectations for net neutrality policy.


Systems ◽  
2020 ◽  
Vol 8 (4) ◽  
pp. 40
Author(s):  
Khaled Medini ◽  
Stefan Wiesner ◽  
Milad Poursoltan ◽  
David Romero

Today’s fast-growing demands at the global level for mobile applications (apps) cause customers to call for the customization of their apps to fit their individualized needs and business realms. Customization is a challenge for apps-development companies when they want to satisfy their numerous users in a crowded competitive market. Moreover, pursuing customization involves additional challenges when ramping up app development projects in order to meet demands at a larger scale. To address this challenge, we proposed a framework to systematize and support mobile apps’ development consistently with a customer-driven approach and modular design philosophy. From a practical point of view, the proposed framework integrates quality function deployment (QFD), axiomatic design (AD) principles, and practices from the ITIL (Information Technology Infrastructure Library) framework. The framework supports a systematic process for translating customer needs into design parameters as well as supporting prioritization of ITIL practices for further development. The effectiveness of the framework was explored in practice through a case study about an app supporting relief in the 2020 COVID-19 pandemic, as well as a survey among potential users. The assessment of the framework indicated an average score ranging between 3.58 and 3.92 in a five-point Likert scale for all of the items used in the survey.


Author(s):  
Mamta Pandey ◽  
Ratnesh Litoriya ◽  
Prateek Pandey

Software industry is turning toward endorsing application (app, in short) development due to the ubiquitous use and interest in this computing pattern. Increasing trend and popularity of mobile apps reveal several issues for the developers to address. Absence of a scientific developmental approach adds further issues to the apps development. There are millions of daily downloads, use and views on mobile apps, which give rise to an interesting phenomenon of apps acceptance by the user community. It is significant to note that users tend to reject or dislike apps that present challenges, owing to the issues in the apps, to them. Therefore, it is imperative to know the different issues that affect mobile ratings. In this paper, we have identified 14 issues by reviewing the relevant literature and collected the data from numerous mobile app stores to find the influence of the identified issues on mobile app ratings. Further, an interpretive structure modeling (ISM) approach is used to categorize the identified issues into four groups — dependent, driving, linkage and autonomous — for better understanding and further analysis. There are two objectives of this research paper: (1) to identify issues in apps which affect ratings and (2) to find out mutual relationship between dominating issues in mobile apps.


Author(s):  
Fahad S. Altuwaijri ◽  
Maria Angela Ferrario

Abstract Mobile app development has been considered as one of the fastest growing segments of the software industry both worldwide and in Saudi Arabia. Due to their pervasiveness, mobile applications call for consideration of complex and rapidly changing requirements given the diversity of their environments. Therefore, agile is considered the most suitable methodology for developing mobile apps. However, little research has investigated agile adoption in mobile app development in the real context. Therefore, the purpose of this PhD is to investigate the factors that have a significant impact on agile adoption in mobile app development by small and medium-size software organisations in Saudi Arabia. The expected key contribution of this research will be a deep insight into agile adoption in mobile app development, and the design and development of tools and techniques that may support agile adoption within Saudi context.


2018 ◽  
Vol 28 (Supp) ◽  
pp. 493-502 ◽  
Author(s):  
Armen C. Arevian ◽  
Jennifer O’Hora ◽  
Felica Jones ◽  
Joseph Mango ◽  
Loretta Jones ◽  
...  

Objective: To assess the feasibility of a novel, partnered technology development process to co-create mobile health applica­tions (apps) addressing community health priorities, using psychoeducation of cogni­tive behavioral therapy (CBT) principles for enhancing resilience as an example.Design: Stakeholder engagement, work­groups, pilot feasibility study using mixed methods during October 2013 through January 2016 over three phases: 1) defining the vision of the project and increasing technical capacity, 2) co-development and pilot testing of the app, and 3) planning for sustainability.Setting: An academic-community partner­ship in South Los Angeles, California.Participants: Eight stakeholders; 30 pilot participants from the community.Main Outcome Measures: Qualitative analysis of audio-recordings of the app development process and stakeholder inter­views, surveys of stakeholders’ perception of the development process, app use data, and feedback from pilot participants.Results: The participatory technology development process resulted in creation and pilot-testing of a resiliency-focused text messaging app. Of the 1,107 messages sent, 23 out of 30 (77%) app users responded to explore interactive content. Stakeholders reported increased perceived competency in creating mobile apps and that the process fostered a culture of co-leadership. There was also sustained engagement in mobile app development by stakeholders beyond the initial project period.Conclusions: This is the first study, to our knowledge, to demonstrate the feasibility of participatory technology development, an approach involving direct participation in the development, tailoring and maintenance of a mobile app by a broad set of stakehold­ers with high representation from racial/ ethnic minorities from an under-resourced community. Participatory technology devel­opment is a promising approach for creating sustainable, relevant and engaging health technologies across different technological, clinical and community settings.Ethn Dis. 2018:28(Suppl 2):493-502; doi:10.18865/ed.28.S2.493.


10.2196/16063 ◽  
2020 ◽  
Vol 8 (2) ◽  
pp. e16063
Author(s):  
Ting-Wei Chiang ◽  
Si-Yu Chen ◽  
Yuan-Chien Pan ◽  
Yu-Hsuan Lin

Background There are numerous mobile apps for tracking work hours, but only a few of them record work hours automatically instead of relying on manual logging. No apps have been customized for medical staff, whose work schedules are highly complicated as they have both regular hours and on-call duties. Objective The specific aims of this study were to (1) identify the Staff Hours app users’ GPS-defined work hours, (2) examine the overtime work hours from the app-recorded total work hours and the participants’ self-reported scheduled work hours, and (3) compare these app-recorded total work hours among different occupations. Methods We developed an app, Staff Hours, to automatically calculate a user’s work hours via GPS background data. Users can enter their scheduled hours, including regular hours and on-call duties. The app automatically generates overtime reports by comparing the app-recorded total work hours with the user-defined scheduled hours. A total of 183 volunteers (60 females and 123 males; mean age 32.98 years, SD 6.74) were included in this study. Most of the participants (162/183, 88.5%) were medical staff, and their positions were resident physicians (n=89), visiting staff (n=38), medical students (n=10), registered nurses (n=25), and non–health care professionals (non-HCPs; n=21). Results The total work hours (mean 55.69 hours, SD 21.34) of the 183 participants were significantly higher than their scheduled work hours (mean 50.67 hours, SD 21.44; P=.01). Medical staff had significantly longer total work hours (mean 57.01 hours, SD 21.20) than non-HCPs (mean 45.48 hours, SD 20.08; P=.02). Residents (mean 60.38 hours, SD 18.67) had significantly longer work hours than visiting staff (mean 51.42 hours, SD 20.33; P=.03) and non-HCPs (mean 45.48 hours, SD 20.08; P=.004). Conclusions Staff Hours is the first automatic GPS location–based app designed for medical staff to track work hours and calculate overtime. For medical staff, this app could keep complete and accurate records of work hours in real time, reduce bias, and allow for better complying with labor regulations.


Author(s):  
Julia Fisher

Internet systems have the potential to reach a huge and unknown audience. How easy a system is to use will usually determine its success or failure and consequently the business and yet the human factors elements of systems are rarely considered. Usability describes the ease with which people can use a system to complete a task. It is often the case however that development teams focus more on the technology and less on the users when designing systems resulting in software that is not useable and therefore does not satisfy users’ need. This chapter presents recent research, which examines one approach to developing a web-based information system and demonstrates how the composition of the development team through the inclusion of people with an understanding of user needs is important to the quality of the final product and ultimately the success of the system.


Author(s):  
Yerramalli Subramaniam ◽  
Avik Pal ◽  
Arindam Dey

Given that Agile software development is preferred methodology for products and services in life science industry, in this chapter we will describe how to adopt Agile software development process and still be compliant. We will focus on few Agile methodologies and provide details on what design controls we can adopt in order for the product and process to be compliant. We will also focus on some of the tools that can be used to help put such design and process control in place where we can have complete transparency and traceability.


Sign in / Sign up

Export Citation Format

Share Document