<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>The growing and risky industry of nomadic apps for drivers</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Carlos Carvajal</string-name>
          <email>carlos.carvajall@info.unlp.edu.ar</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andrés Rodríguez</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Alejandro Fernández</string-name>
          <email>alejandro.fernandez@lifia.info.unlp.edu.ar</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>CICPBA</institution>
          ,
          <addr-line>F.I.</addr-line>
          <institution>, LIFIA Research Center, National University of La Plata</institution>
          ,
          <addr-line>La Plata</addr-line>
          ,
          <country country="AR">Argentina</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>HCI researchers have worked for decades defining methods and techniques to assess the attention demands of in-vehicle information systems (IVIS). Acceptance test methods have been proposed that must be passed for the safe use of IVIS. Most of these methods require expensive test environments and highly trained personnel for its implementation. This article makes a review of those strategies with focus in the cost and development process phase. In the realm of mobile application ecosystems (aka "apps"), guidelines and certification programs exist. Apps must pass them to be considered as automotiveready systems or to integrate with OEM infotainment devices. However, getting into the category of certified applications does not guarantee full compliance with the criteria established by formal methods accepted by the automotive industry and international standards. Moreover, many studies show the high risk of using IVIS while driving, which lead to consider that the current predominant approaches to assess attention demands of automotive apps and to guide IVIS design are not enough. Efficient cost-benefit methods applicable in early phases of application development, as well as context-adaptive interfaces have the potential to contribute to the improvement of safe driving environments.</p>
      </abstract>
      <kwd-group>
        <kwd>IVIS</kwd>
        <kwd>driver attention</kwd>
        <kwd>empirical methods</kwd>
        <kwd>visual demand</kwd>
        <kwd>cognitive demand</kwd>
        <kwd>analytical techniques</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        A Vehicle Information System is a software application that processes vehicle data
