Multiplatform and Mobile App Development in Scheme with Gambit/SchemeSpheres

2014 ◽  
Author(s):  
Álvaro Castro-Castilla
Keyword(s):  
Mobile App ◽  
App Development

scholarly journals Quality of Mobile Apps for Care Partners of People with Alzheimer’s Disease and Related Dementias: Mobile App Rating Scale Evaluation (Preprint)

2021 ◽  
Author(s):  
Nicole E Werner ◽  
Janetta C Brown ◽  
Priya Loganathar ◽  
Richard J Holden
Keyword(s):  
Rating Scale ◽  
Mobile Apps ◽  
Mobile App ◽  
Future Research ◽  
App Development ◽  
Care Partners ◽  
Acceptable Quality ◽  
The Us ◽  
Google Play

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.

Mobile app development for the Indian market

IEEE Software ◽  
2014 ◽  
Vol 31 (3) ◽  
pp. 17-20
Author(s):  
Rahul D. Sadafule
Keyword(s):  
Mobile App ◽  
Indian Market ◽  
App Development

Onshore Mobile App Development: Successes and Challenges

Computer ◽  
2011 ◽  
Vol 44 (9) ◽  
pp. 102-104
Author(s):  
Christopher L. Huntley
Keyword(s):  
Mobile App ◽  
App Development ◽  
Successes And Challenges

Comparison of Mobile Operating System Based on Development and Application

2013 ◽  
Vol 411-414 ◽  
pp. 420-424
Author(s):  
Qian Xing
Keyword(s):  
Operating System ◽  
Business Model ◽  
Mobile Apps ◽  
Smart Phone ◽  
Mobile App ◽  
Market Mechanism ◽  
App Development ◽  
Development Technology ◽  
Model Device

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.

scholarly journals Recommendations for Developing Support Tools With People Suffering From Chronic Obstructive Pulmonary Disease: Co-Design and Pilot Testing of a Mobile Health Prototype

10.2196/16289 ◽  
2020 ◽  
Vol 7 (2) ◽  
pp. e16289
Author(s):  
Alan Davies ◽  
Julia Mueller ◽  
Jean Hennings ◽  
Ann-Louise Caress ◽  
Caroline Jay
Keyword(s):  
Chronic Obstructive Pulmonary Disease ◽  
Pulmonary Disease ◽  
Health Care Professionals ◽  
Experience Sampling ◽  
Well Being ◽  
Mobile App ◽  
Lessons Learned ◽  
Chronic Obstructive ◽  
Obstructive Pulmonary Disease ◽  
App Development

Background Gaps exist between developers, commissioners, and end users in terms of the perceived desirability of different features and functionalities of mobile apps. Objective The objective of this study was to co-design a prototype mobile app for people with chronic obstructive pulmonary disease (COPD). We present lessons learned and recommendations from working on a large project with various stakeholders to develop a mobile app for patients with COPD. Methods We adopted a user-centered, participatory approach to app development. Following a series of focus groups and interviews to capture requirements, we developed a prototype app designed to enable daily symptom recording (experience sampling). The prototype was tested in a usability study applying the think aloud protocol with people with COPD. It was then released via the Android app store, and experience sampling data and event data were captured to gather further usability data. Results A total of 5 people with COPD participated in the pilot study. Identified themes include familiarity with technology, appropriate levels for feeding back information, and usability issues such as manual dexterity. Moreover, 37 participants used the app over a 4-month period (median age 47 years). The symptoms most correlated to perceived well-being were tiredness (r=0.61; P<.001) and breathlessness (r=0.59; P<.001). Conclusions Design implications for COPD apps include the need for clearly labeled features (rather than relying on colors or symbols that require experience using smartphones), providing weather information, and using the same terminology as health care professionals (rather than simply lay terms). Target users, researchers, and developers should be involved at every stage of app development, using an iterative approach to build a prototype app, which should then be tested in controlled settings as well as in the wild (ie, when deployed and used in real-world settings) over longer periods.

Sign in / Sign up

Export Citation Format

Share Document