<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing with OASIS Tables v3.0 20080202//EN" "journalpub-oasis3.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:oasis="http://docs.oasis-open.org/ns/oasis-exchange/table" dtd-version="3.0"><?xmltex \hack{\hyphenpenalty= 8000}?><?xmltex \hack{\sloppy}?>
  <front>
    <journal-meta>
<journal-id journal-id-type="publisher">NHESSD</journal-id>
<journal-title-group>
<journal-title>Natural Hazards and Earth System Sciences Discussions</journal-title>
<abbrev-journal-title abbrev-type="publisher">NHESSD</abbrev-journal-title>
<abbrev-journal-title abbrev-type="nlm-ta">Nat. Hazards Earth Syst. Sci. Discuss.</abbrev-journal-title>
</journal-title-group>
<issn pub-type="epub">2195-9269</issn>
<publisher><publisher-name>Copernicus GmbH</publisher-name>
<publisher-loc>Göttingen, Germany</publisher-loc>
</publisher>
</journal-meta>

    <article-meta>
      <article-id pub-id-type="doi">10.5194/nhessd-3-4555-2015</article-id><title-group><article-title>Teaching disaster preparedness via a mobile device: a study of Auckland Civil
Defence's Smartphone Application</article-title>
      </title-group><?xmltex \runningtitle{Teaching disaster preparedness via a~mobile device}?><?xmltex \runningauthor{O.~Kulemeka}?>
      <contrib-group>
        <contrib contrib-type="author" corresp="yes" rid="aff1 aff2">
          <name><surname>Kulemeka</surname><given-names>O.</given-names></name>
          <email>owen.kulemeka@ou.edu</email>
        <ext-link>https://orcid.org/0000-0002-6592-5974</ext-link></contrib>
        <aff id="aff1"><label>1</label><institution>University of Oklahoma, College of Journalism and Mass Communication, Norman, OK, USA</institution>
        </aff>
        <aff id="aff2"><label>†</label><institution>deceased</institution>
        </aff>
      </contrib-group>
      <author-notes><corresp id="corr1">O. Kulemeka (owen.kulemeka@ou.edu)</corresp></author-notes><pub-date><day>3</day><month>August</month><year>2015</year></pub-date>
      
      <volume>3</volume>
      <issue>8</issue>
      <fpage>4555</fpage><lpage>4583</lpage>
      <history>
        <date date-type="received"><day>17</day><month>May</month><year>2015</year></date>
           <date date-type="accepted"><day>21</day><month>June</month><year>2015</year></date>
      </history>
      <permissions>
<license license-type="open-access">
<license-p>This work is licensed under a Creative Commons Attribution 3.0 Unported License. To view a copy of this license, visit <ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/3.0/">http://creativecommons.org/licenses/by/3.0/</ext-link></license-p>
</license>
</permissions><self-uri xlink:href="https://nhess.copernicus.org/preprints/3/4555/2015/nhessd-3-4555-2015.html">This article is available from https://nhess.copernicus.org/preprints/3/4555/2015/nhessd-3-4555-2015.html</self-uri>
<self-uri xlink:href="https://nhess.copernicus.org/preprints/3/4555/2015/nhessd-3-4555-2015.pdf">The full text article is available as a PDF file from https://nhess.copernicus.org/preprints/3/4555/2015/nhessd-3-4555-2015.pdf</self-uri>


      <abstract>
    <p>This content analysis study examined whether a disaster preparedness
education smartphone application created by a New Zealand city matches
what experts say are effective ways of teaching disaster preparedness
and teaching via an app. The app was assessed to ascertain if it
excelled as a platform for learning, communicated effectively,
addressed factors that can hinder people from preparing, and provided
information for special needs populations. Results show that the app
addressed most factors that hinder preparedness, provided information
for some special needs populations, excelled as a platform for
learning, and communicated effectively. The app's weaknesses include
the fact that it lacked targeted information for low-income
residents. The findings provide insight on how organizations can
effectively use apps to teach disaster preparedness.<?xmltex \hack{\newline}?><?xmltex \hack{\newline}?>
<bold>The author passed away before the publication of this discussion paper. <?xmltex \hack{\newline}?> Therefore, a final revised paper is not foreseen.</bold></p>
  </abstract>
    </article-meta>
  </front>
<body>
      

<sec id="Ch1.S1" sec-type="intro">
  <title>Introduction</title>
      <p>Following a 2011 earthquake that killed 185 people and cost
over
USD 25 billion, disaster preparedness is a key concern in New
Zealand. Auckland Civil Defence, the disaster agency of the country's
largest city, has warned that only one in 10 Aucklanders is ready for
disasters (Day, 2014). To address this, the agency has created
a smartphone application (app) to teach residents disaster
preparedness. The agency is not alone in using an app for disaster
preparedness education: the U.S. Federal Emergency Management Agency
and Emergency Management Australia also have apps for this purpose.</p>
      <p>When this researcher examined the Auckland Civil Defence app in
February 2015, it was organized as follows. First time app users were
shown welcome screens explaining the app's purpose. After these
screens, a user could log in using an email address or a Facebook
username. Once logged in, the user faced four pages: home, plan, people,
and info. The home page showed critical information about pending or
occurring disasters as well as preparedness events such as evacuation
drills.</p>
      <p>The plan page allowed a user to create a preparedness plan in six
steps that included reading about disasters that can affect Auckland,
entering emergency contact information, listing emergency supplies,
and indicating an emergency meeting point. On the people page, a user
could connect with friends and family members via email, SMS or
Facebook. With these connections, a user could see the progress peers
were making in crafting disaster plans.</p>
      <p>The info page described disasters Auckland is at risk of, showed
disaster related events occurring in Auckland, explained how special
needs groups should prepare for disasters, and outlined special
disaster information (e.g., insurance). In addition, how to contact
emergency officials, what radio stations to listen to, how to receive
SMS alerts, how to volunteer, and how to access disaster help were
explained. Figures 1–4 show images of the app.</p>
      <p>This study examined the Auckland Civil Defence's app to understand two
things. First, whether the app taught in a way that matched what
experts say are effective ways of teaching people to prepare for
disasters. Second, whether it taught in ways matching what experts say
are effective ways of teaching via a mobile app. Answering these
questions can help others considering using apps to teach disasters
preparedness. The paper opens by describing what is known regarding
effectively teaching people how to prepare for disasters and
effectively teaching people via mobile devices. The research questions
are outlined, the methodology is explained, findings are revealed, and
implications as well limitations are discussed.</p>
</sec>
<sec id="Ch1.S2">
  <title>Literature review</title>
<sec id="Ch1.S2.SS1">
  <title>Effectively teaching people disaster preparedness</title>
      <p>Researchers have shown that a variety of factors can help or hinder
efforts to teach people disaster preparedness. These factors include
environmental cues, social context, source credibility, warning
channels, warning content, past experience, lack of resources, and
residency barriers (Lundgren and McMakin, 2013). When people see or
hear cues in the environment that show that a hazard exists, some are
more likely to prepare (Sattler et al., 2000). Social context, the
relationships people are part of, also influence disaster
preparedness. Some people are more likely to prepare when they see
friends preparing (Patterson et al., 2010). How people perceive the
credibility of a source can influence preparedness actions. Because
people vary significantly in regards to whom they find credible,
researchers recommend using multiple sources to encourage preparedness
(Sorensen and Sorensen, 2006). Preparedness messages are also
distributed through conversations, television, websites, newspapers
and other channels. Because people vary in regards to which channels
they pay attention to and find trustworthy, researchers recommend
distributing preparedness messages through diverse channels (Lindell
and Perry, 2004).</p>
      <p>In regards to message content, researchers recommend that preparedness
messages should counter arguments or myths that people have regarding
disasters preparedness. Messages should be repeated so that people pay
attention but not excessively to avoid annoying people (Lindell and
Perry, 2004). Past experience with disasters can also influence
preparedness actions. Drabek (1999) noted that depending on
circumstances, individuals who have experienced a disaster in the past
are more likely or less likely to follow preparedness
advice. Preparedness messages should therefore factor past experience.</p>
      <p>Demographic characteristics also impact disaster preparedness. In
