age is associated with changes in sensory abilities ; the most - studied age - associated sensory changes are vision and audition .
also , aspects of memory ( e.g. , keeping a lot of information active in working memory ) , online reasoning ability , and aspects of attention , such as attending to more than one source of information all show age - related declines . with the increase in numbers of the aging population
type ii diabetes affects 90% of people with diabetes around the world and is largely the result of excess body weight and physical inactivity .
self - monitoring blood glucose ( smbg ) systems have the potential to play an important role in the management of diabetes and in the reduction of risk of serious secondary clinical complications . in that regard
, mobile applications can be used as an effective tool in different self - monitoring techniques .
they are useful for all user groups from people with no overt health problems to chronic patients .
they have been tested on patients with type ii diabetes , asthma , chronic obstructive pulmonary disease ( copd ) , and different psychiatric conditions [ 58 ] . in this paper , we investigate on a practical example how elderly people specifically use mobile applications for diabetes management .
we describe the limitations that might be preventing them from adopting such digital mhealth solutions and outline and demonstrate how existing applications can be adapted to increase the usability and adoption rate .
our findings will also be put into practice with our involvement in the uncap   project , which is aimed at adapting digital health solutions and technologies for the aging population , thus helping them live independently while maintaining and improving their lifestyle .
section 2 presents the desa app and all its functionalities ; section 3 introduces the utilized methodology , where the moderating technique and the questionnaire are discussed .  
section 4 combines the results from the individual evaluations and demonstrates the changes made to the app .  
one of the most important demographic changes to diabetes prevalence across the world appears to be the increase in the proportion of people over 65 years of age .
furthermore , the number of elderly persons with type ii diabetes is expected to grow in concert with the overall increase of the elderly population .
the majority of people with diabetes in developed countries are older than 64 years . by 2030
, it is estimated that the number of people with diabetes over the age of 64 will be more than 82 million in developing countries and more than 48 million in developed countries .
the benefits include an increased feeling of safety , time and cost savings , shortened waiting queues , improved quality of life , and possibilities to develop additional health - related activities .
mhealth applications use mobile devices for collecting healthcare data , delivering healthcare data to physicians , researchers and patients , monitoring vital signs in real time and ensuring direct healthcare ( i.e. , telemedicine ) .
examples include the exchange of medical information via email , texting , smartphone apps , storing and forwarding pictures , and web - based video . according to the ims institute for healthcare informatics , in the last years
, the number of mobile health apps has soared with more than 165,000 mhealth apps available in the apple app store and google play .
the number of apps in the apple app store has doubled since 2013 , with more than 90,000 available apps .
however , only 10 percent of mhealth apps can connect to a device or sensor that provides access to medical data .
there are more than 1,700 diabetes apps in all the app stores combined ( google play , apple app store , blackberry , windows , and ovi store ) .
researchers have examined outcomes of interventions using some of these mobile phone apps for diabetes .
in , where studies of the clinical effectiveness of mobile - based applications were reviewed , they found 10 of the 13 studies in type ii diabetes and 4 of the 7 studies on type i diabetes found mhealth to lead to benefits .
other studies [ 16 , 17 ] have also found promise in using mobile app interventions .
considering the number of apps , the users are left to their own devices to find an app that they feel helps them manage their medical condition in the most beneficial way .
after the app is developed and available on the market , the developers normally receive very little feedback and have no clear understanding as to what the consumers find engaging and useful , which can significantly undermine the potential effectiveness of the intervention .
regrettably , there is no simple formula for designing engaging and effective mhealth apps , and the matter has to be addressed on a case - by - case basis .
as opposed to fitness and well - being apps , mhealth technologies are frequently designed and developed within the scope of the existing structures of the health care system . however , when including patients as part of the design team , out - of - the - box thinking is encouraged , inspiring that designers or care providers who develop the technologies to think differently , unconventionally , or from a new perspective , finally leading to applications that are better tailored to patients ' needs .
for example , the technology developers often fail to fully capture the tacit knowledge and develop useless solutions that do not address the real problems .
this is becoming unacceptable in an increasing number of fields , including diabetes , where the target market of the solution significantly overlaps with the elderly demographic group .
if the capabilities and limitations of the elderly group are not considered in the design and development process of mhealth applications , most likely results will be poor adoption and inefficient use of the technology , thus negating all resources spent on trying to solve the problem .
the goal of the study was to ascertain whether an application that was designed for general population can be efficiently used by the elderly without modifications . in our tests we used an in - house developed diabetes application called the destress assistant ( desa ) .
after the first round of tests , several modifications were made to the application , and the tests were repeated with a different set of users .
desa was designed and developed within the fistar project , with the goal of providing diabetes patients that live in remote areas a way to track their condition and keep in touch with their physician . during the design phase ,
medical staff , diabetes patients , and their next - of - kin were involved during the design phase to ensure the best possible user experience and compliance with clinically related requirements .
after the initial app was developed and tested in a hospital setting , with a group of patients of mixed demographic structure , we tested the app again , in a nonclinical setting , with a group of elderly users .
this led to identification of the possible design flaws impeding the adoption of the application within the older demographic .
since desa was developed based on feedback from multiple stakeholder groups ( patients , next - of - kin , clinicians , medical device makers , developers , and information security specialists ) , it contains a broad spectrum of features .
these include glucose diary , automatic logging of physical activity using the in - built motion sensors or add - on pedometers , macronutrient logging , self - reporting of stress , and weight and insulin boluses , as well as data logging reminders and sharing of logs directly with a physician .
desa is designed as a self - contained application that stores all the observation data on the phone . during the design phase , to comply with privacy regulations , special care was taken to ensure that data never leaves the device without the user 's consent . in a systematic review   of diabetes applications , only 17.7% of apps on the market at that time offered three or more functions and only a small number of apps offered the possibility of a connected glucometer device and transferring of data wirelessly and automatically via bluetooth to the mobile device .
desa was specifically designed to interface with the glucometer directly , by plugging the glucometer directly into the audio jack of the mobile device .
this eliminated several possible issues , including charging the batteries of the glucometer , and provided greater security and reliability than transferring data radio - based technologies such as bluetooth ( see figure 1 ) .
this proves crucial if the application aims to be both useful and usable . with desa
, multiple stakeholders were involved in the design and development process , where their needs , wants , and limitations were given special attention at each stage . with this study , we aimed to repeat the usability evaluation on an older population .
to do so , the usability evaluation method needed to be adapted with the end user in mind .
the best way to ensure usability is to have the potential users ( as well as other stakeholders ) involved in the process of solution design and development .
that way , the developers can understand the needs of the users and can address potential issues before the app is finished .
however , once the app has been developed , and a lot of research and development resources went into it , changes become increasingly hard .
the optimization problem that we wanted to address was how to improve the app without going through the whole process again and achieve maximum improvement with minimum effective modification .
for this it was important to first identify and understand the most pressing issues the users face and based on the findings and modify the app accordingly .
the first step of the evaluation process is determining whether the app should be evaluated by the experts or by the end users .
based on the extensive previous evaluations performed both by general population and by domain experts , we have chosen to perform subsequent usability evaluations on end users alone .
the users were all older than 50 , with the average age of 64.2 years .
the first step of the evaluation was thus choosing a moderating technique and designing a suitable questionnaire , as follows .
effectively moderating usability tests plays a crucial part in understanding the needs of the users .
the most common moderation techniques include the following : concurrent think aloud ( cta ) is used to understand participants ' thoughts as they interact with a product by having them think aloud while they work .
the goal is to encourage participants to keep a running stream of consciousness as they work.in retrospective think aloud ( rta ) , the moderator asks participants to retrace their steps when the session is complete .
often participants watch a video replay of their actions , which may or may not contain eye - gaze patterns.concurrent probing ( cp ) requires that as participants work on tasks  when they say something interesting or do something unique , the researcher asks follow - up questions.retrospective probing ( rp ) requires waiting until the session is complete and then asking questions about the participant 's thoughts and actions .
researchers often use rp in conjunction with other methods  as the participant makes comments or actions , the researcher takes notes and follows up with additional questions at the end of the session.our usability tests were performed in two phases on n = 10 users .
the used moderating technique was the rp with the combination of cta , which seemed to fit the target audience best .
we decided not to use the cp technique , because we wanted to let the user navigate the app freely and not lose focus .
considering the age group , we also decided the rta would increase the overall length of the session and likely cause them to lose focus .
the elderly users were asked to perform a set of tasks in the application , while the moderator observed and provided limited assistance , if needed .
after the participants completed the tasks , they were asked a set of questions , to determine how they felt using the app and to try and distinguish the possible difficulties they encountered while using the app .
concurrent think aloud ( cta ) is used to understand participants ' thoughts as they interact with a product by having them think aloud while they work . the goal is to encourage participants to keep a running stream of consciousness as they work . in retrospective
think aloud ( rta ) , the moderator asks participants to retrace their steps when the session is complete .
often participants watch a video replay of their actions , which may or may not contain eye - gaze patterns .
concurrent probing ( cp ) requires that as participants work on tasks  when they say something interesting or do something unique , the researcher asks follow - up questions .
retrospective probing ( rp ) requires waiting until the session is complete and then asking questions about the participant 's thoughts and actions .
researchers often use rp in conjunction with other methods  as the participant makes comments or actions , the researcher takes notes and follows up with additional questions at the end of the session .
the questionnaire has to be designed specifically for the end users , and not the experts evaluating the application in question ; even more importantly , it has to yield specific results .
questionnaires designed for experts typically involve testing by individuals familiar with technology and experience with using different mobile apps . for the improvement and adaptation of the app ,
we need to highlight specific issues that have to be handled in order for the app to be beneficial for the older demographic . in the scientific literature
one such tool is the mobile app rating scale ( mars ) , developed by .
they considered existing guidelines for evaluating the usability of mhealth apps and came to the conclusion that they were incomplete and a reliable and objective instrument was still needed . for this reason , they developed a multidimensional scale for classifying and rating the quality of mobile health apps .
the largest drawback of the mars scale , with respect to the elderly , is the fact that it recommends the evaluators complete a training exercise and thoroughly explore the app 's content and functionalities .
this means that users that are not familiar with the app will not be able to fully rate it .
the questionnaire is also far too complex for the average user and it is not geared towards elderly users . in fact , the main reason for the training exercise is the complexity of the questionnaire .
after careful consideration , we decided to adapt the questionnaire developed by   instead of the mars scale . due to the complexity of most questionnaires and their target audience not being elderly users
, we decided to use one that would allow us to gather as much useful information as possible and at the same time not confuse and strain the respondents .
the questionnaire was not primarily developed for elderly users to evaluate the app but was adapted and yielded quick and specific results .
however , some questions still had to be answered by an expert , because they were either beyond the scope of the performed test , or because they were based on experiencing rare occurrences .
for example , the questions about fault tolerance can only be answered , if a mistake is made while entering data .
since the users in our case have not encountered that issue and could not know how or if the app manages erroneous input , they could not answer this question .
in addition to the chosen and adapted questionnaire ( see table 1 ) , we also decided to use the system usability scale ( sus ) , as sus has become an industry standard , with references in over 1300 articles and publications .
sus was not intended to diagnose usability problems , but it can be used for benchmarking outside of a usability test . in our care , it would serve as a comparison of perceived usability between before and after the applied changes .
strongly agree  to  strongly disagree .  in order to get the best ranking ( a ) , a score above an 80.3 is needed ( see figure 2 ) .
this is also the point where users are more likely to be recommending the product to a friend . scoring at the mean score of 68 equals a c and anything below a 51 is an f ( the bottom 15% ) .
age - specific requirements , such as screen size , colour , and use of symbols normally familiar to younger users , can cause usability issues in older users .
also , differentiations between clickable and unclickable areas , all play an important role in the end user 's desire to use the application .
our objective was to determine specific issues and relay that information to the developers as simply and clearly as possible , so the problems could be dealt with and the app could be optimised for older users .
the results can also be used as a guide when designing applications for the elderly , as they offer certain guidelines and highlight important areas .
the first test included users over the age of fifty , with the average age of 64 .
they were instructed to open the application and perform the following tasks : ( 1 ) measure their blood glucose level , ( 2 ) record their stress level , ( 3 ) view the data on the charts , ( 4 ) review the data in the logbook , and ( 5 ) send the data to their physician ( see figure 3 ) .
the moderator was observing the user and helping them with simple suggestions , if they did not know how to perform the task .
after the test was completed , they were asked to answer the two chosen questionnaires and grade their experience .
the questions that were deemed unsuitable for the users , specifically the criterion of  general characteristics ,  were answered by an expert .
this was done because we consider the fault tolerance / fault management to be an important aspect of mhealth apps and should be handled appropriately . if a user does not input an erroneous value during the test , they would never notice this feature was not available , but a regular user would encounter this problem eventually . analysing the results , the evaluations were in the range of 3.0 to 4.3 , which corresponds to a moderate to good rating of the app .
comprehensibility ,  specifically the subcriterion of  simple comprehensibility and interpretability of displayed images and depictions ,  with a total average value of 2.6 ( the rationale for the low score by the users was  the symbols do not look like buttons .
they look like random images .  ,  i could not find the  add ' and  menu ' buttons 
the lowest scored characteristic was the  provision of additional explanations ,  with the average value of 1.8 .
this rating comes as no surprise , as there was no welcome wizard or any other help in the app .
the app received the best rating for the criterion  presentation  ( 4.3 ) followed by  usability  ( 3.5 ) ( the rationale for the good rating in  presentation  was  the screen size is very good .
i can use the application without my glasses  ,  i like the colours used in the app and the text is big enough  , etc . ) .
the criterion valued by the expert was rated the worst with the value of 1 , due to the fact that the subcriterion of  high fault tolerance / efficient fault management  was not dealt with properly in the app .
the data input was not limited to meaningful values and there was a lack of user feedback in the case of erroneous data input .
both of these problems were also detected by one of the users who had issues measuring blood glucose automatically and decided to input it manually .
when they made a mistake while choosing the blood glucose level , they were not alerted to a possible error .
the following categories of problems were represented the most : the app was missing a welcome wizard with instructions to help the user get started.the icons used on buttons were confusing ; there were problems differentiating between a button and an image or text.the app was missing error notifications ( e.g. , in case of erroneous input).the input data was not validated or limited to meaningful values ( e.g. , the possibility of choosing dates in the future).the users found the first screen ( dashboard ) of the newly installed app confusing , due to the lack of any data or instructions .
there were problems distinguishing the buttons on the screen ; only the users with prior smartphone experience could find the add ( + ) button , but even these could not find the menu (  ) button ( see figure 5(a ) ) .
all the other users had to be aided in finding both buttons to initiate the testing procedure .
the app was missing a welcome wizard with instructions to help the user get started .
the icons used on buttons were confusing ; there were problems differentiating between a button and an image or text .
the app was missing error notifications ( e.g. , in case of erroneous input ) .
the input data was not validated or limited to meaningful values ( e.g. , the possibility of choosing dates in the future ) . if the welcome wizard would guide the user and offer an explanation of the different button symbols and what they represent , the user might find the application easier to use .
the two most common cognitive declines that accompany aging both affect the memory function , either the working memory , that is , the ability to maintain information actively as it is being processed , or the episodic memory , which has the ability to store new memories of events .
therefore , it might be more beneficial to make the buttons clearer and simplify the use .
the buttons should have text or symbols with text , so the user knows what they represent .
the sus score of the first test was 64.4 ( see figure 6(b ) ) , which gives it a d grade or the percentile rank of 30% .
after reviewing the questionnaire results , modifications were made in the app 's appearance and functionalities .
the first step was to add a welcome wizard , which helps a new user learn how to use the app ( see figure 4 ) .
the next step was to change the button symbols into text and enable the ios accessibility functions which allow a user to enlarge text and , if needed , draw button shapes to make buttons more apparent ( figure 5(b ) ) . additionally , error notifications and input checking ( limiting values to meaningful numbers ) were also added .
most users did not detect this problem , but it was observed by the moderator and could present a significant usability issue when used frequently .
next , the text colour of the add menu was changed to increase contrast , because some users had a problem with distinguishing black letters on the dark background .
the second testing phase was performed on a different set of users with the average age of 65 .
the same moderating technique was adopted and the users filled out both questionnaires ( sus and table 1 ) .
the sus results were slightly higher than the first evaluation with a score of 84.5 ( see figure 6(b ) ) .
all criteria rated better in the second evaluation , with the smallest difference in the criterion  presentation  , which was already the best graded category in the first test ( with the average score of 4.5 ) .
criterion , with an increase from 3.5 to 4.3 ( see figure 6(b ) ) .
since the average age of the population in developed world is increasing , the number of chronic conditions is also on the rise . for all interventions involving mobile apps ,
our own experience has shown that not involving elderly users in the design and development process can cause significant usability barriers in that demographic .
this is especially true when such app is meant to be used by the same target population that also has the highest prevalence of the disease . during the evaluations
, two users stood out ; one of them had no experience with touchscreen devices , used an old mobile phone for making calls only , had never used the internet or sent any text messages , and had never used a computer .
the other one was an advanced user that had used different sports apps in connection with body sensors to track his physical activity .
a common problem with elderly users is their reluctance to press buttons due to the fear of breaking something .
the advanced user clicked around the screen until he found what he was looking for , while the others spent a lot of time observing the screen and trying to determine the correct step .
but there are of course users that could still have problems using the app , especially users with limited technical proficiency .
such users would benefit from having assistance until they get comfortable with using new technology .
a similar approach will be used in the project uncap where the technology training and familiarization have started long before the service is available to the users .
this means the users will already be acquainted with different aspects of using mobile apps .
such training with caregivers also gives the developers valuable insight into what users want and need .
the most important points to keep in mind when designing an app for the elderly are thus the size , visibility , and comprehensibility of buttons and symbols .
most modern devices ( including those running ios and android ) have built - in accessibility support that can be enabled in the app , in case users need to enlarge the text size , enable voice over , invert colours , and so forth .
however , in case of ios , the app needs to specifically support it , which is highly recommended .
they can be in the form of a welcome wizard or as an additional button , which is always available to the user in case they need assistance .
age - related memory decline and not being very familiar with the technology can cause the user to become easily confused ; therefore , it is very important to give them the possibility of looking for help .
the general trend in this area is worrying , with device makers making unsubstantiated claims about their devices being simple to use , while this may increasingly not be the case anymore .
next , colour contrast needs to be taken into account for users with poor eyesight ; when using stronger background colours , the designer has to make sure the text remains legible .
this problem is further exacerbated with modern high - resolution screens , which allow even thinner fonts with poorer legibility .
this goes hand in hand with the recent shifts from skeuomorphic to flat design mobile operating systems , as it has a significant impact on the overall usability .
for example , earlier versions of ios implemented a skeuomorphic design , styling the user interfaces with the specific goal to resemble real - world objects .
this greatly aided the first - time users and educated them on how to use the applications by analogy . by ensuring the app has all the accessibility functions enabled , at least some of the issues attributed to flat design can be mitigated .
handling exceptions and faults , as well as validating user input , is of crucial importance both for ease of use and for ensuring clean and valid data .
this is especially important in mhealth apps , where medical decisions can be later made based on faulty data , having significant impact on the well - being of the patient .
we understand that the test users did not use all of the functionalities of the app , which could affect the overall score significantly . in
, the authors came to the conclusion that the presence of documentation and analysis functions reduced the usability score significantly .
since the desa app was not compared to other apps , we could not determine whether an application with fewer functions would be preferable to the users ; however , we do estimate that the larger number of features makes the app harder to use .
in this paper , we performed an evaluation of an existing diabetes app in two consecutive test trials with elderly users , using two different questionnaires in parallel .
the overall results show , that applications developed for the general population are not necessarily suitable for elderly users , which can be a significant problem , especially if they address the issues of the elderly users specifically .
we demonstrated that , with a limited amount of modifications , an existing app can be significantly improved to better suit elderly users .
this could also be facilitated by creating different profiles to optimize the app for different accessibility groups ( e.g. , poor eyesight and limited dexterity ) .
a user could simply select their profile and the app would be configured to their preferences .
such personalization features would of course have significantly larger impact and reach , if they were consistently implemented in all of the major mobile device operating systems . making apps that would suit any and
the best one can currently do is focus on some characteristics that most users of the target group have in common and try to adapt the app to best suit their needs . considering the number of older users that will need the help of mhealth apps in the future , it is increasingly important to focus our efforts on delivering beneficial solutions that will suit this demographic .
 diabetes mellitus has high prevalence in the ageing population and is often accompanied by other comorbidities , such as alzheimer 's disease , and general disabilities , such as poor eyesight . 
 these comorbidities have redefined ways in which patients use mhealth apps , including diabetes apps . 
 the latter have proven benefits for monitoring blood glucose levels and insulin tracking in the general population . in this paper 
 , we analyse a diabetes monitoring app destress assistant ( desa ) , which was developed as a part of an eu project and tested in a hospital setting . due to the increasing number of older adults 
 , we wanted to ensure the app was suitable for that demographic . 
 based on a number of supervised tests , we show that the app , which was developed with the help of workshops and feedback from tech - savvy patients and clinicians , is difficult to use by elderly users . 
 we demonstrate that with a small number of changes it is possible to raise the usability of the app in a number of categories . 
 we summarise the lessons learned in the discussion . 
 our findings demonstrate that special care needs to be taken when developing mhealth apps for the elderly population . 
1. Introduction
2. The DeStress Assistant (DeSA)
3. Usability Evaluation Methodology
4. Results
5. Discussion
6. Conclusion