<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">The Design and Development of Mobile Game to Promote Secure Smartphone Behaviour</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Anirudh</forename><surname>Ganesh</surname></persName>
							<email>anirudh.ganesh@dal.ca</email>
							<affiliation key="aff0">
								<orgName type="department">Faculty of Computer Science</orgName>
								<orgName type="institution">Dalhousie University</orgName>
								<address>
									<country key="CA">Canada</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Chinenye</forename><surname>Ndulue</surname></persName>
							<email>cndulue@dal.ca</email>
							<affiliation key="aff0">
								<orgName type="department">Faculty of Computer Science</orgName>
								<orgName type="institution">Dalhousie University</orgName>
								<address>
									<country key="CA">Canada</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Rita</forename><surname>Orji</surname></persName>
							<email>rita.orji@dal.ca</email>
							<affiliation key="aff0">
								<orgName type="department">Faculty of Computer Science</orgName>
								<orgName type="institution">Dalhousie University</orgName>
								<address>
									<country key="CA">Canada</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">The Design and Development of Mobile Game to Promote Secure Smartphone Behaviour</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">FC9FB828AE19686F975616AC570113FE</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-25T00:56+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Smartphone Security</term>
					<term>Persuasive Game</term>
					<term>Game Design Patterns</term>
					<term>Self-efficacy</term>
					<term>User Awareness</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Smartphones have evolved significantly in different ways over the years. Currently, Android and iOS dominate the market, followed by other operating systems. Along with the evolution of smartphones, malware, privacy, and other security issues have evolved along with it. Therefore, there is a need to develop interventions to educate and motivate users towards safe and privacysensitive smartphone usage behaviour while engaging with the rapidly changing features of these devices. In this paper, we introduce the design and development of a mobile persuasive game called "PermaRun" to improve users' knowledge, build self-efficacy and create awareness about privacy-sensitive and securityconscious behaviours, especially as it regards to user control and handling of Android permissions and other secure smartphone behaviour. We implement nine persuasive strategies to keep the users motivated and six game design patterns to make the game engaging and more interesting for the player.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>Humans are the weakest link in the chain of cybersecurity <ref type="bibr" target="#b0">[1]</ref> and have been ignored in the initial stages while cybersecurity was being studied. In this age of ubiquitous computing, smartphones have become an integral part of everybody's life. People take their smartphone wherever they go and use it for various day-to-day tasks, and most of the time, their personal data is involved. Over the years, there have been countless instances where the users' personal information has been compromised without their knowledge through Android apps <ref type="bibr" target="#b1">[2,</ref><ref type="bibr" target="#b2">3]</ref>. In the recent past, various security flaws were found and patched up <ref type="bibr">[4]</ref>. In recent times, Smartphones have evolved in various ways and, uniformity in design (both hardware and software) can be seen in most phones. With uniformity, the common problems were solved, yet the issue of privacy and security seemed to have evolved along with smartphone advancements.</p><p>To address these security concerns, smartphone operating systems have employed various techniques to protect user data. For example, the Android Operating System (OS) protects user data through the usage of App Permissions <ref type="bibr">[5]</ref>, which can be granted or denied by the users. There are two kinds of app permissions: install-time permissions and runtime permissions <ref type="bibr">[5,</ref><ref type="bibr">6]</ref>. Install-time permissions are granted automatically Ninth International Workshop on Behavior Change Support Systems (BCSS 2021):</p><p>The Design and Development of Mobile Game to Promote Secure Smartphone Behaviour during the installation of an application and further split into two categories, namely normal permissions, and signature permissions. Normal permissions present minimal risk to the users' privacy. Examples of normal permissions include fetching the current date and time, accessing the phone's vibrator. Signature permissions allow apps signed with the same certificate <ref type="bibr">[7]</ref> to share permissions to avoid requesting the permission again. Signature permissions are commonly used when the developers declare their own permissions and want to use it in another app developed by them. Examples of signature permissions are fetching the battery status, auto-filling of forms, clearing the app's cache and so on.</p><p>Runtime permissions, also called dangerous permissions, require users' decisions since they deal with accessing sensitive data or users' personal data <ref type="bibr">[5,</ref><ref type="bibr">6]</ref>. It is the app developers' responsibility to request a specific permission for a specific functionality of an app, while users decide whether to accept or deny these requests, based on their judgements. To convince users to allow these permissions, developers may show the users why a specific permission is required <ref type="bibr" target="#b3">[8]</ref>. Unfortunately, users often make the wrong decisions out of impulse <ref type="bibr" target="#b4">[9]</ref>, ignorance of what granting the permission entails, and do not always check the permissions and the app's functionality <ref type="bibr" target="#b5">[10,</ref><ref type="bibr" target="#b6">11]</ref>. More recent user studies <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b7">[12]</ref><ref type="bibr" target="#b8">[13]</ref><ref type="bibr" target="#b9">[14]</ref> show that user awareness about smartphone security and possible privacy implications are limited, and only a few people follow secure smartphone behaviours. Secure smartphone behaviour refers to the general etiquettes that are to be followed while using a smartphone to stay safe and protect oneself from malware and other kinds of security threats <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b6">[11]</ref><ref type="bibr" target="#b7">[12]</ref><ref type="bibr" target="#b8">[13]</ref><ref type="bibr" target="#b9">[14]</ref><ref type="bibr" target="#b10">[15]</ref><ref type="bibr" target="#b11">[16]</ref>. Bitton et al. <ref type="bibr" target="#b5">[10]</ref> monitored the users' smartphone behaviour using an Android app and compared it with the data that was monitored over the network and self-reported responses from the users. It was evident that the users' self-reported behaviour was different and inefficient from what was observed over the network and the mobile app. Although the users thought they were aware of what they were doing, from the data collected by the mobile app, it turned out to be the opposite. The users were giving away personal information to spam pop-ups and installed apps that required permissions that were not essential for their functionality. Zhou et al. <ref type="bibr" target="#b12">[17]</ref> conducted a longitudinal study among 192 university students in China and found that people use smartphones more securely when their awareness, selfefficacy and social support from others are high.</p><p>As evident from prior research, user awareness about smartphone security is limited and is an essential component to improve secure smartphone behaviour. Therefore, there is a need for interventions to promote smartphone security and privacy awareness among users and persuade them to be more security conscious and privacy-sensitive when using third-party apps on their devices. An interesting intervention for achieving this aim is the use of persuasive games. Persuasive games are interactive and gameful interventions that strategically employ persuasive strategies to motivate and promote changes in human behaviour. In recent times, there have been a lot of persuasive games across various domains <ref type="bibr" target="#b13">[18]</ref><ref type="bibr" target="#b14">[19]</ref><ref type="bibr" target="#b15">[20]</ref>. Although in the domain of cybersecurity, games that educate about smartphone security practices specifically are very sparse. Most of the existing games focus on other areas of cybersecurity, such as detecting phishing links and spam emails <ref type="bibr" target="#b16">[21]</ref><ref type="bibr" target="#b17">[22]</ref><ref type="bibr" target="#b18">[23]</ref><ref type="bibr" target="#b19">[24]</ref>. The Design and Development of Mobile Game to Promote Secure Smartphone Behaviour</p><p>In this paper, we present the design and development of a mobile persuasive game, called 'PermaRun', to promote secure smartphone behaviour among users and improve their awareness about Android permissions and other secure smartphone behaviour. We also present the implementation of nine persuasive strategies from the Persuasive System Design model (PSD) as proposed by Oinas-Kukkonen et al. <ref type="bibr" target="#b20">[25]</ref> and six game design patterns for 2D games as proposed by Khalifa et al. <ref type="bibr" target="#b21">[26]</ref>. We conclude with key takeaways from our game design, and we discuss our future work.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Background and Related Work</head><p>Games for cybersecurity have been around for a considerable amount of time. The most popular one being CyberCIEGE <ref type="bibr" target="#b22">[27]</ref>, a game that is meant for a classroom environment to educate students in a cybersecurity course. Digital Forensics Interactive (DFI) <ref type="bibr" target="#b23">[28]</ref>, a Role-Playing Game (RPG) game that aims to educate the player about the field of digital forensics where the player takes the role of a digital forensics expert and solves a case for a company. While playing the game, the user has the opportunity to learn about the various tools used for a particular task in the field of digital forensics. Even the board games category has covered cybersecurity. "[d0x3d!]" and "Control-Alt-Hack" <ref type="bibr" target="#b24">[29]</ref> are two such games that received positive feedback from school students and their parents for their role-playing and collaborative playing experience. Scholefield et al. <ref type="bibr" target="#b25">[30]</ref> designed a quiz-themed mobile game that taught users about password security. However, the game was missing feedback due to which users had to depend on playing the game repetitively to learn the correct answers. Most of the recent works have been concentrating on phishing and password security <ref type="bibr" target="#b17">[22]</ref><ref type="bibr" target="#b18">[23]</ref><ref type="bibr" target="#b19">[24]</ref><ref type="bibr" target="#b26">31]</ref>. Phisher Crush <ref type="bibr" target="#b17">[22]</ref> followed the style of a matchmaking game to educate players about identifying phishing links. The author ran a heuristic evaluation for playability and found that the users preferred immediate feedback rather than feedback towards the end of the game. Wen et al. <ref type="bibr" target="#b19">[24]</ref> designed a game called "What.Hack" that implemented situated learning to improve the self-efficacy of the users while playing the game. The players take the role of a phishing expert to identify phishing emails for a bank. They have a rule book which they can refer to learn how to identify phishing emails. Hacked time <ref type="bibr" target="#b26">[31]</ref> is a role-playing game where the player takes the role of a detective and helps an NPC to solve the case of password theft while learning about keeping passwords safe and secure along with other best practices. We were able to find only a handful of games for smartphone security. This might be because, in recent times, smartphones have undergone considerable evolution and, smartphone and associated security risks is a relatively new topic compared to other areas of cybersecurity. Zargham et al. <ref type="bibr" target="#b27">[32]</ref> designed a humorous, decision-based game to educate users about smartphone security and privacy. The author conducted a study with a betweensubject design, where apart from the game, a humorous video and a serious video explaining about smartphone security and privacy issues were used for the study. It was evident from the results that the participants preferred the humorous game followed by the humorous video. However, the users also pointed out that once all the decisions are known, the game would become boring. An Android app called "HappyPermi" <ref type="bibr" target="#b28">[33]</ref> Ninth International Workshop on Behavior Change Support Systems (BCSS 2021):</p><p>The Design and Development of Mobile Game to Promote Secure Smartphone Behaviour displayed the permissions requested by other apps installed in the users' phone along with examples of what data could be retrieved by the app if a specific permission was granted by the user. In the user study, it was found that the users were surprised to see their data being displayed in the place of example data, and most of them were concerned about their photos being accessible to the apps and also blocked contacts permission after using the "HappyPermi" <ref type="bibr" target="#b28">[33]</ref> app. Although the app tries to point out the causes and effects of permissions, it does not educate the users why a specific permission might be necessary for an app or why it might be unnecessary and the potential harms of granting unnecessary permissions. "Make my phone secure" <ref type="bibr" target="#b29">[34]</ref>, a role-playing game, where the player takes the role of an IT security expert and helps other nonplayable game characters (NPC) with their smartphone security problems that revolve around Android permission. The player must turn off appropriate permissions according to the problem statement presented to them in-game. However, the game focuses only on privacy intrusions that are visible in the foreground while using some apps.</p><p>While there is plenty of research around games for cybersecurity, very little work has been done for creating persuasive games to raise awareness around secure smartphone behaviour. Also, the games focus on Android permissions for specific apps only and thus, the user misses out on the context of permissions for other apps and is left to decide solely based on their intuition. Therefore, we present a mobile persuasive game, titled 'PermaRun', to promote secure smartphone user behaviour and improve their awareness about Android permissions in a contextual manner.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>3</head><p>System Design</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Initial Design Phase</head><p>To improve the Android permission handling awareness of the users and other secure smartphone behaviour, we designed a persuasive game called PermaRun. We followed the eight-step design process for creating a persuasive technology <ref type="bibr" target="#b30">[35]</ref> to come up with a design for the initial prototype of our game. We discuss these eight steps that are summarized in five stages below.</p><p>1. Choose a Target Behaviour. From the background work, it is evident that there is a scarcity of interventions for secure smartphone behaviour. Hence, we selected the target behaviour as secure smartphone behaviour awareness.</p><p>2. Choose a Target Audience. The audience of our intervention is Android smartphone users.</p><p>3. Find the Barriers Hindering the Target Behaviour. Users being unaware of secure smartphone behaviour, and dangers of insecure behaviours are barriers that we identified, which we have discussed in the background work section.</p><p>4. Choose a Technology Channel. Persuasive games have been widely adopted and have been implemented in various domains. Little or no persuasive games exist targeted at promoting secure smartphone behaviour. Thus, we planned to design a persuasive game. The Design and Development of Mobile Game to Promote Secure Smartphone Behaviour 5. Find Existing Examples of Persuasive Games, Imitate them, and Iterate. Before starting with our game design, we analyzed various cybersecurity games and persuasive games from other domains, as discussed in our background work section. The game design went through an iterative design process and received informal feedback from potential users to arrive at the final prototype presented in this paper, for which we hope to conduct a formal evaluation in the future.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2">Game Story</head><p>To maintain the context of smartphone security and to introduce this topic to the users, we came up with a story for the game. The story revolves around Android permissions and the need for awareness to teach users about the importance of being aware of secure smartphone behaviour. We call the main game character Dillon, whose main goal is to learn all about Android permissions and associated security and privacy issues to save his friends, who have been captured by a troll. Dillon went on a camping trip with his friends, and their plans are ruined by a troll, that came out of nowhere and started attacking the group. The troll was angry with humans because it was a recent victim of data theft. Dillon found out that the troll had been using an Android Smartphone and downloaded apps from untrusted sources and was careless while granting runtime permissions to the apps and hence became a victim of data theft. Dillon promised to help the troll by selecting appropriate app permissions, but the troll did not trust humans and, hence kidnapped Dillon's friends and promised to release them if Dillion helped the troll choose appropriate permissions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.3">PermaRun Persuasive Game Description</head><p>We developed the initial prototype with the Unity Game Engine <ref type="bibr" target="#b31">[36]</ref> and Proto.io <ref type="bibr" target="#b32">[37]</ref>, got informal feedback from the persuasive researchers of the Persuasive Computing Lab at Dalhousie University. We then used the feedback to refine and develop the main game using Unity Game Engine <ref type="bibr" target="#b31">[36]</ref>. During the initial prototyping sessions, we decided to have various levels in our game for teaching the players about permissions. Each level simulates a scenario for a specific app for which the player must collect appropriate runtime permissions according to the app's functionality. To give a context of runtime permissions required for a specific app, we include an instruction screen (Fig. <ref type="figure">1</ref>) explaining when it might be necessary for a player to accept runtime permissions and why those permissions are needed for that specific type of app. Apps require only a particular set of runtime permissions from the user to function as expected. This differs from one app to another. However, we try to highlight only the permissions that are essential for the core functionality of each type of app. Hence, we colour coded the permissions in a traffic signal format. The permissions that are green in colour are the ones that are required for an app, whereas the permissions that are red in colour are the ones that are not necessary for an apps' functionality. The main idea is that by playing the game, users learn to decide when a particular type of permission is necessary and when it is unnecessary for the functioning of the app. We plan to include a variety of apps from diverse categories for comprehensive knowledge. For example, an online Ninth International Workshop on Behavior Change Support Systems (BCSS 2021): The Design and Development of Mobile Game to Promote Secure Smartphone Behaviour music player might need location permission from the user to recommend them with local content. Thus, for each app, we consider the core functionalities and map dangerous permissions according to the required functionality. The description of each runtime permission is available at <ref type="bibr" target="#b33">[38]</ref>. Even though there are multiple runtime permissions, the common runtime permissions are grouped by Android [6] into 11 distinct groups. Hence, we only use permission groups <ref type="bibr" target="#b33">[38]</ref> to maintain a real-world context. We also designed our game to resemble the old 2D game Super Mario <ref type="bibr" target="#b34">[39]</ref>, to attract a diverse audience and reduce the learning curve. Recent research suggests that pastmemories and satisfaction of competence are directly affected by nostalgia, especially with retro games that are challenging and involve fast gameplay <ref type="bibr" target="#b35">[40]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.4">Game Play</head><p>Following our initial high-fidelity prototype and informal feedback from target users, we developed the first level of gameplay and used the "Online Music Streaming App" for which the player must collect the appropriate runtime permissions only. We chose the required permission groups as Microphone, Location and External Storage, which were depicted green in colour (Fig. <ref type="figure">2</ref>). Apart from these, we also had other unnecessary permissions that were red in colour (Fig. <ref type="figure">2</ref>). For every necessary permission that the player collects, they would gain points, and for every unnecessary permission, they would lose points and, their movement speed would be reduced for a short period. Whenever the player picks up a permission, we show them a suggestion related to secure smartphone behaviour, that is displayed in between the in-game controls, over the Heads-Up Display (HUD). The HUD shows the runtime permission symbols that are to be collected for that specific level. When the player finishes picking up a set of runtime permission, that specific permission would disappear from the HUD. When the player reaches the end of the level, they would be able to save Dillon's friends if they manage to collect all the required runtime permission in that specific level. If the player tries to complete the level without collecting all the app permissions, a dialog box pops up, informing the player to collect all the app permissions to save Dillon's friends. To make the game more interesting, we have obstacles, hidden areas, enemies, and other in-game items that reward the player with points. We discuss more about these in the upcoming sections. The Design and Development of Mobile Game to Promote Secure Smartphone Behaviour </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.5">Persuasive Principles</head><p>We built a fast-paced 2D side-scrolling game and implemented nine persuasive strategies (Reduction, Tunnelling, Self-Monitoring, Simulation, Rewards, Suggestion, Liking, Competition, Recognition) from the Persuasive System Design Framework <ref type="bibr" target="#b20">[25]</ref>. We will discuss the implementation of each persuasive principle in this section.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Self-Monitoring.</head><p>A system that helps the user to keep track of their performance to see their progress towards achieving their goals. The player has a HUD in between the ingame controls throughout the game (Fig. <ref type="figure">3</ref>). This HUD shows the permissions that are required for a specific level. When the user has finished collecting a specific set of permissions, then that permission would disappear from the HUD. The HUD serves as a self-monitoring tool for the player to check if there are any other permissions left to collect for that level before completing the level. If the player tries to complete the level The Design and Development of Mobile Game to Promote Secure Smartphone Behaviour without collecting all the app permissions, a dialog box pops up to inform the user to collect all the app permissions to save Dillon's friends.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Simulation.</head><p>A system that helps the user to observe the link between causes and effects by means of simulation. All the required permissions for a specific app are green in colour, and all the unnecessary permissions are red in colour. When the user picks up a necessary permission, their score increases, but when they pick up an unnecessary permission, their score and health decrease, and the player's movement speed reduces for a short duration.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Rewards.</head><p>A system that rewards the user for performing a specific task or target behaviour. The game currently has three rewards. When the players pick up the correct permissions or if they destroy an enemy, their score increases. Apart from this, the game has fruits that increase the player's health by a small amount. There are also extra lives in hidden areas for the player to collect. The player is transported to these hidden areas (Fig. <ref type="figure">4</ref>) when they pick up a gem in the game.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Suggestion.</head><p>A system that provides appropriate suggestions while the user is using the system. We give the users immediate feedback and tips regarding secure smartphone behaviour. Whenever the player picks up a permission, we show them tips and suggestions about secure smartphone behaviour. These suggestions are displayed in-between the in-game controller, over the HUD for a short period (Fig. <ref type="figure">5</ref>).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Liking.</head><p>A system that is visually attractive and appealing will be more persuasive. To improve the attractiveness of the game, we added sound effects for the game character and background music apart from other in-game features and animations.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Competition.</head><p>A system that leverages the human tendency of competition will be more persuasive. We have a leaderboard (Fig. <ref type="figure">6</ref>) where we rank the players according to their in-game score. This score increases as the player proceeds to successive levels. This score is affected by various factors like the type of permissions the player collects ingame, items that they pick up (E.g., Fruits), and the number of enemies destroyed.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Recognition.</head><p>A system that offers public recognition for a user will motivate the user to adopt the target behaviour. The users get badges if they reach a specific level/score or find a hidden item. The badges that the players earn show up on the leaderboard and are visible to other players too (Fig. <ref type="figure">6</ref>), and this might also serve as a normative influence.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Reduction.</head><p>A system that reduces the number of steps for achieving a target will motivate the users. During the initial phase of the prototype design, we decided to have various in-game checkpoints (Fig. <ref type="figure">7</ref>). Whenever the player loses health in the game, The Design and Development of Mobile Game to Promote Secure Smartphone Behaviour they start again from the last checkpoint. This process repeats until they lose all of their three lives, and a game-over dialog box would appear if they lose all of their lives, and the player would have options to either start over or quit the game. We consider this as a reduction since the player need not repeat the whole level if they make a mistake and lose a life in the middle of the game.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Tunnelling.</head><p>A system that guides the user in a step-by-step manner to achieve their target behaviour. There are two instances of tunnelling, one before the start of the game the player encounters the storyline followed by an instruction screen that explains how to play the game and shows other instructions like collecting appropriate permissions and destroying enemies would increase the player's score (Fig. <ref type="figure">3</ref>). Apart from the instruction screen, we placed the collectible permissions to guide the player to the end of the level.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.6">Game Design Patterns</head><p>To ensure that the game is engaging and enjoyable for the players, we followed the six game design patterns (Guidance, Foreshadowing, Safe Zone, Layering, Branching, Pace Breaking) as specified by Khalifa et al. <ref type="bibr" target="#b21">[26]</ref>.</p><p>Guidance. A non-verbal game element that guides the player towards the goal or in the right direction comes under guidance. Guidance can either be the in-game path or can be in-game collectible items or an enemy that attracts the players' attention to a particular location or an environmental cue that grabs the players' attention. We used the pathways to guide the player, and we used permissions as collectibles. Enemies and items were also placed in a manner to increase the players' curiosity and guide them towards a specific path. This game design pattern can be correlated with the tunnelling persuasive principle but in a gamified manner.</p><p>Foreshadowing. Teasing the player with an in-game element with which they might not be able to interact or can be a game element that changes over the course of the game comes under foreshadowing. We introduced foreshadowing in two ways. We tease players with hidden areas or inaccessible game items which would be accessible to them as they proceed to play through the levels (Fig. <ref type="figure">4</ref>). This design pattern increases the player's curiosity and keeps them hooked to the game. Initially, enemies are introduced in a stationary way, and later the player is introduced to patrolling enemies. This makes the game more interesting to play and might increase the players' curiosity. Safe Zone. The areas in-game, where the player is not in danger and can think about their next actions or where they can take a break from all the tension that was built ingame. We treat the checkpoints in our game as safe zones, where the player is not in danger and would feel safe. We have three checkpoints in our game (Fig. <ref type="figure">7</ref>) placed in such a way that the player would feel safe after exiting combat or can plan a strategy before going into combat. This pattern can be correlated with the reduction persuasive principle but in a gamified manner.</p><p>Layering. Combining multiple game elements or reusing the same game elements to introduce challenges is classified as layering. We placed enemies in-front of collectibles, positioned app permissions near enemies, and players can reach some areas only through a moving platform or platforms that are suspended in mid-air.</p><p>Branching. Giving the player multiple paths to explore in-game is classified as branching. If we apply constraints, where the player needs to meet specific conditions to choose another pathway, then it is called conditional branching. In our game, we The Design and Development of Mobile Game to Promote Secure Smartphone Behaviour implement both branching and conditional branching. For branching, we give an alternate path to the player for exploration, and for conditional branching, the player is teleported to another location if they pick up a gem. This makes the game more interesting and increases the curiosity of the player. Pace Breaking. Increasing or decreasing the tension in-game is commonly referred to as pace breaking. Pace breaking is usually achieved by introducing bosses or giving the player a break after a long period of combat. We implement pace breaking by introducing enemies and then by giving the player a brief break from combat. We mix the layering pattern with this by adding obstacles to the paths to keep the game interesting and to keep the players engaged.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Conclusion and Future Work</head><p>Due to the lack of interventions for smartphone security and privacy awareness, we designed a persuasive game for improving users' awareness and self-efficacy about secure smartphone behaviour. The key takeaways from our design are: (a) Our game gives instant feedback or tips about secure smartphone behaviour when the player picks up a permission symbol in-game. (b) We built the game according to six game design patterns <ref type="bibr" target="#b21">[26]</ref> to make it more enjoyable for the player and implemented nine persuasive principles to motivate the players. (c) We impart skills for secure smartphone behaviour and expose the dangers of unnecessary permissions to an individual's privacy and security using an interesting game narrative while maintaining the context of smartphone security. For our future work, we are looking forward to evaluating the game to examine both its usability and effectiveness with respect to promoting safe smartphone security behaviour and privacy knowledge. We are also planning to tailor the game <ref type="bibr" target="#b36">[41]</ref><ref type="bibr" target="#b37">[42]</ref><ref type="bibr" target="#b38">[43]</ref> and consider the players' emotions because most times when a security incident occurs, it is because the user is either desperate, careless <ref type="bibr" target="#b9">[14]</ref>, or impulsive <ref type="bibr" target="#b4">[9]</ref>. </p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 .Fig. 2 .</head><label>12</label><figDesc>Fig. 1. Instruction Screen</figDesc><graphic coords="7,169.10,326.80,257.10,140.60" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 3 .Fig. 4 .</head><label>34</label><figDesc>Fig. 3. In-game Instructions</figDesc><graphic coords="10,174.65,321.70,245.25,134.57" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Fig. 5 .Fig. 7 .</head><label>57</label><figDesc>Fig. 5. In-game Suggestions</figDesc><graphic coords="11,178.90,379.90,237.50,125.50" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head></head><label></label><figDesc>The Design and Development of Mobile Game to Promote Secure Smartphone Behaviour 4. Flynn, L., Klieber, W.: Smartphone Security. IEEE Pervasive Comput. 14, 16-21 (2015). https://doi.org/10.1109/MPRV.2015.67.</figDesc><table><row><cell>5.</cell><cell>Google:</cell><cell>App</cell><cell cols="2">permissions</cell><cell>overview</cell><cell>|</cell><cell cols="2">Android</cell><cell>Developers,</cell></row><row><cell></cell><cell cols="7">https://developer.android.com/training/basics/permissions,</cell><cell>last</cell><cell>accessed</cell></row><row><cell></cell><cell cols="2">2020/12/03.</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>6.</cell><cell>Google:</cell><cell cols="2">Permissions</cell><cell>on</cell><cell>Android</cell><cell>|</cell><cell>Android</cell><cell>Developers,</cell></row><row><cell></cell><cell cols="8">https://developer.android.com/guide/topics/permissions/overview,</cell><cell>last</cell></row><row><cell></cell><cell cols="3">accessed 2020/11/29.</cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>7.</cell><cell>Application</cell><cell></cell><cell>Signing</cell><cell>|</cell><cell>Android</cell><cell cols="2">Open</cell></row></table></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Acknowledgement. This research was undertaken, in part, thanks to funding from the Canada Research Chairs Program. We acknowledge the support of the Natural Sciences and Engineering Research Council of Canada (NSERC) through the Discovery Grant.</p></div>
			</div>


			<div type="availability">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Source</head><p>Project, https://source.android.com/security/apksigning, last accessed 2020/12/04.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Smartphone Cyber Security Awareness in Developing Countries: A Case of Thailand</title>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">C</forename><surname>Popova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename></persName>
		</author>
		<idno type="DOI">10.1007/978-3-030-05198-3</idno>
		<ptr target="https://doi.org/10.1007/978-3-030-05198-3" />
	</analytic>
	<monogr>
		<title level="j">Dep. Comput. Syst. Sci. Stock. Univ. Sweden</title>
		<imprint>
			<biblScope unit="volume">58</biblScope>
			<biblScope unit="page">68</biblScope>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Collusive data leak and more: Largescale threat analysis of inter-app communications</title>
		<author>
			<persName><forename type="first">A</forename><surname>Bosu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Liu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">D</forename><surname>Yao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Wang</surname></persName>
		</author>
		<idno type="DOI">10.1145/3052973.3053004</idno>
		<ptr target="https://doi.org/10.1145/3052973.3053004" />
	</analytic>
	<monogr>
		<title level="m">ASIA CCS 2017 -Proceedings of the 2017 ACM Asia Conference on Computer and Communications Security</title>
				<imprint>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page" from="71" to="85" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<author>
			<persName><forename type="first">J</forename><surname>Reardon</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Á</forename><surname>Feal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Elazari</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>On</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Vallina-Rodriguez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Egelman</surname></persName>
		</author>
		<title level="m">Open access to the Proceedings of the 28th USENIX Security Symposium is sponsored by USENIX. 50 Ways to Leak Your Data: An Exploration of Apps&apos; Circumvention of the Android Permissions System 50 Ways to Leak Your Data: An Exploration of Apps&apos; Circumvention of the Android Permissions System</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<ptr target="https://developer.android.com/training/permissions/usage-notes" />
		<title level="m">Google: App permissions best practices | Android Developers</title>
				<imprint>
			<date type="published" when="2020-11-29">2020/11/29</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Breaching the human firewall: Social engineering in phishing and spear-phishing emails</title>
		<author>
			<persName><forename type="first">M</forename><surname>Butavicius</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Parsons</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Pattinson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Mccormac</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ACIS 2015 Proceedings -26th Australasian Conference on Information Systems</title>
				<imprint>
			<date type="published" when="2015">2015</date>
			<biblScope unit="page" from="1" to="10" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Evaluating the Information Security Awareness of Smartphone Users</title>
		<author>
			<persName><forename type="first">R</forename><surname>Bitton</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Boymgold</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Puzis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Shabtai</surname></persName>
		</author>
		<idno type="DOI">10.1145/3313831.3376385</idno>
		<ptr target="https://doi.org/10.1145/3313831.3376385" />
	</analytic>
	<monogr>
		<title level="m">Conference on Human Factors in Computing Systems -Proceedings</title>
				<imprint>
			<date type="published" when="2020">2020. 2020</date>
			<biblScope unit="page" from="1" to="13" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Information security behaviors of smartphone users in China: An empirical analysis</title>
		<author>
			<persName><forename type="first">X</forename><forename type="middle">J</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Deng</surname></persName>
		</author>
		<idno type="DOI">10.1108/EL-09-2016-0183</idno>
		<ptr target="https://doi.org/10.1108/EL-09-2016-0183" />
	</analytic>
	<monogr>
		<title level="j">Electron. Libr</title>
		<imprint>
			<biblScope unit="volume">35</biblScope>
			<biblScope unit="page" from="1177" to="1190" />
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">A survey on smartphone user&apos;s security choices, awareness and education</title>
		<author>
			<persName><forename type="first">F</forename><surname>Breitinger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Tully-Doyle</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Hassenfeldt</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.cose.2019.101647</idno>
		<ptr target="https://doi.org/10.1016/j.cose.2019.101647" />
	</analytic>
	<monogr>
		<title level="j">Comput. Secur</title>
		<imprint>
			<biblScope unit="volume">88</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Security Awareness Level of Smartphone Users: An Exploratory Case Study</title>
		<author>
			<persName><forename type="first">M</forename><surname>Koyuncu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Pusatli</surname></persName>
		</author>
		<idno type="DOI">10.1155/2019/2786913</idno>
		<ptr target="https://doi.org/10.1155/2019/2786913" />
	</analytic>
	<monogr>
		<title level="j">Mob. Inf. Syst</title>
		<imprint>
			<date type="published" when="2019">2019. 2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Smartphone Owners Need Security Advice . How Can We Ensure They Get It ?</title>
		<author>
			<persName><forename type="first">K</forename><surname>Renaud</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CONF-IRM 2016 Proceedings</title>
				<imprint>
			<date type="published" when="2016">2016</date>
			<biblScope unit="page">60</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Taxonomy of mobile users&apos; security awareness</title>
		<author>
			<persName><forename type="first">R</forename><surname>Bitton</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Finkelshtein</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Sidi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Puzis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Rokach</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Shabtai</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.cose.2017.10.015</idno>
		<ptr target="https://doi.org/10.1016/j.cose.2017.10.015" />
	</analytic>
	<monogr>
		<title level="j">Comput. Secur</title>
		<imprint>
			<biblScope unit="volume">73</biblScope>
			<biblScope unit="page" from="266" to="293" />
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Cybersecurity behaviour of smartphone users in India: an empirical analysis</title>
		<author>
			<persName><forename type="first">P</forename><surname>Shah</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Agarwal</surname></persName>
		</author>
		<idno type="DOI">10.1108/ICS-04-2019-0041</idno>
		<ptr target="https://doi.org/10.1108/ICS-04-2019-0041" />
	</analytic>
	<monogr>
		<title level="j">Inf. Comput. Secur</title>
		<imprint>
			<biblScope unit="volume">28</biblScope>
			<biblScope unit="page" from="293" to="318" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Risk Awareness, Self-Efficacy, and Social Support Predict Secure Smartphone Usage</title>
		<author>
			<persName><forename type="first">G</forename><surname>Zhou</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Gou</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Gan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Schwarzer</surname></persName>
		</author>
		<idno type="DOI">10.3389/fpsyg.2020.01066</idno>
		<ptr target="https://doi.org/10.3389/fpsyg.2020.01066" />
	</analytic>
	<monogr>
		<title level="j">Front. Psychol</title>
		<imprint>
			<biblScope unit="volume">11</biblScope>
			<biblScope unit="page" from="1" to="8" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">LunchTime: A slow-casual game for long-term dietary behavior change</title>
		<author>
			<persName><forename type="first">R</forename><surname>Orji</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Vassileva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">L</forename><surname>Mandryk</surname></persName>
		</author>
		<idno type="DOI">10.1007/s00779-012-0590-6</idno>
		<ptr target="https://doi.org/10.1007/s00779-012-0590-6" />
	</analytic>
	<monogr>
		<title level="j">Pers. Ubiquitous Comput</title>
		<imprint>
			<biblScope unit="volume">17</biblScope>
			<biblScope unit="page" from="1211" to="1221" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">STD PONG: Changing Risky Sexual Behaviour in Africa Ninth International Workshop on Behavior Change Support Systems (BCSS 2021): The Design and Development of Mobile Game to Promote Secure Smartphone Behaviour through Persuasive Games</title>
		<author>
			<persName><forename type="first">C</forename><surname>Ndulue</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Orji</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Second African Conference for Human Computer Interaction: Thriving Communities</title>
				<meeting>the Second African Conference for Human Computer Interaction: Thriving Communities<address><addrLine>New York, NY, USA</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Nourish Your Tree! Developing a Persuasive Exergame for Promoting Physical Activity among Adults</title>
		<author>
			<persName><forename type="first">O</forename><surname>Oyebode</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Maurya</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Orji</surname></persName>
		</author>
		<idno type="DOI">10.1109/SeGAH49190.2020.9201637</idno>
		<ptr target="https://doi.org/10.1109/SeGAH49190.2020.9201637" />
	</analytic>
	<monogr>
		<title level="m">IEEE 8th International Conference on Serious Games and Applications for Health</title>
				<meeting><address><addrLine>SeGAH</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2020">2020. 2020. 2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Phishy -A serious game to train enterprise users on phishing awareness</title>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">J</forename><surname>Gokul</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Pandit</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Vaddepalli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Tupsamudre</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Banahatti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Lodha</surname></persName>
		</author>
		<idno type="DOI">10.1145/3270316.3273042</idno>
		<ptr target="https://doi.org/10.1145/3270316.3273042" />
	</analytic>
	<monogr>
		<title level="m">CHI PLAY 2018 -Proceedings of the 2018 Annual Symposium on Computer-Human Interaction in Play Companion Extended Abstracts</title>
				<imprint>
			<date type="published" when="2018">2018</date>
			<biblScope unit="page" from="169" to="181" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">PHISHER CRUSH: A Mobile Persuasive Game for Promoting Online Security</title>
		<author>
			<persName><forename type="first">C</forename><surname>Ndulue</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Oyebode</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Orji</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-030-45712-9</idno>
		<ptr target="https://doi.org/10.1007/978-3-030-45712-9" />
	</analytic>
	<monogr>
		<title level="s">Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics</title>
		<imprint>
			<biblScope unit="page" from="223" to="233" />
			<date type="published" when="2020">2020</date>
			<publisher>Springer International Publishing</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">Using a game to teach about phishing</title>
		<author>
			<persName><forename type="first">P</forename><surname>Weanquoi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Johnson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Zhang</surname></persName>
		</author>
		<idno type="DOI">10.1145/3125659.3125669</idno>
		<ptr target="https://doi.org/10.1145/3125659.3125669" />
	</analytic>
	<monogr>
		<title level="m">-Proc. 18th Annu. Conf. Inf. Technol. Educ</title>
				<imprint>
			<date type="published" when="2017">2017. 2017</date>
			<biblScope unit="volume">75</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<analytic>
		<title level="a" type="main">What.Hack: Engaging Anti-Phishing Training through a Role-playing Phishing Simulation Game</title>
		<author>
			<persName><forename type="first">Z</forename><forename type="middle">A</forename><surname>Wen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Lin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Andersen</surname></persName>
		</author>
		<idno type="DOI">10.1145/3290605.3300338</idno>
		<ptr target="https://doi.org/10.1145/3290605.3300338" />
	</analytic>
	<monogr>
		<title level="j">Conf. Hum. Factors Comput. Syst. -Proc</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="issue">12</biblScope>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">Persuasive systems design: Key issues, process model, and system features</title>
		<author>
			<persName><forename type="first">H</forename><surname>Oinas-Kukkonen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Harjumaa</surname></persName>
		</author>
		<idno type="DOI">10.17705/1cais.02428</idno>
		<ptr target="https://doi.org/10.17705/1cais.02428" />
	</analytic>
	<monogr>
		<title level="j">Commun. Assoc. Inf. Syst</title>
		<imprint>
			<biblScope unit="volume">24</biblScope>
			<biblScope unit="page" from="485" to="500" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<analytic>
		<title level="a" type="main">Level design patterns in 2D games</title>
		<author>
			<persName><forename type="first">A</forename><surname>Khalifa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>De Mesentier Silva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Togelius</surname></persName>
		</author>
		<idno type="DOI">10.1109/CIG.2019.8847953</idno>
		<ptr target="https://doi.org/10.1109/CIG.2019.8847953" />
	</analytic>
	<monogr>
		<title level="m">IEEE Conf. Comput. Intell. Games, CIG. 2019-Augus</title>
				<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<analytic>
		<title level="a" type="main">Active learning with the CyberCIEGE video game</title>
		<author>
			<persName><forename type="first">M</forename><surname>Thomps</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Irvine</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">4th Workshop on Cyber Security Experimentation and Test, CSET 2011</title>
				<imprint>
			<date type="published" when="2011">2011</date>
			<biblScope unit="page" from="1" to="8" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b23">
	<analytic>
		<title level="a" type="main">Development Of Serious Games For Teaching Digital Forensics</title>
		<author>
			<persName><forename type="first">J</forename><surname>Yerby</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Issues Inf. Syst</title>
		<imprint>
			<biblScope unit="volume">13</biblScope>
			<biblScope unit="page" from="112" to="122" />
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b24">
	<analytic>
		<title level="a" type="main">Security through play</title>
		<author>
			<persName><forename type="first">M</forename><surname>Gondree</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><forename type="middle">N J</forename><surname>Peterson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Denning</surname></persName>
		</author>
		<idno type="DOI">10.1109/MSP.2013.69</idno>
		<ptr target="https://doi.org/10.1109/MSP.2013.69" />
	</analytic>
	<monogr>
		<title level="j">IEEE Secur. Priv</title>
		<imprint>
			<biblScope unit="volume">11</biblScope>
			<biblScope unit="page" from="64" to="67" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b25">
	<analytic>
		<title level="a" type="main">Gamification Techniques for Raising Cyber Security Awareness</title>
		<author>
			<persName><forename type="first">S</forename><surname>Scholefield</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">A</forename><surname>Shepherd</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">LNCS</title>
		<imprint>
			<biblScope unit="page" from="191" to="203" />
			<date type="published" when="2019">2019. 2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b26">
	<analytic>
		<title level="a" type="main">Self-efficacy-based game design to encourage security behavior online</title>
		<author>
			<persName><forename type="first">T</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Dabbish</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Hammer</surname></persName>
		</author>
		<idno type="DOI">10.1145/3290607.3312935</idno>
		<ptr target="https://doi.org/10.1145/3290607.3312935" />
	</analytic>
	<monogr>
		<title level="m">Association for Computing The Design and Development of Mobile Game to Promote Secure Smartphone Behaviour Machinery</title>
				<meeting><address><addrLine>New York, NY, USA</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="1" to="6" />
		</imprint>
	</monogr>
	<note>Conference on Human Factors in Computing Systems -Proceedings</note>