particular, low-income individuals, recent immigrants, and individuals
with disabilities face challenges preparing for disasters (Bolin,
2006). Many preparedness campaigns ask individuals to purchase extra
food and supplies which can be difficult for the poor. Some
communities with large immigrant populations not fluent in the local
language do not provide translated disaster preparedness education
material or provide poorly translated items (James et al.,
2007). Undocumented migrants sometimes do not access government
provided disaster services because they fear arrest. For example,
during Hurricane Ike in Texas, some undocumented individuals did not
seek help from government agencies because officials refused to ease
immigration policing during the early part of the disaster (Wilson
and Tiefenbacher, 2012). Many communities also do not adequately
address challenges people with disabilities face when preparing for
disasters. The result is that many with disabilities are hurt or die
in disasters (Rooney and White, 2007).</p>
      <p>This literature revealed to this researcher that one way to assess the
Auckland Civil Defence app could be to examine how well it addressed
factors that can hinder disaster preparedness. For example, whether
the app showed users cues in the environment illustrating the
likelihood of a disaster occurring or how well the app addressed myths
people may have about preparing for a disaster. From this literature,
the first question that guided this study was therefore developed:</p>
      <p>RQ1: Does the Auckland Civil Defence app address these factors that
can hinder people from preparing for disasters: environmental cues,
social context, source credibility, warning channels, warning content,
past experience, lack of resources, and residency barriers?</p>
      <p>Across the world, there is increased realization that disaster
preparedness efforts should factor in people who are marginalized and
vulnerable (e.g., racial-ethnic minorities, individuals with
disabilities) (Blaikie et al., 2014). In the US, the lessons learned
after Hurricane Katrina have spurred efforts to ensure that disaster
preparedness efforts take into consideration the challenges faced by
traditionally marginalized groups (Baker and Cromier, 2014). Kailes
and Enders (2007) argued that in order to avoid marginalizing
vulnerable individuals, disaster preparedness education efforts should
address the requirements of those with communication needs:
individuals with reduced or no ability to hear, see, or speak; those
with limited or no ability to speak, read, or understand the local
language; and those with limited ability to understand or
learn. Preparedness educators should also provide information for
those with medical needs (e.g., chronic conditions), those who utilize
animals or devices to maintain independence (e.g., wheelchairs,
hearing aids), and those requiring transportation assistance (e.g.,
those who cannot afford a vehicle and those legally restricted from
driving). In addition, information should be provided for care
providers of individuals requiring supervision (e.g., nurses for
individuals with dementia) (Kailes and Enders, 2007).</p>
      <p>These works revealed that a second way to assess the Auckland app
could be to examine how well it addressed the challenges marginalized
and vulnerable individuals face when preparing for
a disaster. Specifically, how well the app provided information on how
people with unique communication, medical, independence, supervision,
and transportation needs can prepare for a disaster. From this
literature, the second question that guided this study was crafted:</p>
      <p>RQ2: Does the Auckland Civil Defence app provide preparedness
information for people with communication, medical, independence,
supervision, and transportation needs?</p>
      <p>Another issue experts say preparedness education should cover is
animals. In past disasters, some people have refused to evacuate due
to fear regarding what will happen to their pets or livestock. Many
shelters do not accept pets while livestock pose unique evacuation
challenges. Experts emphasize that preparedness education should
address animal owner needs (Heath, 2001; Thompson, 2013). This
literature revealed that a third way to assess the New Zealand app
could be to ascertain how well it addressed issues faced by pet and
livestock owners. Therefore, this third research question was drafted:</p>
      <p>RQ3: Does the Auckland Civil Defence provide preparedness information
for animal owners?</p>
      <p>The next section examines research on how to effectively teach and
communicate information using apps.</p>
</sec>
<sec id="Ch1.S2.SS2">
  <title>Effectively teaching people via apps</title>
      <p>Apps, as teaching tools, are advantageous in various ways. Removed
from the confines of classrooms, app users can learn from anywhere
they have mobile devices (El-Hussein and Cronje, 2010). Apps also
allow material to be learned and put to use immediately. For example,
residents can browse a grocery store and use an app to learn what
items to buy for an emergency. Learning on apps is often cheaper and
brings lessons to those who find attending classrooms difficult (Gu
et al., 2011).</p>
      <p>Despite their positives, apps have limitations. Learning on an app can
be fragmented because without supervision, learners on apps can stop
or digress anytime. This loss of continuity can hinder learners from
grasping concepts that require uninterrupted, supervised focus. Apps
also often lack instructor feedback leaving learners without answers
to their questions (Park, 2011). Creating apps is also a complicated
process requiring knowledge in programming, mobile learning, and
specialized subject matter (e.g., disasters). In addition, app
designers have to make sure apps work on diverse hardware and
software. Many organizations cannot meet these requirements and create
apps ill suited for learning (Harrison et al., 2013).</p>
      <p>The realization that poorly designed apps can fail drives research on
how to design effective apps. Numerous organizations that have
invested millions in apps want to know if their apps meet the needs of
users and are achieving desired goals. Various experts on mobile
learning have developed guidelines on how to design mobile learning
platforms such as apps that are usable and excel as platforms for
learning. These experts (e.g., Dillard, 2012; Elias, 2011;
Kukulska-Hulme and Traxler, 2013; Wang and Shen, 2012) have argued
that mobile learning platforms such as apps, in order to excel as
platforms for learning, should: (a) have intuitive and simple
interfaces, (b) incorporate multimedia because people find learning
easier if they see more than just text, (c) present lessons in short
chunks to accommodate the fact that human short term memory is
limited, (d) be engaging and entertaining, (e) provide content that is
relevant to learners, (f) deliver information fitting users' immediate
needs and contexts, and (g) provide access to information even when
not connected to wireless networks. From this review, it was evident
that a fourth way to assess the Auckland app could be to ascertain if
the app possessed characteristics that scholars argue are present in
apps that excel as platforms for learning. Hence, this fourth research
question was drafted:</p>
      <p>RQ4: Does the Auckland Civil Defence app exhibit principles of an app that
excels as a platform for learning: (a) simple and intuitive interface;
(b) incorporates multimedia; (c) information that is contextual and relevant
to the learner; (d) just-in time delivery; and (e) offline access?</p>
      <p>Additional guidelines on designing apps that excel as learning
platforms have emerged from health research. As health related apps
have grown in numbers, scholars worried about the accuracy of the
information in these apps have developed principles on how to design
apps that communicate effectively. An example is the principles
developed by Huckvale et al. (2012, 2015) in their research on how to
design asthma apps that communicate effectively. These researchers
have argued that an app that communicates effectively should have
information attributed to an author whose qualifications are mentioned
(when information was written and modified should also be indicated),
claims supported by evidence, and a privacy policy regarding how app
user information is used. In addition, who paid to create the app
should be identified, external influences that could affect the
objectivity of app content should be revealed, and a way to contact
app creators should be provided. The purpose of the app as well as the
intended audience should be clearly explained and a disclaimer should
be presented that the app is not meant to replace advice from human
professionals (Huckvale et al., 2012, 2015). This literature revealed
that a fifth way to assess the Auckland app could be to assess if the
app possessed the characteristics that scholars have argued are
present in apps that communicate effectively. This fifth research
question was therefore drafted:</p>
      <p>RQ5: Does the Auckland Civil Defence app exhibit principles of an app
that communicates effectively: (a) information attributed to qualified
author, (b) app purpose explained, audience identified, creator
identified, and disclaimer present, (c) privacy policy present,
(d) content creation and modification date present, (e)  claims
supported by evidence, (g) who paid for app identified, (h) external
influence that could affect objectivity of content identified, and
(i) contact information of app creators provided?</p>
</sec>
</sec>
<sec id="Ch1.S3">
  <title>Method</title>
      <p>Researchers seeking to evaluate apps have a variety of methods at