and/or other data from different sources to finally provide valuable and
actionrelevant information to the vehicle driver and/or to other stakeholders [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. When the
Information System is used inside a car it is called: “In-Vehicle Information System”,
or IVIS. It can run as a mobile application installed in smartphones and other “mobile
or nomadic devices”. Information systems in the vehicle can be either introduced in
portable devices or run as OEM systems that are permanently installed and are part of
the original vehicle. The latter are designed by companies that understand driving and
have a group of professionals who permanently conduct studies of their applications,
Copyright c 2020 for this paper by its authors. Use permitted under Creative Commons
seeking their continuous improvement, keeping in mind to maintain safe driving
conditions.
      </p>
      <p>
        Driving distraction is understood as any activity that distracts the focus of the
primary activity that in this case is driving, including talking or writing on the phone,
talking with people in the car, manipulating the controls of devices such as stereo or
navigation system. In short, a driving distraction is any activity that moves attention
away from safe driving practices [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Many studies, both in the United States of
America and in Europe report that accidents due to driver distractions have reached
annual costs of around 40 billion dollars and 5 thousand deaths [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. There’s
considerable contribution of driver distraction caused using cell phones to traffic accidents.
Nowadays, the accident rate is inversely proportional to the age of the involved
drivers. However, it is worth asking whether decades in the future, when the current age
group of adolescents grow older, will this fact still hold? This article analyzes relevant
strategies that support the development of vehicular information systems. Section 2
compares related work with this article review. Section 3 shows formal evaluation
strategies for assessing driver distraction in the automotive context. Section 4
describes the work done by the software industry to safeguard the security of its
implementations in the automotive environment. Section 5 highlights relevant discussion
topics for this research. Finally, conclusions section aims to summarize this study and
to describe our potential future work.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Comparison to related work</title>
      <p>
        Many authors warn about the risks introduced by software applications embedded in
the vehicle. This opinion is not fully shared by Heinrich who conducted two review
articles about automotive telematic applications between 2013 and 2015. He stated
that “Despite of the concerns in the past there is no increase of accidents due to the
use of integrated devices” [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. In the introductory section of this article, it is
highlighted among several facts, that using cell phone is an important cause for traffic
accidents, with a high proportion in young population.
      </p>
      <p>
        Heinrich suggested that automotive applications can run on a smartphone, but use
the OEM installed screen, and by this way apply all the industry guidelines [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. He
agrees with the MirrorLink standard strategy (reviewed in detail later in the
“Automotive Mobile Apps” section) in which nomadic devices can only work paired with the
certified infotainment system of the car where the screen conversions are carried out
to comply with the guidelines and standards. Android Auto, since its 2019 update, no
longer allows applications to run directly from the smartphone; it forces applications
to pair with the large display of the car. However, avoiding the use of applications
directly from mobile devices is almost impossible. The development of secure mobile
applications for the automotive context constitutes an important research challenge
for Human Computer Interaction.
      </p>
      <p>
        “Speech recognition technologies may reduce the crash risk” [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Strayer et al.
presented, between 2013 and 2015, three researches[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] developing a cognitive
distraction scale for tasks in the automotive cockpit. Starting from the single activity of
operating a motor vehicle with a base quantification of 1.0, then listening radio: 1.21,
conversing with passenger: 2.33, using a hands-free cell phone: 2.27, interacting with
a speech to text system: 3.06 and finally doing mental operations with the top rating
of 5.0. They demonstrated that interacting with voice-based systems in the vehicle
may have consequences that negatively affect traffic safety [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Just listening to voice
messages (not considering a response) has a cognitive workload rating like conversing
on a cell phone. Next, they tested a personal assistant system, Apple Siri, which
required interaction with the driver and got a higher value of 4.0. in the “Strayer
workload rating” [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Therefore, Strayer and Heinrich conclusions differ greatly related
with distraction impact of speech technologies.
      </p>
      <p>
        Heinrich pointed out that more restrictive and complex standards for OEM devices
could incentivize the use of nomadic devices without controls, which potentially
affect the overall safety” [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Strayer et al. [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] observed that, when nomadic devices are
used in conjunction with the built-in infotainment systems (and the large screens they
offer), lower workload levels are obtained. However, Ramnath et al. [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] highlight the
potential dangers of these dominant ecosystems. On the one hand, they conclude that
touch interaction is so dangerous that it leads to not complying with the NHTSA
guideline on eye behavior, while voice command interaction does comply. They also
find dangerous increases in driver reaction times through voice interaction and worse
negative results through touch.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Evaluation Strategies</title>
      <p>Strategies for the evaluation of IVIS can be classify into four families. Visual demand
strategies apply empirical methods to assess the impact of the use of an application on
the visual attention of the driver. Cognitive demand strategies assess the impact of the
use of an application in the cognitive load of the driver. Analytical strategies use
predictive models to assess the potential for distraction without the need for experimental
tests or functional prototypes. Finally, subjective methods rely on the user’s opinion.
In the following sections we discuss common aspects of each of these categories and
present representative strategies. We pay special attention to the element of cost, and
applicability of each strategy in the IVIS life cycle. A table summarizes relevant
publications in each category and provides cost indicators (the research is understood as
costly when for its complexity, it could be carried out with the support of the
automotive industry or government entities), the existence of a financial sponsor, and the
stage in the IVIS development process.
3.1</p>
      <sec id="sec-3-1">
        <title>Visual Demand, Empirical Techniques</title>
        <p>
          Visual Demand research is carried out using techniques that evaluate driver gaze
behavior to asses driver workload to perform a given task. Two methods are the most
used in this domain: “glance time” and “occlusion test”. Glance time testing involves
measuring eye glance away from the road in two dimensions for a specific IVIS task:
total glance time and mean glances time, with an eye tracker device. Occlusion
Testing require a see-through device (such as lenses or googles with crystal liquid
shutters) and is used to restrict the time that the driver can see the tool under test. Goggles
are configured with the vision and non-vision times, and this is used to quantify the
time required to complete an objective. In terms of eye trackers costs, there are
professional solutions at 10,000 US Dollars [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]. Eye gaze measurements Occlusion
techniques are supported by an ISO international standard, specifically ISO 16673:
2007. Formally, Occlusion techniques require specialized goggles to achieve the
shutter and open effect, that can have a significant cost above 4.000 US Dollars [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ].
There are also studies that have simulated the effect of occlusion glasses by obscuring
the application’s interface with theoretically similar effects [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. In terms of the life
cycle of the IVIS application, empirical visual demand assessments are typically
performed in last stages of products development. This is logical, because a useful and
realistic application visual performance test is more effective as you get closer to the
product’s final version. Table 1 mentions relevant studies related to visual demand
assessments. Table 2 presents a summary of main tests used in visual demand
assessments, their metrics and whether they are defined in international standards or
guidelines.
3.2
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>Cognitive and Mixed Demand, Empirical Techniques</title>
        <p>
          The analysis of the cognitive demand provides information to designers and software
developers to gauge the usability of the portable application, for example when
presenting information in different ways and selecting alternatives less cognitively
demanding. Detection Response Task (DRT) is one of the most popular methods to
evaluate the cognitive load of a task. The method is based on the thesis that suggests
that increased cognitive load of a task would reduce the driver’s attention to other
visual, tactile or auditory information. While performing the task under test, drivers
are presented with a sensory stimulus every 3–5 seconds and are asked to respond to it
by pressing a button attached to their finger. More demanding tasks result in the
driver more frequently missing and not answering the presented DRT stimuli. “Response
times and hit rates are interpreted as indicators of the attentional effect of cognitive
load.” [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. DRT is mainly used in final development stages. Table 3 shows some
articles that report DRT using. Table 4 describes the main metrics to evaluate and the
international standard that support the method.
3.3
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>Analytical Techniques</title>
        <p>
          Analytical methods are based on predictive models that can assess the potential for
distraction without the need for experimental tests or functional prototypes. Early
stages of development can benefit by having approximate measurements of the
performance of a task and thus optimize its iterative development. This kind of
techniques aim to model the human behavior in the automotive context and requires an
important knowledge level in order to create, learn and understand the model, hence is
a challenge for Human Computer Interaction researchers [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. Table 5 summarizes
articles that report the use of analytical methods. A summary of tests commonly used
in analytical techniques, their main metrics and if they are defined in an international
standard or guideline is found in table 6.
3.4
        </p>
      </sec>
      <sec id="sec-3-4">
        <title>Subjective Methods</title>
        <p>Based on the ISO 9241-11 standard, the usability of a system refers to its ability to be
used in each context of use to achieve goals of effectiveness, efficiency and
satisfaction. Regarding the satisfaction condition, subjective user assessments are required by
asking them to rate his experience with the IVIS interaction. In table 7 is listed
representative researches of the main subjective evaluation methods. The Nasa TLX (Task
Load Index) is a widely assessment tool for perceived workload, used in wide variety
of research domains. An optimized version for the automotive context is known as:
Driving Activity Load Index – DALI. Both SUS (System Usability Scale) and DALI
methods are questionnaire type evaluations, they are simple tests to implement and
allow a quantification of user perceptions.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Automotive Mobile Apps</title>
      <p>
        Android Auto manages an ecosystem of “auto ready” mobile apps that have approved
a certification program. The Android Auto interface is optimized for the automotive
context and is manageable by touch or voice commands. In relation to Android Auto
design guidelines, it is striking that there is no specific mention of any of the formal
evaluation methods, nor to any international standards or driver distraction
international guidelines. However, many of the defined principles can be considered
inspired by good practices defined in the automotive industry. Android Auto since July
2019 introduces an important User Interface optimization and a paradigm change,
because it begins to get rid of the smartphone UI and moves towards the exclusive use
of in-car displays [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. On the other hand, Apple Car Play try to provide a safe
environment in the automotive context with iPhone ecosystem. Apple defines Human
Interface Guidelines to develop adequate apps for the driving environment. Apple
Car Play validates its guidelines compliance to adopt third party compatible apps to
its ecosystem. Nevertheless, the Apple CarPlay development API is closed and not
everyone has the possibility to build apps. It is necessary to get an Apple Mfi
Manufacturing License that is normally available by companies with their own industrial
facilities [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. Nowadays Apple Car Play has only a few third-party compatible apps.
MirrorLink is a car-based technology that claims to be designed to allow a car driver
to safely access information, entertainment and communication features from a
mobile device while driving [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. Like Android Auto and Apple CarPlay, MirrorLink
considers development guidelines for its compatible apps, based on the general
principles of industry control entities. MirrorLink development tools, examples and
tutorials are only available for Android operating system. MirrorLink requires IVIS
applications to certify at his Authorized Test Lab [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. To the date, checking the
MirrorLink website, one can see that there’s no updates for many years. In several online
forums, it is argued that the platform has lost its relevance due to Apple and Android
implementations that have taken their place [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ].
5
      </p>
    </sec>
    <sec id="sec-5">
      <title>Discussions</title>
      <p>
        There are situations where paying the right attention and being well focused can be
the difference between life and death. The automotive context is a very particular
scenario for the study of human computer interfaces, since there is a clear primary
activity set in the real and physical world, which is to drive safely. Any additional
interaction while driving constitutes a potentially dangerous competition for driver’s
attention. In line with this need, the automotive industry and government control
agencies have sponsored various investigations that have produced a series of regional
regulations and guidelines to align secondary activities related to the use of IVIS in
the driver’s cab. Wiese et al. [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ] have categorized these efforts into two groups:
Interference Mitigation and Workload Management. IVIS safety standards are related
mainly with Interference Mitigation, with strategies that minimize the number and
duration of IVIS glances required. Typical design considerations for conventional
mobile applications include maximizing user attention, but this is not consistent with
the automotive context. The software industry, in its concern about this peculiarity of
IVIS, has prepared a series of reference guides for software developers and has
prepared qualification plans for third-party applications prior to presenting them on its
car product portals. However, these validation criteria reflect a lack of rigor far from
the formality of the complex standards demanded by the automotive industry and
regional control agencies. MirrorLink makes a considerable effort to try to align itself
with the rigorous regional automotive controls, so much so that it even demands
validation of the applications in its certified laboratories. Perhaps that is precisely one of
the motivators for their loss of relevance as ecosystem for IVIS against the duopoly of
its competitors. Ramnath et al. [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] studied the reaction time of a driver under various
scenarios and found that this response was surprisingly better under the influence of
alcohol or cannabis consumption, than during the interaction with an IVIS, either in
the various implementations of Android Auto or Apple Car Play. This research was
conducted in a simulated environment and among their main conclusions find that an
undistracted driver typically reacts in 1 second to stimuli, and these times increase
percentage-wise in the following order (starting with the best results and ending with
the worst): with alcohol use, cannabis use, hands-on phone free, Android Auto by
voice, Apple CarPlay by voice, manual use of the phone, Android Auto touch, Apple
CarPlay touch [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. In short, they demonstrate that using an IVIS while driving can be
more dangerous than doing it under the influence of alcohol or cannabis which
supports the hypothesis that the current approaches that guide IVIS design are not enough
for reach adequate levels of secure drive. There is a clear condition to be solved,
which is to adapt the guidelines for the development of mobile applications that must
be optimized in their condition and treated as secondary activities in the context of
safe driving. On the other hand, effective cost-benefit strategies are required since
most formal IVIS distraction assessment methodologies are demanding in terms of
equipment and specialists to process the results, as previously highlighted in
Evaluation Strategies section. This implies that they are commonly outside the scope and
budget of typical software development and maintenance projects. The footprint of
attention of the activities required by an IVIS must be managed with a holistic
approach that does not depend solely on the magnitude of attention that the application
demands (commonly evaluated in simulated environments). Evaluation should also
acknowledge the variable attention demands of the road conditions, and of other
tools/devices/situations in the cockpit. Several approaches can be proposed at this
point, such as the idea of a collaborative "attention grounding" by Wiese et al. [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ] or
the "attention account" for pervasive attentive user interfaces by Bulling [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ]
(drawing an analogy with bank account).
6
      </p>
    </sec>
    <sec id="sec-6">
      <title>Conclusions</title>
      <p>
        Formal methodologies for IVIS attention assessment are usually complex and
expensive to implement, focused on scientific research. That is why much of the research
reviewed in this article had financial support from car manufacturers or government
entities. Lamm et al., in their analysis of the research literature on evaluation of
InVehicle Information Systems, find that methods applied at early stages of
development such as those based on predictive models of behavior are not popular in
Automotive HCI research [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ], which can be verified with a simple search in Google
Scholar and realize low number of references for articles related with predictive
methods in the IVIS context [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ].
      </p>
      <p>Nowadays Android and iOS have defined acceptance environments for IVIS
developed by third parties. Like any good practice, it coincides in its spirit with much
of what is defined by different international traffic regulatory agencies as well as
world standards like ISO and SAE. However, passing these certifications does not
guarantee compliance with the strictest acceptance levels developed by the scientific
community and used by the automotive industry for decades. We believe that there is
a lack of affordable formal methods applicable mainly in early stages of In-Vehicle
systems development, that could benefit software developers without financial
support from large corporate research projects, but who want to (and should) adhere to
formal methods for attention management in automotive context.</p>
      <p>
        The methods known as “mixed” imply the combination of quantitative and
qualitative evaluations [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ]. These have had important acceptance in other science
disciplines, but in the IVIS development niche are still considered infrequent in their
study. There’s a research opportunity when considering this approach for the study of
methods and tools that support the software developers work. The focus for this future
work will be related with techniques attached to scientific rigor and economic
feasibility in its implementation. Mixed methods like DRT variants (quantitative),
predictive techniques or software tools (economic) and usability evaluations (qualitative),
promise to be material for a framework that define what we might know as the
InVehicle Information System attention footprint.
      </p>
      <p>
        Another field to explore, is the IVIS-driver-roadway dynamic, which potentially
offers better answers to real world environments where it is not enough to consider
the resources demanded by each situation but also when and where drivers should
adapt their attention. Supporting adaptive and user focused interfaces for secondary
tasks in the demand for user attention, has a significant development potential in the
automotive context and thus contribute with the improvement of safe driving
environments.
predicting the visual
demand of IVIS [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ]
Evaluating distraction of Purucker
in-vehicle information
systems while driving by
predicting total
eyes-offroad times with KLM [
        <xref ref-type="bibr" rid="ref30">30</xref>
        ]
human behavior.
      </p>
      <p>
        KLM extended
model to predict:
Total eyes-off-road
times (TEORT).
Title
SUS – A quick and dirty
usability scale (not specified
for automotive domain)
Evaluating driver mental Pauzié
workload using (DALI) [
        <xref ref-type="bibr" rid="ref31">31</xref>
        ] A.
      </p>
      <p>Author
Brooke</p>
      <p>J.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>C.</given-names>
            <surname>Kaiser</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Stocker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Festl</surname>
          </string-name>
          , G. Lechner, and
          <string-name>
            <given-names>M.</given-names>
            <surname>Fellmann</surname>
          </string-name>
          , “
          <article-title>A research agenda for vehicle information systems</article-title>
          ,
          <source>” 26th Eur. Conf. Inf. Syst.</source>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. NHTSA, “Distracted Driving.” [Online]. Available: https://www.nhtsa.gov/riskydriving/distracted-driving. [Accessed:
          <fpage>21</fpage>
          -Apr-2019].
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>F.</given-names>
            <surname>Tango</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Botta</surname>
          </string-name>
          , “
          <article-title>Real-time detection system of driver distraction using machine learning</article-title>
          ,
          <source>” IEEE Trans. ITS</source>
          , vol.
          <volume>14</volume>
          , no.
          <issue>2</issue>
          , pp.
          <fpage>894</fpage>
          -
          <lpage>905</lpage>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>C.</given-names>
            <surname>Heinrich</surname>
          </string-name>
          , “Fighting Driver Distraction - Worldwide
          <string-name>
            <surname>Approaches</surname>
          </string-name>
          ,” no.
          <issue>13</issue>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>C.</given-names>
            <surname>Heinrich</surname>
          </string-name>
          , “
          <string-name>
            <surname>FIGHTING DRIVER DISTRACTION - RECENT DEVELOPMENTS</surname>
          </string-name>
          2013
          <article-title>-</article-title>
          <year>2015</year>
          ,” no.
          <issue>15</issue>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>8</lpage>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>D. L.</given-names>
            <surname>Strayer</surname>
          </string-name>
          et al.,
          <article-title>“Measuring Cognitive Distraction in the Automobile,” AAAFoundation</article-title>
          .org, no.
          <source>June</source>
          , pp.
          <fpage>202</fpage>
          -
          <lpage>638</lpage>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>D. L.</given-names>
            <surname>Strayer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Turrill</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. R.</given-names>
            <surname>Coleman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E. V</given-names>
            <surname>Ortiz</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Cooper</surname>
          </string-name>
          , “
          <article-title>Measuring Cognitive Distraction in the Automobile II: Assessing In-Vehicle Voice-Based Interactive Technologies</article-title>
          ,” AAAFoundation.org, no.
          <source>October</source>
          , pp.
          <fpage>202</fpage>
          -
          <lpage>638</lpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>D. L.</given-names>
            <surname>Strayer</surname>
          </string-name>
          et al.,
          <article-title>“Visual and Cognitive Demands of Using Apple's CarPlay, Google's Android Auto and Five Different OEM Infotainment Systems</article-title>
          ,”
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>R.</given-names>
            <surname>Ramnath</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Kinnear</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Chowdhury</surname>
          </string-name>
          , and T. Hyatt, “
          <article-title>Interacting with Android Auto and Apple CarPlay when driving : The effect on driver performance A simulator study</article-title>
          ,
          <source>” IAM RoadSmart</source>
          , p.
          <fpage>55</fpage>
          ,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10. “Eye Tracking Research In The Field.” [Online]. Available: https://www.tomshardware.com/news/tobii-pro-glasses-2
          <string-name>
            <surname>-</surname>
          </string-name>
          eye-tracking,
          <volume>33575</volume>
          .html. [Accessed:
          <fpage>04</fpage>
          -Nov-2019].
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11. “Visual Occlusion Goggles.” [Online]. Available: https://redscientific.com/visualocclusion-goggles.html. [Accessed:
          <fpage>04</fpage>
          -Nov-2019].
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>M. Krause</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          <string-name>
            <surname>Donant</surname>
            , and
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Bengler</surname>
          </string-name>
          , “
          <article-title>Comparing Occlusion Method by Display Blanking to Occlusion Goggles,” Procedia Manuf</article-title>
          .,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <given-names>K.</given-names>
            <surname>Stojmenova</surname>
          </string-name>
          and
          <string-name>
            <given-names>J.</given-names>
            <surname>Sodnik</surname>
          </string-name>
          , “
          <article-title>Detection-Response Task Uses</article-title>
          and Limitations,”
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <given-names>C.</given-names>
            <surname>Harvey</surname>
          </string-name>
          and
          <string-name>
            <given-names>N. A.</given-names>
            <surname>Stanton</surname>
          </string-name>
          ,
          <article-title>Usability Evaluation for In-Vehicle Systems</article-title>
          .
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15. T. Kerns, “
          <article-title>Google is getting rid of Android Auto's smartphone UI - here's why</article-title>
          ,”
          <year>2019</year>
          . [Online]. Available: https://www.androidpolice.com/
          <year>2019</year>
          /07/30/android-auto
          <article-title>-app-goingaway-assistant-driving-mode/</article-title>
          . [Accessed:
          <fpage>17</fpage>
          -Nov-2019].
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16. “
          <article-title>Discover Apple CarPlay Apps List from Third-Party Developers</article-title>
          .” [Online]. Available: https://www.cleveroad.com/blog/discover-apple
          <article-title>-carplay-apps-list-from-third-partydevelopers</article-title>
          . [Accessed:
          <fpage>03</fpage>
          -Mar-2020].
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17. C. Rosamond, “What is MirrorLink?,” Auto Express Website,
          <year>2017</year>
          . [Online]. Available: https://www.autoexpress.co.uk/car-news/99194/what-is
          <article-title>-mirrorlink-guide-to-the-carsmartphone-hook-up-system</article-title>
          . [Accessed:
          <fpage>03</fpage>
          -Mar-2020].
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>18. “MirrorLink certification for Smartphones.” [Online]. Available: https://www.7layers.com/certification/mirrorlink-certification.</mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19. “
          <article-title>Can we give Mirrorlink some attention?” [Online]</article-title>
          . Available: https://www.reddit.com/r/windowsphone/comments/5bvxm6/can_we_give_mirrorlink_so me_attention_we_need_it/. [Accessed:
          <fpage>03</fpage>
          -Mar-2020].
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <given-names>E. E.</given-names>
            <surname>Wiese</surname>
          </string-name>
          and
          <string-name>
            <given-names>J. D.</given-names>
            <surname>Lee</surname>
          </string-name>
          , “
          <article-title>Attention grounding: A new approach to in-vehicle information system implementation,” Theor. Issues Ergon</article-title>
          . Sci.,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21. A. Bulling, “
          <article-title>Pervasive Attentive User Interfaces,” Computer (Long</article-title>
          . Beach. Calif)., vol.
          <volume>49</volume>
          , no.
          <issue>1</issue>
          , pp.
          <fpage>94</fpage>
          -
          <lpage>98</lpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <given-names>L.</given-names>
            <surname>Lamm</surname>
          </string-name>
          and
          <string-name>
            <given-names>C.</given-names>
            <surname>Wolff</surname>
          </string-name>
          , “
          <article-title>Exploratory Analysis of the Research Literature on Evaluation of In-Vehicle Systems</article-title>
          ,” pp.
          <fpage>60</fpage>
          -
          <lpage>69</lpage>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <given-names>C.</given-names>
            <surname>Harvey</surname>
          </string-name>
          and
          <string-name>
            <given-names>N. A.</given-names>
            <surname>Stanton</surname>
          </string-name>
          , “
          <article-title>Trade-off between context and objectivity in an analytic approach to the evaluation of in-vehicle interfaces</article-title>
          ,”
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24. G. Burnett, “
          <article-title>How do you assess the distraction of in-vehicle information systems ? A comparison of occlusion, lane change task and medium- fidelity driving simulator methods</article-title>
          ,
          <source>” 3rd Int. Conf. Driv. Distraction Ina</source>
          .,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>R. B. Mikael Ljung</surname>
          </string-name>
          , “
          <article-title>Assessing In-Vehicle Secondary Tasks with the NHTSA VisualManual Guidelines Occlusion Method Mikael,”</article-title>
          <string-name>
            <surname>Adv. Hum. Asp. Transp.</surname>
          </string-name>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26. J. E. Domeyer, “
          <article-title>Using occlusion to measure the effects of the NHTSA participant criteria on driver distraction testing</article-title>
          ,
          <source>” Hum. Factors Ergon. Soc.</source>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27. P. Green, “
          <article-title>The 15-second rule for driver information systems</article-title>
          ,
          <source>” Proc ITS Am</source>
          .,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <given-names>D. L.</given-names>
            <surname>Strayer</surname>
          </string-name>
          and
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Cooper</surname>
          </string-name>
          , “
          <article-title>Assessing the visual and cognitive demands of in-vehicle information systems</article-title>
          ,” Cogn. Res.,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29. M. Pettitt, “
          <article-title>An extended keystroke level model (KLM) for predicting the visual demand of in-vehicle information systems</article-title>
          ,
          <source>” Hum. Factors Comput. Syst.</source>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30. C. Purucker, “
          <article-title>Evaluating distraction of in-vehicle information systems while driving by predicting total eyes-off-road times with keystroke level modeling</article-title>
          ,”
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31. A. Pauzie, “
          <article-title>Evaluating driver mental workload using the driving activity load index(DALI</article-title>
          ),
          <source>” Eur. Conf. Hum. centred Des</source>
          . Intell. Transp. Syst., pp.
          <fpage>67</fpage>
          -
          <lpage>77</lpage>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>