</biblStruct>

<biblStruct xml:id="b27">
	<analytic>
		<title level="a" type="main">What could go wrong? Raising mobile privacy and security awareness through a decision-making game. CHI Play 2019 -Ext</title>
		<author>
			<persName><forename type="first">N</forename><surname>Zargham</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Bahrini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Volkmar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Sohr</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Wenig</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Malaka</surname></persName>
		</author>
		<idno type="DOI">10.1145/3341215.3356273</idno>
		<ptr target="https://doi.org/10.1145/3341215.3356273" />
	</analytic>
	<monogr>
		<title level="j">Abstr. Annu. Symp. Comput. Interact. Play</title>
		<imprint>
			<biblScope unit="page" from="805" to="812" />
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b28">
	<analytic>
		<title level="a" type="main">HappyPerMi: Presenting critical data flows in mobile application to raise user security awareness</title>
		<author>
			<persName><forename type="first">M</forename><surname>Bahrini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Meissner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Malaka</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Wenig</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Sohr</surname></persName>
		</author>
		<idno type="DOI">10.1145/3290607.3312914</idno>
		<ptr target="https://doi.org/10.1145/3290607.3312914" />
	</analytic>
	<monogr>
		<title level="m">Conf. Hum. Factors Comput. Syst. -Proc</title>
				<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b29">
	<analytic>
		<title level="a" type="main">Make my phone secure! Using gamification for mobile security settings</title>
		<author>
			<persName><forename type="first">M</forename><surname>Bahrini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Schmutte</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Wenig</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Sohr</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Malaka</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename></persName>
		</author>
		<idno type="DOI">10.1145/3340764.3340775</idno>
		<ptr target="https://doi.org/10.1145/3340764.3340775" />
	</analytic>
	<monogr>
		<title level="m">ACM Int. Conf. Proceeding Ser</title>
				<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="299" to="308" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b30">
	<analytic>
		<title level="a" type="main">Creating persuasive technologies: An eight-step design process</title>
		<author>
			<persName><forename type="first">B</forename><forename type="middle">J</forename><surname>Fogg</surname></persName>
		</author>
		<idno type="DOI">10.1145/1541948.1542005</idno>
		<ptr target="https://doi.org/10.1145/1541948.1542005" />
	</analytic>
	<monogr>
		<title level="j">ACM Int. Conf. Proceeding Ser</title>
		<imprint>
			<biblScope unit="volume">350</biblScope>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b31">
	<monogr>
		<ptr target="https://unity.com/" />
		<title level="m">Unity: Unity Real-Time Development Platform | 3D, 2D VR &amp; AR Engine</title>
				<imprint>
			<date type="published" when="2020-12-04">2020/12/04</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b32">
	<monogr>
		<author>
			<persName><surname>Proto</surname></persName>
		</author>
		<author>
			<persName><surname>Io</surname></persName>
		</author>
		<ptr target="https://proto.io/" />
		<title level="m">Proto.io -Prototypes that feel real</title>
				<imprint>
			<date type="published" when="2020-12-04">2020/12/04</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b33">
	<monogr>
		<ptr target="https://developer.android.com/reference/android/Manifest.permission_group" />
		<title level="m">Manifest.permission_group | Android Developers</title>
				<imprint>
			<date type="published" when="2020-12-03">2020/12/03</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b34">
	<monogr>
		<ptr target="https://mario.nintendo.com/" />
		<title level="m">The official home of Super Mario TM -Home</title>
				<imprint>
			<date type="published" when="2021-01-11">2021/01/11</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b35">
	<analytic>
		<title level="a" type="main">Once Upon a Game: Exploring Video Game Nostalgia and Its Impact on Well-Being</title>
		<author>
			<persName><forename type="first">T</forename><surname>Wulf</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">D</forename><surname>Bowman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">A</forename><surname>Velez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Breuer</surname></persName>
		</author>
		<idno type="DOI">10.1037/ppm0000208</idno>
		<ptr target="https://doi.org/10.1037/ppm0000208" />
	</analytic>
	<monogr>
		<title level="j">Psychol. Pop. Media Cult</title>
		<imprint>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b36">
	<analytic>
		<title level="a" type="main">Socially-driven persuasive health intervention design: Competition, social comparison, and cooperation</title>
		<author>
			<persName><forename type="first">R</forename><surname>Orji</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Oyibo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">K</forename><surname>Lomotey</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">A</forename><surname>Orji</surname></persName>
		</author>
		<idno type="DOI">10.1177/1460458218766570</idno>
		<ptr target="https://doi.org/10.1177/1460458218766570" />
	</analytic>
	<monogr>
		<title level="j">Health Informatics J</title>
		<imprint>
			<biblScope unit="volume">25</biblScope>
			<biblScope unit="page" from="1451" to="1484" />
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b37">
	<analytic>
		<title level="a" type="main">Improving the efficacy of games for change using personalization models</title>
		<author>
			<persName><forename type="first">R</forename><surname>Orji</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">L</forename><surname>Mandryk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Vassileva</surname></persName>
		</author>
		<idno type="DOI">10.1145/3119929</idno>
		<ptr target="https://doi.org/10.1145/3119929" />
	</analytic>
	<monogr>
		<title level="j">ACM Trans. Comput. Interact</title>
		<imprint>
			<biblScope unit="volume">24</biblScope>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b38">
	<analytic>
		<title level="a" type="main">Towards a Trait Model of Video Game Preferences</title>
		<author>
			<persName><forename type="first">G</forename><surname>Fortes Tondello</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Valtchanov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Reetz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">R</forename><surname>Wehbe</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Orji</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">E</forename><surname>Nacke</surname></persName>
		</author>
		<idno type="DOI">10.1080/10447318.2018.1461765</idno>
		<ptr target="https://doi.org/10.1080/10447318.2018.1461765" />
	</analytic>
	<monogr>
		<title level="j">Int. J. Human-Computer Interact</title>
		<imprint>
			<biblScope unit="volume">34</biblScope>
			<biblScope unit="page" from="732" to="748" />
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