their disposal. These include conducting experiments, watching people
using an app in the real world, and surveying users to get their input
(Nayebi et al., 2012). In this study, this researcher decided that an
appropriate method for evaluating the Auckland Civil Defence app would
be one in which two individuals of similar educational and
professional backgrounds would utilize the Auckland Defence app and
afterwards, use a checklist to assess whether the app met the
characteristics outlined in the research questions. This checklist
approach mirrors the app assessment method utilized in past studies
that have evaluated apps such as Reynoldson et al. (2014), Bender
et al. (2013), and Huckvale et al. (2012, 2015).</p>
      <p>This checklist method has several limitations that were highlighted by
Alshehri and Freeman (2012) who explained that apps have several
characteristics that make it difficult to assess them. In everyday
life, apps are used in various scenarios (e.g., while running,
driving) by numerous people (e.g., technology experts, novices) using
numerous devices (e.g., expensive devices with newest software, older
devices) on different wireless networks (e.g. Wi-Fi, 4G, 3G,). These
differences make it hard to assess apps because in some cases, it is
not clear if the problem is with the app, the hardware of the mobile
device, the software running the mobile device, the wireless network,
or the person using the app. To address these potential pitfalls, this
researcher ensured that those evaluating the Auckland Civil Defence
app, in addition to being of similar educational and professional
background, would assess the app on identical devices using a common
wireless network while carrying out uniform tasks.</p>
      <p>The first step in crafting the app analysis method was to develop a checklist
for ascertaining whether the app: (a) had a simple and intuitive interface,
(b) incorporated multimedia, (c) had information that was relevant to the
learner, (d) offered just-in time delivery, and (e) offered offline access to
data. In order to craft such a checklist, this researcher had to figure out
how to measure whether the app was simple and intuitive. To find such
measures, studies of simplicity and intuitiveness in other digital media were
examined. What emerged was that an influential way of determining simplicity
and intuitiveness is Taylor and Kent's (2014) dialogic framework. These
scholars argued that simple and intuitive digital media have a guide or map
that tells users where to go in the media, a search box that can be used to
find out what is in the media, a navigation indicator showing the part of the
media the user is on, and a button or link that easily takes a user back to
the homepage of media. In addition, the media should lack animation that can
strain processing power and pages should load in less than 0.1 s (Kim
et al., 2014; Lee,
2014). These items were adopted as measures for assessing whether the
app was simple and intuitive. They were added to the other items
(incorporates multimedia; has information relevant to the learner;
offers just-in time delivery; offline access to information) to create
a checklist for assessing the app.</p>
      <p>A second checklist this researcher created was one for determining
whether the app matched the principles of an app that communicates
effectively. The principles utilized by Huckvale et al. (2012, 2015) to
assess asthma education apps were used to develop this
checklist. A third checklist was drafted to determine whether the app
addressed factors that can hinder people from taking steps to prepare
for disasters. Lindell and Perry's (2012) Protective Action Decision
Model, which details what factors can prevent people from preparing
for a disaster, was utilized to draft this checklist. A fourth
checklist was created to assess whether the app provided information
for people with communication, medical, independence, supervision, and
transportation needs as well as animal ownership needs. Kailes and
Enders' (2007) Function-Based Framework for Emergency Management and
Planning which describes how to best prepare individuals with special
needs for disasters was utilized to draft this checklist. These
checklists can be seen in Tables 1–4. Data collection occurred
1–10 February 2015. The app was downloaded to two identical smartphones
running the latest version of the Apple iOS operating system. The
smartphones did not contain any additional apps except those installed
at the factory. Two independent coders (both PhDs in mass
communication and employed as college professors at universities in
the United States) randomly selected four sections of the app and
analysed them using the above-mentioned checklists. This analysis was
conducted while the smartphones were connected to the same WIFI
network in the same room at a uniform time. After this initial
analysis, the coders met to discuss their findings. Initial
inter-rater agreement was 95 %. Discrepancies were resolved and
the coders reviewed remaining sections of the app. After completing
the analysis, ratings were compared and final ratings reached by
consensus.</p>
</sec>
<sec id="Ch1.S4">
  <title>Results</title>
      <p><?xmltex \hack{\noindent}?><italic>RQ1: Does the Auckland Civil Defence app address these factors that can hinder people from preparing for disasters: environmental cues, social context, source credibility, warning channels, warning content, past experience, lack of resources, and residency barriers?</italic></p><?xmltex \hack{\vspace*{0.5\baselineskip}}?>
      <p><?xmltex \hack{\noindent}?>Disaster preparedness messages are more likely to be effective if
people are shown cues in the environment illustrating the likelihood
of disasters occurring (Lindell and Perry, 2012). The app addressed
this factor with an activity section that showed the prevalence of
storms and floods in the Auckland area. This illustration of risks
Auckland faces can be viewed as an example of pointing to
environmental cues. Research has also shown that some people are
likely to prepare if they see peers preparing (Dash and Gladwin,
2007). The app addressed this factor by allowing users to connect with
friends via Facebook, SMS, or email. Through the app, users could see
preparedness steps their peers were taking and thus be encouraged to
also prepare.</p>
      <p>Because people vary in regards to whom they find credible and what
communication channel they utilize frequently, experts recommend that
preparedness messages be distributed by multiple sources on various
channels (Guion et al., 2007). The app provided a multiplicity
of sources from where to obtain preparedness information. For example,
the section on fire provided a link to the New Zealand Fire Service
and the section on pandemics provided a link to the Ministry of
Health. In addition, the app provided links on how to obtain
information through radio, SMS, email, phone, and other channels.</p>
      <p>Preparedness messages should address arguments people may have against
preparing as well as past experience individuals have had with
disasters (Sharma and Patt, 2012). The app addressed these factors by
presenting statistics. Parts of the app went into detail describing
past disasters that have affected Auckland and the likelihood of these
disasters occurring in the future. For example, the section on
aviation disasters explained that between 1996–1999, there were 40
aircraft accidents in the Auckland area. The section on cyclones noted
that every year, a cyclone comes within 500 <inline-formula><mml:math display="inline"><mml:mi mathvariant="normal">km</mml:mi></mml:math></inline-formula> of
Auckland. These statistics served to counter Aucklander's
preconceptions as well as past experience.</p>
      <p>The app did not address how low-income individuals can obtain
assistance in preparing for disaster. For example, information was not
provided on how the poor can obtain help purchasing items for
emergency kits. The app also did not address any concerns that
undocumented individuals may have about accessing disaster
preparedness help. Experts recommend that disaster managers make it
clear what disaster resources are available to the undocumented so
that these individuals are not apprehensive about seeking official
help (Santos-Hernandez, 2006). See Table 1 for complete findings in
regards to RQ1.</p>
      <p><?xmltex \hack{\noindent}?><italic>RQ2: Does the Auckland Civil Defence app provide preparedness information for people with communication, medical, independence, supervision, and transportation needs?</italic></p><?xmltex \hack{\vspace*{0.5\baselineskip}}?>
      <p><?xmltex \hack{\noindent}?>Kailes and Enders (2007) recommended that in order to
avoid marginalizing vulnerable individuals, disaster preparedness
education efforts should meet communication, medical, independence,
supervision, and transportation needs. The app's section on “people
with disabilities or special requirements” provided information for
people with hearing impairment, asthma/respiratory problems, sight
impairment, and physical disability/mobility impairment. The advice it
provided included organizing a support network of people who can
assist with evacuation, preparing a seven-day supply of essential
medication, and knowing where to access life sustaining equipment.</p>
      <p>Where the app was lacking was in providing information for those with
