Severity: Warning
Message: file_get_contents(https://...@pubfacts.com&api_key=b8daa3ad693db53b1410957c26c9a51b4908&a=1): Failed to open stream: HTTP request failed! HTTP/1.1 429 Too Many Requests
Filename: helpers/my_audit_helper.php
Line Number: 176
Backtrace:
File: /var/www/html/application/helpers/my_audit_helper.php
Line: 176
Function: file_get_contents
File: /var/www/html/application/helpers/my_audit_helper.php
Line: 250
Function: simplexml_load_file_from_url
File: /var/www/html/application/helpers/my_audit_helper.php
Line: 3122
Function: getPubMedXML
File: /var/www/html/application/controllers/Detail.php
Line: 575
Function: pubMedSearch_Global
File: /var/www/html/application/controllers/Detail.php
Line: 489
Function: pubMedGetRelatedKeyword
File: /var/www/html/index.php
Line: 316
Function: require_once
Background: Physical inactivity is a global health issue, and mobile health (mHealth) apps are expected to play an important role in promoting physical activity. Empirical studies have demonstrated the efficacy and efficiency of app-based interventions, and an increasing number of apps with more functions and richer content have been released. Regardless of the success of mHealth apps, there are important evidence gaps in the literature; that is, it is largely unknown who uses what app functions and which functions are associated with physical activity.
Objective: This study aims to investigate the use patterns of apps and wearables supporting physical activity and exercise in a Japanese-speaking community sample.
Methods: We recruited 20,573 web-based panelists who completed questionnaires concerning demographics, regular physical activity levels, and use of apps and wearables supporting physical activity. Participants who indicated that they were using a physical activity app or wearable were presented with a list of app functions (eg, sensor information, goal setting, journaling, and reward), among which they selected any functions they used.
Results: Approximately one-quarter (n=4465) of the sample was identified as app users and showed similar demographic characteristics to samples documented in the literature; that is, compared with app nonusers, app users were younger (odds ratio [OR] 0.57, 95% CI 0.50-0.65), were more likely to be men (OR 0.83, 95% CI 0.77-0.90), had higher BMI scores (OR 1.02, 95% CI 1.01-1.03), had higher levels of education (university or above; OR 1.528, 95% CI 1.19-1.99), were more likely to have a child (OR 1.16, 95% CI 1.05-1.28) and job (OR 1.28, 95% CI 1.17-1.40), and had a higher household income (OR 1.40, 95% CI 1.21-1.62). Our results revealed unique associations between demographic variables and specific app functions. For example, sensor information, journaling, and GPS were more frequently used by men than women (ORs <0.84). Another important finding is that people used a median of 2 (IQR 1-4) different functions within an app, and the most common pattern was to use sensor information (ie, self-monitoring) and one other function such as goal setting or reminders.
Conclusions: Regardless of the current trend in app development toward multifunctionality, our findings highlight the importance of app simplicity. A set of two functions (more precisely, self-monitoring and one other function) might be the minimum that can be accepted by most users. In addition, the identified individual differences will help developers and stakeholders pave the way for the personalization of app functions.
Download full-text PDF |
Source |
---|---|
http://www.ncbi.nlm.nih.gov/pmc/articles/PMC10690103 | PMC |
http://dx.doi.org/10.2196/49148 | DOI Listing |
Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!