limited or no ability to speak, read or understand English. New
Zealand is a multilingual country. Tan (2009) explained that New
Zealand's government, recognizing that English fluency is a problem
for many, provides a Language Line service that provides translators
fluent in 44 languages to assist people seeking help from hospitals,
police, charities, and other vital services. The app did not indicate
how those not proficient in English could obtain information. See
Table 2 for complete findings in regards to this research question.</p><?xmltex \hack{\vspace*{1\baselineskip}}?>
      <p><?xmltex \hack{\noindent}?><italic>RQ3: Does the Auckland Civil Defence app provide preparedness information for animal owners?</italic></p><?xmltex \hack{\vspace*{0.5\baselineskip}}?>
      <p><?xmltex \hack{\noindent}?>For disaster preparedness efforts to be successful,
the needs of animal owners should be included in planning (Thompson,
2013). The app fulfilled these criteria in its special section on pets
and livestock. For pets, the app advised users to microchip pets,
prepare emergency food, and identify pet-friendly hotels. For
livestock, the app instructed owners to work with local authorities on
developing measures to secure livestock in a disaster.</p><?xmltex \hack{\vspace*{1\baselineskip}}?>
      <p><?xmltex \hack{\noindent}?><italic>RQ4: Does the Auckland Civil Defence app exhibit principles of an app that excels as a platform for learning: (a) simple and intuitive interface, (b) incorporate multimedia, (c) information that is contextual and relevant to the learner, (d) just-in time delivery, and (e) offline access to data?</italic></p><?xmltex \hack{\vspace*{0.5\baselineskip}}?>
      <p><?xmltex \hack{\noindent}?>Taylor and Kent (2014) argued that digital platforms
that excel as platforms for learning are characterized by a simple and
intuitive interface. Aspects of the Auckland app that exemplified this
characteristic include the presence of a navigation bar telling users
where to go on the app and absence of animation that can strain
processor power. The app also met other criteria outlined by Taylor
and Kent such as incorporating images, providing contextual
information by allowing users to receive customized disaster alerts,
and providing just-in-time delivery of information by allowing the
delivery of notifications when a disaster was occurring. When offline,
the app did show information from the previous time it was used. The
app was lacking only in one area: it lacked a search box where a user
could   enter text to search to find specific items. See Table 3 for
complete findings in regards to this research question.</p><?xmltex \hack{\vspace*{1\baselineskip}}?>
      <p><?xmltex \hack{\noindent}?><italic>RQ5: Does the app exhibit principles of an app that communicates effectively: (a) information attributed to qualified author; (b) app purpose explained, audience identified, creator identified, and disclaimer present; (c) privacy policy present; (d) content creation and modification date present; (e) claims supported by evidence; (g) who paid for app identified; (h) external influence that could affect objectivity of content identified; and (i) contact information of app creators provided?</italic></p><?xmltex \hack{\vspace*{0.5\baselineskip}}?>
      <p><?xmltex \hack{\noindent}?>According to Huckvale et al. (2012, 2015), an app that
communicates effectively must provide full contact information of the
app's creators. The Auckland app met these criteria by providing the
email and phone contact information of the Auckland Defence
Council. Additional criteria that the app met include describing the
full purpose of the app and who created it. The app noted, for
example, that the Auckland Civil Defence commissioned the app,
a company called CloudM created the app software, and a company called
Ogilvy and Mather designed the app interface. The app also justified
claims by providing statistics, was transparent in revealing that it
was funded by the Auckland government and it contained a privacy
policy regarding user data. Pages of the app with detailed information
also had notes indicating when they were last updated.</p>
      <p>Where the app did not meet Huckvale et al.'s (2012, 2015) criteria was
in two areas. First, the information was not authoritative. At the
bottom of each update, the name, title, and contact information of the
person who wrote it were not provided. People, in many cases, find
information more credible if an actual author is listed (Cheever and
Rokkum, 2015). A second weakness was the lack of a disclaimer that the
app was not supposed to replace human advice. Apps, like most
technology, are prone to errors and especially in disaster settings,
can malfunction. Some apps include a disclaimer they are not supposed
to substitute advice from human experts (Boulos et al., 2014). See
Table 4 for complete findings in regards to this research question.</p>
</sec>
<sec id="Ch1.S5" sec-type="conclusions">
  <title>Discussion</title>
      <p>The findings contain valuable lessons for organizations around the
world seeking to use apps for disaster preparedness education. The
first lesson is that it is possible to create an app that addresses
factors that can hinder people from taking steps to address
disaster. Organizations can accomplish this by creating apps that show
disaster cues from the environment, allow users to connect with
friends or family who are preparing for disaster, provide information
from multiple sources, show users how to obtain information from
alternative channels, address arguments people may have against
preparing for disasters, and address past experiences users may have
had with disasters. Additional lessons from the Auckland app is that
it is possible to create an app that excels as a platform for
learning, communicates effectively, and provides information for
people with unique medical, independence, supervision, transportation,
and pet/livestock needs.</p>
      <p>The findings from this app analysis, however, also reveal several
things the Auckland app failed to achieve that other app creators
worldwide should be cognizant about. First, app creators should
recognize the need to provide information on how low-income people can
address challenges to preparing for disaster. Telling people to
prepare but not providing them information on how they can address
lack of resources (e.g., where to get help in stockpiling food if you
lack money) is problematic. In Auckland, an estimated 70 food banks
serve the underprivileged (Jackson, 2013). These statistics mirror
other cities in emerging and developed countries where poverty is
a part of urban life for many. Disaster preparedness app creators can
make their apps stronger by including information on how the
underprivileged can get help with disaster preparedness.</p>
      <p>Second, app creators should also be aware of the need to provide
information to people who do not speak, read, or understand the local
language. In Auckland, police, hospital and other emergency services
utilize a Language Line service to provide assistance to the 44
different nationalities in New Zealand that are not fluent in English
(Tan, 2009). The Auckland app could have been stronger if it had
contained information on how individuals not fluent in English could
access this service. In other regions, app designers should factor how
they will address the linguistic diversity among users.</p>
      <p>App creators should also address challenges undocumented migrants face
preparing for disasters. New Zealand, like many nations, has a growing
population of migrants. Glass (2013) noted that some of these
individuals in New Zealand, documented and undocumented, live in fear
of deportation and are often exploited by employers who pay them below
the minimum wage knowing that they are afraid of going to government
authorities to complain. App designers can make their apps stronger if
they include information clarifying to undocumented individuals what
preparedness services they can access regardless of immigration
status. Lastly, app creators should consider including a search box,
adding author names to articles, and adding a disclaimer that the
information in an app is not meant to replace human professional
advice. The presence of these elements can make apps more effective.</p>
      <p>This study has several limitations that future scholars need to
address in order to enhance the existing body of knowledge regarding
the use of apps as tools for teaching disaster preparedness. First,
this study lacks insight from users regarding what they think about
the app. Surveying and interviewing people who used the Auckland app
could have provided significant insight into whether the app is
succeeding in preparing Aucklanders for future disasters. In addition,
querying users could have shed light on whether Auckland Civil Defence
is using the app not simply to talk at people but to give them a voice
in shaping how disasters are managed. A second limitation of the study
is that it did not explore whether the app is entertaining or
engaging. This is something that can also be ascertained by
interviewing or surveying users. Smartphone users have a multiplicity
of apps to choose from and if an app is not engaging or entertaining,
it is likely they will not use it. Whether the Auckland app is
entertaining and engaging should be understood before other
organizations imitate the app's approach to preparedness
education. A third limitation of the study is that it did not explore
whether the app delivered information in short chunks appropriate for
mobile learning. The Auckland app has lots of information but is it
too much or just the right size for users? Surveys and interviews can
also shed light on this and give valuable details on exactly how much
text and images developers should put in preparedness apps.</p>
</sec>

      
      </body>
    <back><ref-list>
    <title>References</title>

      <ref id="bib1.bib1"><label>1</label><mixed-citation>
Alshehri, F. and Freeman, M.: Methods for usability evaluations of mobile
devices, in: 23rd Australian Conference on Information Systems, edited by:
Lamp, J. W., Deakin University, Geelong, 1–10, 2012.</mixed-citation></ref>
      <ref id="bib1.bib2"><label>2</label><mixed-citation>
Baker, L. and Cromier, L.:
Disasters and Vulnerable Populations: Evidence-Based Practice for the Helping Professions,
Springer, New York, 2014.</mixed-citation></ref>
      <ref id="bib1.bib3"><label>3</label><mixed-citation>
Blaikie, P., Cannon, T., Davis, I., and Wisner, B.:
At Risk II: Natural Hazards, People's Vulnerability and Disasters,
Routledge, London, 2014.</mixed-citation></ref>
      <ref id="bib1.bib4"><label>4</label><mixed-citation>Bender, J. L., Yue, R. Y. K., To, M. J., Deacken, L., and Jadad, A. R.: A lot
of action, but not in the right direction: systematic review and content
analysis of smartphone applications for the prevention, detection, and
management of cancer, J. Med. Internet Res., 15, e287,
doi:<ext-link xlink:href="http://dx.doi.org/10.2196/jmir.2661">10.2196/jmir.2661</ext-link>, 2013.</mixed-citation></ref>
      <ref id="bib1.bib5"><label>5</label><mixed-citation>
Bolin, B.: Race, class, ethnicity, and disaster vulnerability, in: Handbook
of Disaster Research, Springer, New York, 113–118, 2006.</mixed-citation></ref>
      <ref id="bib1.bib6"><label>6</label><mixed-citation>Boulos, M. N. K., Brewer, A. C., Karimkhani, C., Buller, D. B., and
Dellavalle, R. P.: Mobile medical and health apps: state of the art,
concerns, regulatory control and certification, Online J. Public Health
Informatics, 5, 229, <ext-link xlink:href="http://dx.doi.org/10.5210/ojphi.v5i3.4814" ext-link-type="DOI">10.5210/ojphi.v5i3.4814</ext-link>, 2014.</mixed-citation></ref>
      <ref id="bib1.bib7"><label>7</label><mixed-citation>
Cheever, N. A. and Rokkum, J.: Media literacy, in: The Wiley Blackwell
Handbook of Psychology, Technology and Society, Wiley-Blackwell, 56–73,
2015.</mixed-citation></ref>
      <ref id="bib1.bib8"><label>8</label><mixed-citation>Dash, N., and Gladwin, H.: Evacuation decision making and behavioral
responses: individual and household, Nat. Hazards Review, 8, 69–77,
doi:<ext-link xlink:href="http://dx.doi.org/10.1061/(ASCE)1527-6988(2007)8:3(69)">10.1061/(ASCE)1527-6988(2007)8:3(69)</ext-link>,
2007.</mixed-citation></ref>
      <ref id="bib1.bib9"><label>9</label><mixed-citation>Day, S.: Auckland the most unprepared for disaster, Stuff.co.nz, available
at:
<uri>http://www.stuff.co.nz/national/9219092/Auckland-the-most-unprepared-for-disaster</uri>,
2013.</mixed-citation></ref>
      <ref id="bib1.bib10"><label>10</label><mixed-citation>Dillard, A.: Mobile instructional design principles for adult learners,
available at: <uri>https://scholarsbank.uoregon.edu/xmlui/handle/1794/12253</uri>,
2012.</mixed-citation></ref>
      <ref id="bib1.bib11"><label>11</label><mixed-citation>
Drabek, T. E.: Understanding disaster-warning responses, Soc. Sci J., 36,
515–523, 1999.</mixed-citation></ref>
      <ref id="bib1.bib12"><label>12</label><mixed-citation>
El-Hussein, M. and Cronje, J.: Defining mobile learning in the higher
education landscape, Educational Technology &amp; Society, 13, 12–21, 2010.</mixed-citation></ref>
      <ref id="bib1.bib13"><label>13</label><mixed-citation>
Elias, T.: Universal instructional design principles for mobile learning,
International Review of Research in Open and Distance Learning (IRRODL), 12,
143–156, 2011.</mixed-citation></ref>
      <ref id="bib1.bib14"><label>14</label><mixed-citation>Glass, L.: Concern for migrant workers in NZ, available at:
<uri>http://tvnz.co.nz/national-news/concern-migrant-workers-in-nz-5434608</uri>,
2013.</mixed-citation></ref>
      <ref id="bib1.bib15"><label>15</label><mixed-citation>Gu, X., Gu, F., and Laffey, J.:
Designing a mobile system for lifelong learning on the move,
J. Comput. Assist. Lear.,
27, 204–215,
doi:<ext-link xlink:href="http://dx.doi.org/10.1111/j.1365-2729.2010.00391.x">10.1111/j.1365-2729.2010.00391.x</ext-link>, 2011.</mixed-citation></ref>
      <ref id="bib1.bib16"><label>16</label><mixed-citation>Guion, D. T., Scammon, D. L., and Borders, A.:
Weathering the storm: a social marketing perspective on disaster preparedness and response with lessons from Hurricane Katrina,
J. Public Policy Mark.,
26, 20–32,
doi:<ext-link xlink:href="http://dx.doi.org/10.1509/jppm.26.1.20">10.1509/jppm.26.1.20</ext-link>, 2007.</mixed-citation></ref>
      <ref id="bib1.bib17"><label>17</label><mixed-citation>Harrison, R., Flood, D., and Duce, D.: Usability of mobile applications:
literature review and rationale for a new usability model, Journal of
Interaction Science, 1, 1–16, <ext-link xlink:href="http://dx.doi.org/10.1186/2194-0827-1-1" ext-link-type="DOI">10.1186/2194-0827-1-1</ext-link>, 2013</mixed-citation></ref>
      <ref id="bib1.bib18"><label>18</label><mixed-citation>Heath, S. E.:
Human and pet-related risk factors for household evacuation failure during a natural disaster,
Am. J. Epidemiol.,
153, 659–665,
doi:<ext-link xlink:href="http://dx.doi.org/10.1111/j.1365-2729.2010.00391.x.">10.1111/j.1365-2729.2010.00391.x.</ext-link>, 2001.</mixed-citation></ref>
      <ref id="bib1.bib19"><label>19</label><mixed-citation>Huckvale, K., Car, M., Morrison, C., and Car, J.:
Apps for asthma self-management: a systematic assessment of content and tools,
BMC Med.,
10, 144,
doi:<ext-link xlink:href="http://dx.doi.org/10.1186/1741-7015-10-144">10.1186/1741-7015-10-144</ext-link>, 2012.</mixed-citation></ref>
      <ref id="bib1.bib20"><label>20</label><mixed-citation>Huckvale, K., Morrison, C., Ouyang, J., Ghaghda, A., and Car, J.: The
evolution of mobile apps for asthma: an updated systematic assessment of
content and tools, BMC Med., 13, 58, <ext-link xlink:href="http://dx.doi.org/10.1186/s12916-015-0303-x" ext-link-type="DOI">10.1186/s12916-015-0303-x</ext-link>, 2015.</mixed-citation></ref>
      <ref id="bib1.bib21"><label>21</label><mixed-citation>Jackson, W.: Food bank partners, Stuff.co.nz, available at:
<uri>http://www.stuff.co.nz/auckland/local-news/local-blogs/willie-jackson/9481025/Food-bank-partners</uri>,
2013.</mixed-citation></ref>
      <ref id="bib1.bib22"><label>22</label><mixed-citation>James, X., Hawkins, A., and Rowel, R.:
An assessment of the cultural appropriateness of emergency preparedness communication for low income minorities,
J. Homel. Secur. Emerg.,
4, 144,
doi:<ext-link xlink:href="http://dx.doi.org/10.2202/1547-7355.1266">10.2202/1547-7355.1266</ext-link>, 2007.</mixed-citation></ref>
      <ref id="bib1.bib23"><label>23</label><mixed-citation>Kailes, J. I. and Enders, A.: Moving beyond “special needs”:
a function-based framework for emergency management and planning, Journal of
Disability Policy Studies, 17, 230–237,
doi:<ext-link xlink:href="http://dx.doi.org/10.1177/10442073070170040601">10.1177/10442073070170040601</ext-link>,
2007.</mixed-citation></ref>
      <ref id="bib1.bib24"><label>24</label><mixed-citation>Kim, D., Chun, H., Kwak, Y., and Nam, Y.: The employment of dialogic
principles in website, facebook, and twitter platforms of environmental
nonprofit organizations, Soc. Sci. Comput. Rev., 31, 590–605,
<ext-link xlink:href="http://dx.doi.org/10.1177/0894439314525752" ext-link-type="DOI">10.1177/0894439314525752</ext-link>, 2014.</mixed-citation></ref>
      <ref id="bib1.bib25"><label>25</label><mixed-citation>
Kukulska-Hume, A. and Traxler, J.: Design principles for mobile learning, in:
Rethinking Pedagogy for a Digital Age: Designing for 21st Century Learning,
Routledge, London, 244–257, 2013.</mixed-citation></ref>
      <ref id="bib1.bib26"><label>26</label><mixed-citation>Lee, S. T.: A user approach to dialogic theory in a Facebook campaign on love
and marriage, Media Cult. Soc., 36, 437–455,
doi:<ext-link xlink:href="http://dx.doi.org/10.1177/0163443714523809">10.1177/0163443714523809</ext-link>,
2014.</mixed-citation></ref>
      <ref id="bib1.bib27"><label>27</label><mixed-citation>
Lindell, M. K. and Perry, R. W.: Communicating Environmental Risk in
Multi-Ethnic Communities, Sage, Thousand Oaks, California, 2004.</mixed-citation></ref>
      <ref id="bib1.bib28"><label>28</label><mixed-citation>Lindell, M. K. and Perry, R. W.: The protective action decision model:
theoretical modifications and additional evidence, Risk Anal., 3, 616–632,
doi:<ext-link xlink:href="http://dx.doi.org/10.1111/j.1539-6924.2011.01647.x">10.1111/j.1539-6924.2011.01647.x</ext-link>,
2012.</mixed-citation></ref>
      <ref id="bib1.bib29"><label>29</label><mixed-citation>
Lundgren, R. E. and McMakin, A. H.:
Risk Communication: a Handbook for Communicating Environmental, Safety, and Health Risk,
Wiley, Hoboken, New Jersey, 2013.</mixed-citation></ref>
      <ref id="bib1.bib30"><label>30</label><mixed-citation>Nayebi, F., Desharnais, J., and Abran, A.: The state of the art of mobile
application usability evaluation, in: Electrical &amp; Computer Engineering
(CCECE), 2012 25th IEEE Canadian Conference on, 29 April–2 May 2012,
Montreal, QC, IEEE, 1–4, <ext-link xlink:href="http://dx.doi.org/10.1109/CCECE.2012.6334930" ext-link-type="DOI">10.1109/CCECE.2012.6334930</ext-link>, 2012.</mixed-citation></ref>
      <ref id="bib1.bib31"><label>31</label><mixed-citation>
Park, Y.: A pedagogical framework for mobile learning: categorizing
educational applications of mobile technologies into four types,
International Review of Research in Open and Distance Learning (IRRODL), 12,
78–102, 2011.</mixed-citation></ref>
      <ref id="bib1.bib32"><label>32</label><mixed-citation>Patterson, O., Weil, F., and Patel, K.:
The role of community in disaster response: conceptual models,
Popul. Res. Policy Rev..,
29, 127–141,
doi:<ext-link xlink:href="http://dx.doi.org/10.1007/s11113-009-9133-x">10.1007/s11113-009-9133-x</ext-link>, 2010.</mixed-citation></ref>
      <ref id="bib1.bib33"><label>33</label><mixed-citation>Reynoldson, C., Stones, C., Allsop, M., Gardner, P., Bennett, M. I., Closs, S. J., and Knapp, P.:
Assessing the quality and usability of smartphone apps for pain self-management,
Pain Med.,
15, 898–909,
doi:<ext-link xlink:href="http://dx.doi.org/10.1111/pme.12327">10.1111/pme.12327</ext-link>, 2014.</mixed-citation></ref>
      <ref id="bib1.bib34"><label>34</label><mixed-citation>
Rooney, C. and White, G. W.: Consumer perspective: narrative analysis of
a disaster preparedness and emergency response survey from persons with
mobility impairments, Journal of Disability Policy Studies, 17, 206–215,
2007.</mixed-citation></ref>
      <ref id="bib1.bib35"><label>35</label><mixed-citation>
Santos-Hernandez, J. M.:
“Losing Everything:” Undocumented Latino Workers and Hurricane Katrina, Boulder,
Institute of Behavioral Science, University of Colorado at Boulder, CO, 2006.</mixed-citation></ref>
      <ref id="bib1.bib36"><label>36</label><mixed-citation>Sattler, D. N., Kaiser, C. F., and Hittner, J. B.: Disaster preparedness:
relationships among prior experience, personal characteristics, and distress,
J. Appl Soc. Psychol., 30, 1396–1420,
<ext-link xlink:href="http://dx.doi.org/10.1111/j.1559-1816.2000.tb02527.x" ext-link-type="DOI">10.1111/j.1559-1816.2000.tb02527.x</ext-link>, 2000.</mixed-citation></ref>
      <ref id="bib1.bib37"><label>37</label><mixed-citation>Sharma, U. and Patt, A.:
Disaster warning response: the effects of different types of personal experience,
Nat. Hazards,
60, 409–423,
doi:<ext-link xlink:href="http://dx.doi.org/10.1007/s11069-011-0023-2">10.1007/s11069-011-0023-2</ext-link>, 2012.</mixed-citation></ref>
      <ref id="bib1.bib38"><label>38</label><mixed-citation>
Sorensen, J. and Sorensen, B.: Community processes: warning and evacuation,
in: Handbook of Disaster Research, Springer, New York, 183–199, 2006.</mixed-citation></ref>
      <ref id="bib1.bib39"><label>39</label><mixed-citation>Tan, L.: Police say welcome in 14 languages, available at:
<uri>http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&amp;objectid=10608392</uri>,
2009.</mixed-citation></ref>
      <ref id="bib1.bib40"><label>40</label><mixed-citation>Taylor, M. and Kent, M. L.: Dialogic engagement: clarifying foundational
concepts, J. Public Relat. Res., 26, 384–398,
doi:<ext-link xlink:href="http://dx.doi.org/10.1080/1062726X.2014.956106">10.1080/1062726X.2014.956106</ext-link>,
2014.</mixed-citation></ref>
      <ref id="bib1.bib41"><label>41</label><mixed-citation>
Thompson, K.: Save me, save my dog: increasing natural disaster preparedness
and survival by addressing human–animal relationships, Australian Journal of
Communication, 40, 123–136, 2013.</mixed-citation></ref>
      <ref id="bib1.bib42"><label>42</label><mixed-citation>
Wang, M. and Shen, R.: Message design for mobile learning: learning theories,
human cognition and design principles, Brit. J. Educ. Technol., 43, 561–575,
2012.</mixed-citation></ref>
      <ref id="bib1.bib43"><label>43</label><mixed-citation>Wang, R., Wiesemes, R., and Gibbons, C.: Developing digital fluency through
ubiquitous mobile devices: findings from a small-scale study, Comput. Educ.,
58, 570–578, <ext-link xlink:href="http://dx.doi.org/10.1016/j.compedu.2011.04.013" ext-link-type="DOI">10.1016/j.compedu.2011.04.013</ext-link>, 2012.</mixed-citation></ref>
      <ref id="bib1.bib44"><label>44</label><mixed-citation>Wilson, S. N. and Tiefenbacher, J. P.: The barriers impeding precautionary
behaviours by undocumented immigrants in emergencies: the hurricane ike
experience in Houston, Texas, USA, Environmental Hazards, 11, 194–212,
doi:<ext-link xlink:href="http://dx.doi.org/10.1080/17477891.2011.649711">10.1080/17477891.2011.649711</ext-link>,
2012.</mixed-citation></ref>

  </ref-list><app-group content-type="float"><app><title/>

<?xmltex \floatpos{t}?><table-wrap id="App1.Ch1.T1"><caption><p>Does  app  address  factors  that  can  hinder  preparedness?</p></caption><oasis:table frame="topbot"><?xmltex \begin{scaleboxenv}{.65}[.65]?><oasis:tgroup cols="4">
     <oasis:colspec colnum="1" colname="col1" align="justify" colwidth="85.358268pt"/>
     <oasis:colspec colnum="2" colname="col2" align="justify" colwidth="142.26378pt"/>
     <oasis:colspec colnum="3" colname="col3" align="justify" colwidth="71.13189pt"/>
     <oasis:colspec colnum="4" colname="col4" align="justify" colwidth="284.527559pt"/>
     <oasis:thead>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Factor</oasis:entry>  
         <oasis:entry colname="col2">App characteristic</oasis:entry>  
         <oasis:entry colname="col3">Auckland app<?xmltex \hack{\hfill\break}?>exhibits<?xmltex \hack{\hfill\break}?>characteristic?</oasis:entry>  
         <oasis:entry colname="col4">Example from app</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Environmental cues</oasis:entry>  
         <oasis:entry colname="col2">Shows cues from the<?xmltex \hack{\hfill\break}?>environment to encourage<?xmltex \hack{\hfill\break}?>preparedness.</oasis:entry>  
         <oasis:entry colname="col3">X</oasis:entry>  
         <oasis:entry colname="col4">“Heavy  rainfall  is  causing  in  southeastern  parts  of  Auckland  and<?xmltex \hack{\hfill\break}?>metservice  expects  rain  to  continue  until  at  least  4 p.m.”</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Social context</oasis:entry>  
         <oasis:entry colname="col2">Allows users to connect with<?xmltex \hack{\hfill\break}?>others and see what<?xmltex \hack{\hfill\break}?>preparedness steps they are<?xmltex \hack{\hfill\break}?>taking.</oasis:entry>  
         <oasis:entry colname="col3">X</oasis:entry>  
         <oasis:entry colname="col4">“You  will  be  able  to  check  your  connections'  progress  with  their<?xmltex \hack{\hfill\break}?>household  emergency  plan,  through  the  plan  icons.”</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Source  credibility</oasis:entry>  
         <oasis:entry colname="col2">Provides  preparedness<?xmltex \hack{\hfill\break}?>information  from  multiple<?xmltex \hack{\hfill\break}?>sources.</oasis:entry>  
         <oasis:entry colname="col3">X</oasis:entry>  
         <oasis:entry colname="col4">The  16  sections  on  disasters  Auckland  faces    provide  links  to<?xmltex \hack{\hfill\break}?>organizations  such as  Maritime  New  Zealand,  Ministry  of<?xmltex \hack{\hfill\break}?>Health, and Auckland  Engineering Lifelines  Groups  where   users<?xmltex \hack{\hfill\break}?>can  learn  more  information.</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Warning channels</oasis:entry>  
         <oasis:entry colname="col2">Shows users how to obtain<?xmltex \hack{\hfill\break}?>preparedness information<?xmltex \hack{\hfill\break}?>from alternative channels.</oasis:entry>  
         <oasis:entry colname="col3">X</oasis:entry>  
         <oasis:entry colname="col4">“Find  about  local  hazards  and  your  community's  response  plan<?xmltex \hack{\hfill\break}?>by  talking  to  Auckland  Council  Phone  08800 22 22 00 or<?xmltex \hack{\hfill\break}?>09 301 01  Email.”</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Warning content</oasis:entry>  
         <oasis:entry colname="col2">Addresses arguments people<?xmltex \hack{\hfill\break}?>may have against preparing for<?xmltex \hack{\hfill\break}?>disasters</oasis:entry>  
         <oasis:entry colname="col3">X</oasis:entry>  
         <oasis:entry colname="col4">“Auckland's  never  had  a major  shipping  accident,  but  it's  always<?xmltex \hack{\hfill\break}?>a risk  because  we're  surrounded  by  water.”</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Past experience</oasis:entry>  
         <oasis:entry colname="col2">Addresses past experiences<?xmltex \hack{\hfill\break}?>users may have had with<?xmltex \hack{\hfill\break}?>disaster</oasis:entry>  
         <oasis:entry colname="col3">X</oasis:entry>  
         <oasis:entry colname="col4">“Flood  are  Auckland's  most  common  hazards.    Fast-flowing  water<?xmltex \hack{\hfill\break}?>can  knock  you  over  even  if  very  shallow.”</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Lack of resource</oasis:entry>  
         <oasis:entry colname="col2">Address challenges low-income<?xmltex \hack{\hfill\break}?>people may face preparing for<?xmltex \hack{\hfill\break}?>disaster</oasis:entry>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Residency  barriers</oasis:entry>  
         <oasis:entry colname="col2">Addresses  challenges<?xmltex \hack{\hfill\break}?>undocumented  migrants  face<?xmltex \hack{\hfill\break}?>about  preparing  for  disaster</oasis:entry>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup><?xmltex \end{scaleboxenv}?></oasis:table></table-wrap>

<?xmltex \floatpos{t}?><table-wrap id="App1.Ch1.T2"><caption><p>Does  app  provide  preparedness  information  for  people  with  communication,  medical,  independence,  supervision,  transportation,  and  pet-livestock  needs?</p></caption><oasis:table frame="topbot"><?xmltex \begin{scaleboxenv}{.65}[.65]?><oasis:tgroup cols="4">
     <oasis:colspec colnum="1" colname="col1" align="justify" colwidth="85.358268pt"/>
     <oasis:colspec colnum="2" colname="col2" align="justify" colwidth="142.26378pt"/>
     <oasis:colspec colnum="3" colname="col3" align="justify" colwidth="71.13189pt"/>
     <oasis:colspec colnum="4" colname="col4" align="justify" colwidth="284.527559pt"/>
     <oasis:thead>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Function</oasis:entry>  
         <oasis:entry colname="col2">App  characteristic</oasis:entry>  
         <oasis:entry colname="col3">Auckland  app<?xmltex \hack{\hfill\break}?>exhibits<?xmltex \hack{\hfill\break}?>characteristic?</oasis:entry>  
         <oasis:entry colname="col4">Example  from  app</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">Communication</oasis:entry>  
         <oasis:entry colname="col2">Provides information for those<?xmltex \hack{\hfill\break}?>with limited or no ability to<?xmltex \hack{\hfill\break}?>speak, read or understand<?xmltex \hack{\hfill\break}?>English.</oasis:entry>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">Provides information for those<?xmltex \hack{\hfill\break}?>with reduced or no ability to<?xmltex \hack{\hfill\break}?>hear, see, or speak.</oasis:entry>  
         <oasis:entry colname="col3">X</oasis:entry>  
         <oasis:entry colname="col4">“Ensure  your  gateway  kit  contains  a writing  pad,  pencils,  and<?xmltex \hack{\hfill\break}?>a torch,  so  you  can  communicate  with  others.”</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Medical</oasis:entry>  
         <oasis:entry colname="col2">Provides information for those<?xmltex \hack{\hfill\break}?>with chronic conditions, on<?xmltex \hack{\hfill\break}?>special medications, on<?xmltex \hack{\hfill\break}?>dialysis, oxygen etc.</oasis:entry>  
         <oasis:entry colname="col3">X</oasis:entry>  
         <oasis:entry colname="col4">“Make  sure  you  have  dusts  masks  in  your  survival  kit  and  gateway<?xmltex \hack{\hfill\break}?>kit  and  sufficient  medicines  for  at  least  seven  days.”</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Independence</oasis:entry>  
         <oasis:entry colname="col2">Provides information for those<?xmltex \hack{\hfill\break}?>who utilize, wheelchairs, canes,<?xmltex \hack{\hfill\break}?>hearing aids, service animals<?xmltex \hack{\hfill\break}?>etc.</oasis:entry>  
         <oasis:entry colname="col3">X</oasis:entry>  
         <oasis:entry colname="col4">“Keep  extra  canes  and  in  the  workplace  even  if  you  use  a guide<?xmltex \hack{\hfill\break}?>dog.”</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Supervision</oasis:entry>  
         <oasis:entry colname="col2">Provides  information  for  those<?xmltex \hack{\hfill\break}?>with dementia, Alzheimer's  etc.</oasis:entry>  
         <oasis:entry colname="col3">X</oasis:entry>  
         <oasis:entry colname="col4">“Plan  now  if  you  or  a family  member  has  a disability  or  special<?xmltex \hack{\hfill\break}?>need.    Consider  having  at  least  7 days  supply  of  your  essential<?xmltex \hack{\hfill\break}?>medications and  a way  to  store  those  that  need  refrigeration.”</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Transportation</oasis:entry>  
         <oasis:entry colname="col2">Provides information for those<?xmltex \hack{\hfill\break}?>with limited transportation<?xmltex \hack{\hfill\break}?>options due to age poverty,<?xmltex \hack{\hfill\break}?>legal restrictions against driving etc.</oasis:entry>  
         <oasis:entry colname="col3">X</oasis:entry>  
         <oasis:entry colname="col4">“If  you  or  a family  member  has  a physical  disability  that  affects<?xmltex \hack{\hfill\break}?>movement,  ensure  your  gateway  kit  contains  what  you  need.”</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Animal  needs</oasis:entry>  
         <oasis:entry colname="col2">Provides  information  for  pet  and<?xmltex \hack{\hfill\break}?>livestock  owner.</oasis:entry>  
         <oasis:entry colname="col3">X</oasis:entry>  
         <oasis:entry colname="col4">“Keep  a list  of  “pet-friendly”  hotels  and  motels.”</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup><?xmltex \end{scaleboxenv}?></oasis:table></table-wrap>

<?xmltex \floatpos{t}?><table-wrap id="App1.Ch1.T3"><caption><p>Does app excel as platform for learning?</p></caption><oasis:table frame="topbot"><?xmltex \begin{scaleboxenv}{.75}[.75]?><oasis:tgroup cols="3">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="left"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry colname="col1">Design characteristic</oasis:entry>  
         <oasis:entry colname="col2">Auckland app</oasis:entry>  
         <oasis:entry colname="col3">Example  from  app</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">characteristic?</oasis:entry>  
         <oasis:entry colname="col3"/>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">Map telling users where to go</oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">Four  buttons  indicating  main  app  sections</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Search box</oasis:entry>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3"/>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Navigation indicator on app page</oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">Bottom  and  right  side  of  app  has  navigation  adds</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Button that easily takes user back to main page.</oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">Home  button  brought  user  to  app  home</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Absence of animation that can strain processing power.</oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">No  animation</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Loads in less than 0.1 s</oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">Loaded  in 0.1 s</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Incorporates multimedia</oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">Incorporated  images</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Relevant information</oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">Information  shown  based  on  user's  location</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Offers just-in time delivery</oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">Real  time  notifications  about  disaster</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">App can be used offline</oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">When  offline,  app  showed  information  from</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3">when  it  was  last  used</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup><?xmltex \end{scaleboxenv}?></oasis:table></table-wrap>

<?xmltex \floatpos{t}?><table-wrap id="App1.Ch1.T4"><caption><p>Does  app  communicate  effectively?</p></caption><oasis:table frame="topbot"><?xmltex \begin{scaleboxenv}{.65}[.65]?><oasis:tgroup cols="3">
     <oasis:colspec colnum="1" colname="col1" align="justify" colwidth="284.527559pt"/>
     <oasis:colspec colnum="2" colname="col2" align="justify" colwidth="71.13189pt"/>
     <oasis:colspec colnum="3" colname="col3" align="justify" colwidth="227.622047pt"/>
     <oasis:thead>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Design  characteristic</oasis:entry>  
         <oasis:entry colname="col2">Auckland  app<?xmltex \hack{\hfill\break}?>exhibits<?xmltex \hack{\hfill\break}?>characteristic?</oasis:entry>  
         <oasis:entry colname="col3">Example  from  app</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">Information  is  attributed  to  author  whose  qualifications  are<?xmltex \hack{\hfill\break}?>mentioned.<?xmltex \hack{\vspace*{6pt}}?></oasis:entry>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3"/>
       <?xmltex \interline{[6pt]}?></oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Explaining  purpose,  intended  audience,  and  organization  that<?xmltex \hack{\hfill\break}?>created  it.</oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">“This  app  is  brought  to  you  by  Auckland  Civil<?xmltex \hack{\hfill\break}?>Defence  to  help  you  prepare  for  emergencies.”</oasis:entry>
       <?xmltex \interline{[24pt]}?></oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Disclaimer  that  app  that  it  is  not  meant  to  replace  human<?xmltex \hack{\hfill\break}?>professional  advice.<?xmltex \hack{\vspace*{6pt}}?></oasis:entry>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3"/>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Privacy  policy  regarding  user  information.</oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">“We  also  may  collect  personally  identifiable<?xmltex \hack{\hfill\break}?>information  that  you  provide  use,  such  as  your<?xmltex \hack{\hfill\break}?>name,  address,  phone  number,  or  email  address.”<?xmltex \hack{\vspace*{6pt}}?></oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Content  creation  and  last  modification  date.</oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">Pages  with  detailed  information  had  notes  indicating<?xmltex \hack{\hfill\break}?>when  they  were  last  updated.<?xmltex \hack{\vspace*{6pt}}?></oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Claims  on  app  supported  by  evidence.</oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">“In  the  average  year,  one  Tropical  cyclone  comes<?xmltex \hack{\hfill\break}?>within  500 <inline-formula><mml:math display="inline"><mml:mi mathvariant="normal">km</mml:mi></mml:math></inline-formula>  of  New  Zealand.”<?xmltex \hack{\vspace*{6pt}}?></oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Who  paid  for  app  identified.<?xmltex \hack{\vspace*{6pt}}?></oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">Auckland  Civil  Defence  logo  on  each  page.</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">External  influences  that  could  affect  the  objectivity  of  content<?xmltex \hack{\hfill\break}?>revealed.<?xmltex \hack{\vspace*{6pt}}?></oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">Auckland  Civil  Defence  logo  on  each  page.</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">App  creator  contact  details  provided.</oasis:entry>  
         <oasis:entry colname="col2">X</oasis:entry>  
         <oasis:entry colname="col3">The  app  had  a “Send  us  your  feedback” tab.</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup><?xmltex \end{scaleboxenv}?></oasis:table></table-wrap>

      <fig id="App1.Ch1.F1"><caption><p>Welcome screens of the app.</p></caption>
      <?xmltex \igopts{width=284.527559pt}?><graphic xlink:href="https://nhess.copernicus.org/preprints/3/4555/2015/nhessd-3-4555-2015-f01.pdf"/>

    </fig>

      <fig id="App1.Ch1.F2"><caption><p>The home page of the app.</p></caption>
      <?xmltex \igopts{width=369.885827pt}?><graphic xlink:href="https://nhess.copernicus.org/preprints/3/4555/2015/nhessd-3-4555-2015-f02.pdf"/>

    </fig>

      <fig id="App1.Ch1.F3"><caption><p>The plan page of the app.</p></caption>
      <?xmltex \igopts{width=369.885827pt}?><graphic xlink:href="https://nhess.copernicus.org/preprints/3/4555/2015/nhessd-3-4555-2015-f03.pdf"/>

    </fig>

      <fig id="App1.Ch1.F4"><caption><p>The info page of the app.</p></caption>
      <?xmltex \igopts{width=369.885827pt}?><graphic xlink:href="https://nhess.copernicus.org/preprints/3/4555/2015/nhessd-3-4555-2015-f04.pdf"/>

    </fig>

    </app></app-group></back>
    </article>
