A STUDY OF MODERN MOBILE TABLETS

By

Jordan Kahtava

A thesis submitted in partial fulfillment of the requirements for the degree

Bachelor of Computer Science

Algoma University

Gerry Davies, Thesis Advisor

April 14th, 2016 A Study of Modern Mobile Tablets - 1

Abstract

Mobile tablets have begun playing a larger role in mobile computing because of their portability.

To gather an understanding of what mobile computers can currently accomplish Microsoft and

Apple tablets were examined. In general this topic is very broad and hard to research because of the number of mobile devices and tablets. Examining this document should provide detailed insight into mobile tablets and their hardware, operating systems, and programming environment. Any developer can use the information to develop, publish, and setup the appropriate development environments for either Apple or Microsoft. The Incremental waterfall methodology was used to develop two applications that utilize the Accelerometer, Gyroscope, and Inclinometer/Attitude sensors. In addition extensive research was conducted and combined to outline how applications can be published and the rules associated with each application store.

The Apple application used Xcode and Objective-C while the Microsoft application used Visual

Studio 2012, C-Sharp, and XAML. It was determined that developing for Apple is significantly easier because of the extensive documentation and examples available. In addition Apple’s IDE

Xcode can be used to develop, design, test, and publish applications without the need for other programs. It is hard to find easily understandable documentation from Microsoft regarding a particular operating system. Visual Studio 2012 or later must be used to develop Microsoft Store applications. Visual Studios can be used to develop, design, and publish applications, however to test against a Surface tablet a developer must install certificates and side load the application. All of the research gathered can be used by any developer wishing to target iOS and Microsoft Store applications. In conclusion, all the information gathered can be used by a business or individual trying to determine the cost and complexity of developing for either Apple or Microsoft. A Study of Modern Mobile Tablets - 2

Acknowledgements

I would like to thank my thesis supervisor Gerry Davies for his patience and assistance with my thesis. I would also like to thank Dr. Miguel Garcia-Ruiz for being my second reader and the guidance on how to improve my thesis document.

A Study of Modern Mobile Tablets - 3

Table of Contents

Chapter One: Proposal ...... 8 1.1. Introduction ...... 8 1.2. Objectives ...... 8 1.3. Rationale ...... 9 1.4. Scope ...... 9 1.5. TimeTable ...... 11 Chapter Two: Mobile Devices ...... 13 2.1. Apple Devices ...... 13 2.1.1. IPad Series: ...... 13 2.1.2. IPad Air Series: ...... 18 2.1.3. IPad Mini Series: ...... 20 2.1.4. IPad Pro Series: ...... 23 2.2. Microsoft Devices ...... 25 2.2.1. Surface Series:...... 26 2.2.2. Surface Pro Series: ...... 30 2.2.3. Surface Book Series: ...... 35 Chapter Three: Programming Languages ...... 38 3.1. Objective C ...... 38 3.2. C-Sharp ...... 41 3.3. Comparison ...... 42 3.4. Development ...... 47 3.4.1. Apple ...... 47 3.4.2. Microsoft ...... 56 Chapter Four: Publishing Applications ...... 67 4.1. Apple Application Store...... 67 4.2. Microsoft Store ...... 72 4.3. Developer Licenses ...... 76 Chapter Five: Operating Systems ...... 78 5.1. IOS ...... 78 5.1.1. IOS 5 ...... 78 5.1.2. IOS 6 ...... 79 A Study of Modern Mobile Tablets - 4

5.1.3. IOS 7 ...... 80 5.1.4. IOS 8 ...... 81 5.1.5. IOS 9 ...... 82 5.2. Windows 8.1 RT ...... 83 5.3. Windows 10 ...... 83 Chapter Six: Materials and Methods ...... 85 6.1. Materials and Methods ...... 85 Chapter Seven: Results and Conclusion ...... 123 7.1. Results ...... 123 7.2. Conclusion ...... 127 Appendices ...... 132 Appendix A: Device Specifications ...... 132 TABLE I...... 133 TABLE II...... 134 TABLE III...... 135 TABLE IV...... 136 TABLE V...... 137 TABLE VI...... 138 TABLE VII...... 140 Appendix B: Software Statement of Scope ...... 141 B.1. Project Inception: ...... 141 B.2. Functional Requirements: ...... 142 B.3. Non-Functional Requirements ...... 146 Appendix C: Source Code ...... 149 C.1. Increment 1: Accelerometer, IOS ...... 151 C.2. Increment 2: Gyroscope, IOS ...... 156 C.3. Increment 3: Integration, IOS ...... 163 C.4. Increment 4: Accelerometer, Windows 8 ...... 174 C.5. Increment 5: Gyroscope, Windows 8 ...... 181 C.6. Increment 6: Integration, Windows 8 ...... 189 Glossary ...... 207 References ...... 208

A Study of Modern Mobile Tablets - 5

Table of Figures

Figure 1 ...... 13 Figure 2 ...... 15 Figure 3 ...... 15 Figure 4 ...... 17 Figure 5 ...... 19 Figure 6 ...... 22 Figure 7 ...... 24 Figure 8 ...... 26 Figure 9 ...... 28 Figure 10 ...... 28 Figure 11 ...... 29 Figure 12 ...... 32 Figure 13 ...... 32 Figure 14 ...... 33 Figure 15 ...... 36 Figure 16 ...... 40 Figure 17 ...... 43 Figure 18 ...... 43 Figure 19 ...... 44 Figure 20 ...... 44 Figure 21 ...... 45 Figure 22 ...... 46 Figure 23 ...... 46 Figure 24 ...... 47 Figure 25 ...... 48 Figure 26 ...... 49 Figure 27 ...... 50 Figure 28 ...... 51 Figure 29 ...... 52 Figure 30 ...... 53 Figure 31 ...... 55 Figure 32 ...... 56 Figure 33 ...... 57 Figure 34 ...... 58 Figure 35 ...... 58 Figure 36 ...... 60 Figure 37 ...... 60 Figure 38 ...... 62 Figure 39 ...... 63 Figure 40 ...... 64 A Study of Modern Mobile Tablets - 6

Figure 41 ...... 65 Figure 42 ...... 66 Figure 43 ...... 68 Figure 44 ...... 69 Figure 45 ...... 69 Figure 46 ...... 70 Figure 47 ...... 71 Figure 48 ...... 72 Figure 49 ...... 73 Figure 50 ...... 74 Figure 51 ...... 75 Figure 52 ...... 78 Figure 53 ...... 84 Figure 54 ...... 86 Figure 55 ...... 87 Figure 56 ...... 89 Figure 57 ...... 91 Figure 58 ...... 91 Figure 59 ...... 92 Figure 60 ...... 93 Figure 61 ...... 93 Figure 62 ...... 94 Figure 63 ...... 95 Figure 64 ...... 96 Figure 65 ...... 98 Figure 66 ...... 99 Figure 67 ...... 100 Figure 68 ...... 102 Figure 69 ...... 103 Figure 70 ...... 103 Figure 71 ...... 104 Figure 72 ...... 105 Figure 73 ...... 106 Figure 74 ...... 108 Figure 75 ...... 110 Figure 76 ...... 111 Figure 77 ...... 112 Figure 78 ...... 112 Figure 79 ...... 113 Figure 80 ...... 115 Figure 81 ...... 117 Figure 82 ...... 119 Figure 83 ...... 121 Figure 84 ...... 121 A Study of Modern Mobile Tablets - 7

Figure 85 ...... 122 Figure 86 ...... 122 Figure 87 ...... 128 Figure 88 ...... 129 Figure 89 ...... 143 Figure 90 ...... 144

A Study of Modern Mobile Tablets - 8

Chapter One: Proposal

1.1. Introduction

1.2. Objectives

1.3. Rationale

1.4. Scope

1.5. Timetable

1.1. Introduction

The introduction of the mobile phone in 1973 changed how the world communicated.

Since their inception, new and more innovative products have emerged such as tablets,

smart watches, and fitness trackers. Mobile devices are now used by almost everyone.

This research will provide a better understanding on current mobile tablets, their

histories, hardware, operating systems, application development, and implementation.

The results gathered will be used to assess advantages and disadvantages of particular

mobile tablets providing useful information for developers.

1.2. Objectives

1) Review the history of Microsoft and Apple mobile devices.

2) Research the internal hardware and features of specific Apple and Microsoft devices.

3) Investigate commonalities and key differences between Objective C and C-Sharp. A Study of Modern Mobile Tablets - 9

4) Investigate the process required to develop and publish an application for Microsoft

and Apple.

5) Research differences between Apple and Microsoft operating systems.

6) Demonstrate application development techniques by creating a sample application.

1.3. Rationale

The basis for this research is to better understand mobile devices, their evolution and

innovation. Mobile devices are going to be playing an increased role in business

environments. For example, almost all courier services now use mobile devices to gather

client signatures. This detailed study will help individuals understand the different steps

necessary to develop and publish applications to both Windows and Apple systems. The

information can be used to determine the appropriate mobile hardware required for an

individual project. All the data collected will be useful for many years. Once the data

has become obsolete it can be used as a reference on how mobile devices evolved within

this period.

1.4. Scope

The study of mobile devices will be broken down into a few select systems and versions.

The main focus will be on mobile tablets and wearable technology. The details to be

examined include their histories, programming languages, applications stores, hardware,

and operating systems. A brief history of monumental changes in mobile devices will be A Study of Modern Mobile Tablets - 10

initiated displaying only substantial changes in the field. To examine the differences between C-Sharp and Objective-C an application will be developed with similar functionality for both Apple and Microsoft tablets. This application will measure the speed and accuracy of each systems features. The goal is to develop a program that uses the different features of each system. The programming languages will also be studied to provide a list of key differences, and similarities. Both Microsoft and Apple have their own application store. These stores will be researched providing an understanding of the processes required in developing and publishing applications. An in-depth analysis will outline how to acquire developer licenses, publish applications, and payment methods.

An overview will be created outlining each mobile devices, processor, memory, cost, ports, and any proprietary peripheral connectors. Lastly the operating systems will be probed to develop an understanding on how the system works.

A Study of Modern Mobile Tablets - 11

1.5. TimeTable

A Study of Modern Mobile Tablets - 12

A Study of Modern Mobile Tablets - 13

Chapter Two: Mobile Devices

2.1. Apple Devices

2.2. Microsoft Devices

2.1. Apple Devices

Apple incorporated has developed a number of mobile devices including a few different

generations of tablets. These tablets include the iPad 1 - 4, iPad Air 1- 2, iPad Mini 1 - 4,

and the iPad Pro. Each version of the iPad improves on a particular piece of hardware

most often the System on a Chip is modified to include a different GPU and CPU. Each

device was released approximately one year apart as can be seen in Figure 1.

Figure 1 A timeline of all the iPad release dates starting from 2010 - 2015.

(“Created by Author”)

2.1.1. IPad Series:

General Details:

The tablets that were examined include the original iPad, iPad 2, 3, and 4. The original

iPad or the first was very basic and can no longer be updated. Appendix A, Table I [1 -

26] contains all the hardware information for the iPad 1, 2, 3, and 4. The first generation A Study of Modern Mobile Tablets - 14

iPad can only upgrade to iOS 5.1.1 [9] which over time will cause a reduction in the number of compatible apps an image is shown in Figure 2 [27]. Figure 3 depicts iPad versions 2 through 4 [28]. Every iPad other then the first version can upgrade their

Operating System (OS) to the most current iOS 9.2 [10]. Each device has a 9.7 inch display the original iPad and version two have a resolution of 1024 by 768, while versions three and four received Retina displays which improved the resolution to 2048 by 1536 [1 - 4]. The Retina display may be the factor that resulted in an 18.8 watt increase in the battery from version two to three [25, 20]. According to Jones the human eye can perceive 287 pixels per inch, confirming that apples 326 pixels per inch display is better than the human eye [29]. The storage options available for most iPad versions include a minimum of 16 GB to a maximum of 128 GB of hard-drive space [1 - 4]. The maximum amount of storage varies with each version indicated in Table I. System memory for the iPad 1 is 256 MB of DRAM [19], the iPad 2 improves with 512 MB of

DDR2 [13], while the iPad 3 and 4 receive 1 GB of DDR2 [20 - 22]. The iPad 2, 3, and 4 all contain a front and back camera the front camera ranges from 0.3 to 1.2 Megapixels and the back camera is 0.7 to 5 megapixels depending on the iPad generation [1 - 4, 23,

24, 20]. Each device is capable of accessing Wi-Fi and Bluetooth, a digital compass exists that can pinpoint your location based on your Wi-Fi location [1-4]. Every iPad except the first includes an Accelerometer, Ambient Light Sensor, and a Gyroscope [2-

4]. The accelerometer is used to determine the force of gravity on the x, y, and z axis.

The ambient light sensor is used to adjust a displays backlight based on the amount of light in an area. A gyroscope gets the angular velocity of a device based on the x, y, and z axis. A Study of Modern Mobile Tablets - 15

Figure 2 Picture of the first generation iPad running IOS 5.

Figure 3 Picture of the 2nd, 3rd, and 4th iPads running IOS 9.

A Study of Modern Mobile Tablets - 16

System on a Chip:

Each version of the iPad uses a System on a Chip (SOC) that is designed by Apple it includes a GPU and CPU in one package. A typical SOC is meant as a motherboard replacement it can contain processors, input output, and power management controllers

[30]. SOC’s are generally used in the mobile device market because of the reduced power consumption and size [30]. A good example of an SOC is the Tegra 3 as shown in

Figure 4[31] which has CPU, GPU, Video, Audio, and Image processing. A CPU uses the GPU to offload graphic intensive computations freeing up the CPU for other tasks

[32]. The main difference between a CPU and GPU is that a GPU is designed to work on task in parallel and it typically contains more cores then a CPU [32].The original iPad uses the Apple A4 SOC which uses an ARM Cortex A8 processor and PowerVR

SGX535 for graphics processing [9, 11, 12]. PowerVR is a brand of graphics processors created by Imagination Technology for use in mobile platforms. The iPad 2 SOC is called the Apple A5 it contains a dual core PowerVR SGX543MP2 chip and a Cortex

A9 processor [13, 14, 17]. When looking at the naming of the PowerVR chips the SGX indicates a fifth series GPU, while the suffix MP identifies the chip as a multi-processor

[33]. The iPad 3 and 4 SOC’s are named the Apple A5X and Apple A6X both contain a quad-core GPU and a CPU based on the ARMv7-A architecture [14 - 18]. The Apple

A5X uses an ARM Cortex A9 processor while the Apple A6X uses processor called

Swift specifically designed by Apple [14, 15, 16]. A Study of Modern Mobile Tablets - 17

Figure 4 An image of the Tegra 3 system on a chip displaying its architecture.

Observations:

The first iPad was very basic with no camera, 256 MB of ram and the Apple A4 SOC.

With the second generation iPad it received upgrades to its SOC, RAM, and received a

front and back camera. The iPad 2 was upgraded to the Apple A5 with 512 MB of ram.

Each version of the iPad on average received a new SOC and RAM. With the 3rd iPad the

new retina display was incorporated resulting in a significant battery power increase.

Although the battery got larger the average running time stayed the same at about ten

hours. After the first iPad at least one camera was upgraded between each generation.

The 4th generation iPad was upgraded to a custom made SOC called Swift which was

based on the same ARM architecture as previous SOC’s. It also became pretty standard

for each iPad to include an Accelerometer, Ambient Light Sensor, and Gyroscope. A Study of Modern Mobile Tablets - 18

2.1.2. IPad Air Series: General Details:

The iPad Air and Air 2 are both considered part of the original iPad series. The iPad Air comes after the iPad 4. The iPad Air and Air 2 have many of the same qualities which can be seen in Appendix A, Table II [34- 41]. Figure 5 shows what the iPad Air and iPad

Air 2 look like [28]. Both versions of the iPad Air have a 9.7 inch retina display and currently support iOS 9.2 just like the iPad 4 [10, 34, 35]. The storage available for both the iPad Air 1 and Air 2 ranges from 16 GB to 128 GB [34, 35]. Apple increased the

RAM available from 1GB of DDR2 in the iPad 4 to 1GB of DDR3 [22, 40], with a further improvement to the Air 2 which contains 2GB of DDR3 [22]. Both systems have a 1.2 MP front camera and a back camera ranging from 5 MPs to 8 MPs [34, 35]. Similar to the other versions Wi-Fi and Bluetooth are present with the addition of the MIMO protocol. MIMO stands for multiple in multiple out, it uses multiple antennas to receive and send data which can increase network throughput [42]. Both iPad Air versions include the Wi-Fi digital compass and the iPad Air 2 added the iBeacon Micro location feature. The IBeacon feature can be used to pinpoint a devices location using the

Bluetooth protocol [43]. Using the Bluetooth low energy band iBeacon devices can broadcast their location, devices coming within range can be notified of their location relative to the broadcasting device [44]. The general idea is to provide a way to market and notify users that they have come into range of an iBeacon device. An example given is having a food truck running iBeacon when devices come within a range a notification is produced indicating that a truck is nearby [44]. The iPad Air like the iPad 4 includes an accelerometer, ambient light sensor and gyroscope [34]. A barometer and touch ID sensor were added to the iPad Air 2 [35]. The iPad Air was one of the first iPad’s to A Study of Modern Mobile Tablets - 19

receive a motion coprocessor called the Apple M7, while the Air 2 uses the Apple M8

motion coprocessor. The motion coprocessor is designed to continuously measure data

received from the accelerometer, gyroscope, barometer, GPS, and compass. A

Magnetometer is used to detect magnetic fields. Barometers are usually used to collect

information about atmospheric pressure. Creating a separate processor increases the

power efficiency of the SOC by offloading sensor calibration tasks to the motion

coprocessor [45].

Figure 5 Picture of the iPad Air and iPad Air 2 running IOS 9.

System on a Chip:

The SOC used by the iPad Air is the Apple A7, while the Air 2 uses the Apple A8X.

With the iPad 4 Apple started to move away from predesigned processors and started

creating their own designs. The iPad Air’s A7 SOC contains a CPU called Cyclone

which is based on an ARMv8-A architecture [16]. The integrated GPU is a PowerVR

G6430 which is from series 6 created by Imagination Technology [39, 46]. The iPad Air

2 SOC is made up of a processor called Typhoon, and a PowerVR GXA6850 [22, 38]. A Study of Modern Mobile Tablets - 20

Typhoon is another apple designed CPU based on ARMv8-A architecture, while it’s

GPU is a custom designed variant of the series 6XT [47].

Observations:

The iPad Air is technically still part of the iPad series of tablets. The 5th generation iPad follows the same path as previous models with an improved SOC and faster RAM. The iPad Air was the first device to introduce the motion coprocessor. Although the iPad Air still has the same retina display it was able to reduce its batter size by about 10 watt hours which is probably why it was slimmer and lighter. Neither cameras received an upgrade but the wireless technology MIMO was introduced. Next the iPad Air 2 was introduced which received an upgraded SOC, motion coprocessor, RAM, back camera, iBeacon, TouchID, and Barometer. Even with the added technology Apple was able to again reduce the battery size by 5 watt-hours compared to the iPad Air. Both iPad Air

SOC’s use ARM 8 architecture compared to the ARM 7 used in all previous models.

The iPad Airs had a custom designed processor called Cyclone and the iPad Air 2 was given Typhoon which was an enhanced Cyclone.

2.1.3. IPad Mini Series:

General Details:

The iPad Mini is a slightly smaller version of the standard iPad, the size was reduced to increase portability. The reduced size allows customers to carry the tablet easily because of its weight and display size. All of the hardware specification for the iPad Mini 1, 2, 3 and 4 are outlined in Appendix A, Table III [48 - 57]. Figure 6 [58] depicts every iPad A Study of Modern Mobile Tablets - 21

Mini running iOS 9. Every version of the iPad Mini has a 7.9 inch display the first generation is the only Mini without a retina display [48 - 51]. The first generation Mini has storage options from 16GB to 64GB while every other version offers up to 128GB

[48 - 51]. The amount of memory in the iPad Mini 1 is 512 MB of DDR2 RAM, just like the iPad 2 [53]. The reduction in size is probably the leading factor in the reduced memory considering that the iPad Mini was available the same year as the iPad 3 which received 1GB of RAM [20, 21]. The iPad Mini 2 and 3 both received 1GB of DDR3

RAM, while the Mini 4 gained another boost with 2GB of DDR3 [54 - 56]. The iPad

Minis all have a 1.2 MP front camera [48 - 51]. The iPad Mini 1, 2, and 3 all contain a 5

MP back camera with the Mini 4 getting an upgraded 8 MP camera [48 - 51]. Each iPad

Mini has Wi-Fi, and Bluetooth at a minimum, the iPad Mini 2 and 4 are also capable of using MIMO [48 - 51]. For geolocation services the each iPad Mini contains a Wi-Fi

Digital Compass, versions 3 and 4 have the addition of iBeacon just like the iPad Air 2.

The sensors available to the iPad Mini 1 and 2 include the accelerometer, ambient light sensor, and gyroscope [48 - 51]. The Mini 3 was upgraded to include Touch ID, while the Mini 4 received Touch ID and a Barometer. Touch ID is another form of password protection that uses a fingerprint to unlock Apple devices, or make purchases through the Apple App Store [59]. Touch ID requires a user to already have a password set on their device. The user must follow some setup steps which involves holding their finger over the home button [59]. Devices with Touch ID have a home button made from a clear sapphire crystal that protects the sensor and acts as its lens [60]. A steel ring surrounding the button detects a user’s finger taking a high resolution image from a small section of the finger print [60]. A mathematical representation of a users finger A Study of Modern Mobile Tablets - 22

print is stored for comparison, to identify a valid finger [60]. A motion coprocessor was

introduced in the iPad Mini 2, 3, and 4. The iPad Mini version 2 and 3 were developed

with the Apple M7, while the iPad Mini 4 received the upgraded Apple M8.

Figure 6 Picture of the iPad mini 1, 2, 3, and 4 running IOS 9.

System on a Chip:

The iPad Mini 1 was created using the Apple A5 SOC, which is the same SOC used by

the iPad 2. The iPad Mini 2 and 3 use the same SOC as the iPad Air 1. Lastly the iPad

Mini 4 received its own custom designed SOC called the Apple A8 which is similar to

the Apple A8X used by the iPad Air 2. The A8 contains a custom processor named

Typhoon designed by Apple, with a PowerVR GX6450 which is a slightly less powerful

version of the GXA6850 [38]. Apple probably reduced the GPUs capabilities to save on

power consumption and maintain the ten hour battery life advertised.

Observations:

The first iPad Mini came out at about the same time as the iPad 4. Although the retina

displays was available it was never added to the iPad mini. The iPad mini was also built

using the Apple A5 SOC the same one used by the iPad 2. In comparison the iPad mini A Study of Modern Mobile Tablets - 23

is nearly identical to the iPad 2. The major difference between them is that the iPad mini received a smaller screen, smaller battery, and better cameras. The iPad Mini 2 was released at the same time as the iPad Air. One difference between the first and second generation iPad Mini is that it received the retina display. The iPad Mini 2 is identical to the iPad Air the only difference between the two is that the iPad Mini 2 has a smaller screen, smaller battery, and weighs less. It would appear that the iPad Mini 2 is just the iPad Air in a smaller container. Looking at the iPad Mini 3 is again nearly identical to the iPad Air and iPad Mini 3. The only differences between the iPad Mini 3 and Mini 2 are the addition of the iBeacon and Touch ID technologies. Otherwise everything else is the same as the iPad Mini 2. Finally with the introduction of the iPad Mini 4 some significant changes occur. The iPad Mini 4 gets an upgraded SOC called the Apple A8 which is less powerful then the iPad Air 2’s A8X chip. The iPad Mini 4 was given 2GB of RAM, upgraded back camera, iBeacon, Touch ID, and Barometer. All these features were added yet the battery size was not increased and the device actually got lighter.

2.1.4. IPad Pro Series:

General Details:

There is currently only one iPad Pro version in production its details are shown in

Appendix A, Table IV [61 - 65]. The iPad Pro was advertised to offer desktop like performance and have one of the fastest CPU’s compared to other tablets [66]. The iPad

Pro has the largest screen of any iPad with a retina display of 12.9 inches [61]. An image of the iPad pro compared to previous versions can be seen in Figure 7 [58]. There are two storage options 32GB or 128GB most likely due to Apple trying to push the iPad A Study of Modern Mobile Tablets - 24

Pro as a desktop replacement [61]. The new iPad Pro received 4GB of DDR4 RAM

compared to the iPad Air 2 and iPad Mini 4 that contain only 2GB of DDR3 [22,56].

The iPad Pro would appear to combine all the upgrades from previous iPad series into

one large package. The front camera is 1.2 MP and the back camera is 8 MP [61].

Support is available for the most common wireless types such as Wi-Fi, Bluetooth, and

MIMO. The geo-location services offered include the Wi-Fi digital compass, and

iBeacon. Lastly it includes all the sensors like accelerometer, compass, gyroscope, touch

ID, and barometer.

Figure 7 Image of the iPad Pro compared to the iPad Air, iPad, and iPad mini.

System on a Chip:

The SOC appears to be where the iPad Pro has made most of its improvements. The

SOC is called the Apple A9X it includes a custom built Twister CPU based on ARMv8-

A architecture [22,63]. The iPad Pro is the only iPad using the new Twister CPU. In

addition the GPU being used is a modified PowerVR series 7 design which was A Study of Modern Mobile Tablets - 25

developed specifically for the iPad Pro [64]. Lastly the A9X SOC integrated the M9

motion coprocessor onto the same chip instead of as a separate one.

Observations:

The iPad Pro may become its own line of devices like the iPad and iPad Mini. It is the

only device using an Apple A9X SOC; it contains 4GB of RAM which is twice as much

as the iPad Mini 4 and iPad Air 2. The iPad Pro has every technology that was

incorporated into every other iPad generation. The iPad Pro could be thought of as the

most complete iPad yet.

2.2. Microsoft Devices

Microsoft has developed a number of mobile devices including a few different

generations of tablets. These tablets include the Surface 1 - 3, Surface Pro 1- 4, and the

Surface Book. Each version of the Surface tablet improves on a particular piece of

hardware. The Surface, Surface 2, and Surface 3 all use a System on a Chip each with a

different GPU and CPU. Each device was released approximately one year apart

occasionally in pairs as can be seen in Figure 8.

A Study of Modern Mobile Tablets - 26

Figure 8 A timeline of all the Microsoft Surface release dates starting from 2012 - 2015.

("Created by the author")

2.2.1. Surface Series:

General Details:

The first series of Microsoft Surface tablets included the Surface RT, Surface 2, and

Surface 3. The complete hardware specifications can be found in Appendix A, Table V

[67 - 83]. Windows RT 8.1 is currently the highest supported operating system for the

Surface RT and Surface 2. Figure 9 [67, 68] shows pictures of the Surface RT and

Surface 2 they are both similar looking. Windows RT is not supported by the Surface 3

instead Windows 10 is the highest supported OS. The first surface tablet was built with a

10.6 inch display, with a lower resolution then the surface 2 and surface 3 [67 - 69]. The

Surface 2 received a resolution increase but kept the same 10.6 inch display. The Surface

3 on the other hand kept the same resolution but received an upgraded screen of 10.8

inches it can be seen in Figure 10 [69]. To increase the clarity on devices with lower

resolutions Microsoft developed ClearType. ClearType improves the clarity and

smoothness of digital text or type [84]. To accomplish this ClearType chooses pixel

around the edge and modifies the brightness value of sub-pixels to blend jagged edges A Study of Modern Mobile Tablets - 27

into smooth shapes [84]. An example of how ClearType works can be seen in Figure 11

[84]. Looking at Figure 11 the first step depicts how the letter looks using its typeface outline, the second portion is the letter rendered to the screen without ClearType, lastly the same letter is rendered using ClearType [84]. From the third image in Figure 11 it is easy to notice the blurry sub pixels caused by reducing their brightness value. ClearType technology was made to work on current displays specifically LCD monitors, but it can provide improvements on CRT monitors [84]. The Surface RT and Surface 2 can be purchased with 32GB or 64GB of internal storage, while the Surface 3 options are either

64GB or 128GB [78, 79, 69]. Compared to early iPad versions the Surface series starts with more memory from the start. The Surface RT and Surface 2 both come with 2GB of

DDR3 RAM, in comparison the Surface 3 gets either 2GB or 4GB based on the amount of internal storage chosen [78, 79]. Each device contains a front and back camera the front camera is 3.5MP for all versions [80 - 82]. The back camera is different for the

Surface 3 with 8MP compared to the Surface RT and Surface 2’s 5MP [81, 82]. The wireless technology supported by all devices includes Wi-Fi and Bluetooth [67 - 69].

The Surface 2 was the only device in this series to receive a digital compass. Each device has an ambient light sensor, accelerometer, gyroscope, and magnetometer. The

Surface 2 continues to be unique with the addition of a proximity sensor. A Study of Modern Mobile Tablets - 28

Figure 9 Picture of the Surface RT and Surface 2.

Figure 10 Picture of the Surface 3 showing available ports and kickstand. A Study of Modern Mobile Tablets - 29

Figure 11 How ClearType technology increases digital type clarity.

System on a Chip:

The original Surface RT was created to utilize the NVIDIA Tegra 3 SOC. The Tegra 3 is

designed around an ARM Cortex A9 processor based on the ARMv7-A architecture [14,

31]. Included within the Tegra 3 is a Geforce Ultra Low Power (ULP) GPU which is

based on the Tegra 2, but with the addition of four extra cores for a total of twelve [85,

86]. The Surface 2 following the same route integrated the NVIDIA Tegra 4 SOC. The

Tegra 4 utilizes four ARM Cortex-A15 processors based on the ARMv7 architecture [74

- 76]. The GPU is a further modified Geforce ULP chip with seventy-two cores which is

six times more than the Tegra 3[31, 75]. The last device in this series is the Surface 3

which reversed the direction from ARM based SOC’s to an Intel Atom x7-Z8700. Within

the Intel Atom SOC is a quad core Atom x7-Z8700 processor based on Intel’s Airmont A Study of Modern Mobile Tablets - 30

architecture [77,87]. The GPU is based on Intel’s generation eight HD graphics which is integrated and designed for low power systems [88].

Observations:

The original Surface tablet was released around the same time as the iPad 3. However it has a lower resolution then most iPad devices. The surface RT runs Windows RT which has received a lot of negative reviews because of its inability to run desktop applications.

The Surface RT is the base for all other versions to improve upon. The Surface 2 received a better resolution screen, and an updated SOC. It was also the first device to add a proximity sensor, and digital compass. However other then these minor improvements nothing else changed. The Surface 3 was the first device to move away from an ARM based SOC instead an Atom SOC was used. The change to an Intel based SOC was probably due to the negative reception of Windows RT. With the new Intel based system it was possible to install Windows 10. Other then the improved SOC only the back camera received an upgrade.

2.2.2. Surface Pro Series:

General Details:

Microsoft’s second series of tablets are known as the Surface Pro from 1 to 4. Details about each Surface Pro device and their hardware can be found in Appendix A, Table VI

[89 - 112]. Each device is capable of running Windows 10 [73]. Figure 12 [113] shows what the Surface Pro looks like while Figure 13 shows the Surface Pro 2 [114]. The

Surface Pro 1 and 2 both come with a 10.6 inch display. The Pro 3 was upgraded to 12 A Study of Modern Mobile Tablets - 31

inches, while version 4 received a 12.3 inch display [91, 92]. Images of the Surface Pro 3 and 4 can be seen in Figure 14 [115, 92].Each Surface Pro’s RAM is determined based on the hard drive size chosen [89 - 92]. The first generation of Surface Pro could only have

64 or 128 GB of storage with a corresponding 4GB of DDR3 RAM [89]. The second and third generation can be purchases with 64, 128, 256, or 512GB of storage [89, 100]. The available RAM is either 4GB or 8GB of DDR3 for a 128GB or smaller drive 4GB is assigned, while a size of 256 or greater gives 8GB [89, 100]. Options available for the

Surface Pro 4 include 128, 256, 512, and 1024GB of storage [92, 100]. The total RAM available is 4 GB, 8GB, or 16GB of DDR3. A storage capacity of 512 or 1024GB always receives 16GB of RAM, while a size of 256GB gives the purchaser the choice of 8GB or

16GB. If a hard drive of 128GB is chosen it is limited to only 4GB of RAM [92, 100].

The first two generations of Surface Pro were equipped with a 1.2MP camera on the front and back [89, 90, 100]. With the introduction of the Surface Pro 3 a 5.0MP front and back camera was added [109]. The last version received an upgraded back camera from

5MP to 8MP, while the front stayed at 5MP [92]. Mobile networking technologies like

Wi-Fi and Bluetooth are supported by every Surface Pro device. The last thing to look at is the sensors available each device includes an ambient light sensor, accelerometer, gyroscope, and magnetometer [89 - 92]. A Study of Modern Mobile Tablets - 32

Figure 12 Picture of the Surface Pro and some of its controls, and features.

Figure 13 Picture of the Surface Pro 2 from Microsoft. A Study of Modern Mobile Tablets - 33

Figure 14 Pictures of what the Surface Pro 3 and Surface Pro 4 look like.

CPU and GPU:

The Surface Pro series were the first tablets from Microsoft where an SOC was not used

instead the graphics are provided by the CPU. The Surface Pro has an Intel i5-3317U

CPU with a speed between 1.7GHz and 2.6GHz [96, 97]. The Intel i5-3317U is based on

Intel’s 3rd Generation architecture which includes an Intel HD Graphics 4000 GPU [96].

The Surface Pro 2 can have an Intel i5-4200U, or an Intel i5-4300U processor designed

using the 4th Generation Intel architecture. The Intel i5-4200U can run between 1.6GHz

and 2.6GHz, while the Intel i5-4300U has a frequency of 1.9GHz to 2.9GHz [96, 98,

102]. In addition the integrated GPU is an Intel HD Graphics 4400 chip [96]. Three

processors are available for the Surface Pro 3 and each has their own GPU. The Surface

Pro 3 can have one of three different CPUS based on Intel’s 4th Generation architecture.

The slowest CPU available is the Intel i3-4020Y which has a speed of 1.5GHz, and an

Intel HD Graphics 4200 GPU [96, 99, 106]. The next step up is an Intel i5-4300U A Study of Modern Mobile Tablets - 34

processor using the Intel HD Graphics 4400 GPU, which is the same CPU available to the Surface Pro 2 [96, 102, 107]. The last option is an Intel i7-4650U CPU running between 1.7GHz and 3.3GHz paired with an Intel HD Graphics 5000 GPU [96, 104,

108]. The Surface Pro 4 also has three CPU options modeled after Intel’s 6th Generation including the m3, i5, and i7. The first option available is an Intel m3-6Y30 with a speed of 0.9GHz up to 2.2GHz, combined with an Intel HD Graphics 515 GPU [100, 101].

Next is an Intel i5-6300U processor starting at 2.4GHz and maxing out at 3.0GHz, paired with an integrated Intel HD Graphics 520 GPU [79, 100, 103]. The only other choice is an Intel i7-6650U CPU with a clock speed of 2.2GHz reaching up to 3.4GHz with an Intel Iris Graphics 540 GPU [100, 105]. The Surface Pro 4 is currently the only device that uses the Iris Graphics GPU series.

Observations:

Once the Surface devices moved away from the ARM based SOC it was possible to offer more processor varieties to users. With the introduction of the Surface Pro Microsoft completely removed the SOC. Instead they opted to use Intel processors with integrated graphics. The Surface Pro was upgraded to use an Intel Core i5 processor and received an increase in RAM. The Surface Pro 2 also uses an Intel Core i5 processor but two options are provided. In addition more storage and RAM options were provided to the user. The cameras in the Surface Pro series were downgraded when compared to the Surface line.

With the Surface Pro 3 even more choices were provided to user an i3, i5, or i7 processor could be chosen. Depending on the processor chosen the integrated graphics would change as well. This means that if a user wants to run graphic intensive applications the A Study of Modern Mobile Tablets - 35

higher end processor would be a good choice. Finally the Surface Pro received an upgraded front and back camera from 1.2 MP to 5.0 MP. In addition the Surface Pro 3 has a 12 inch screen compared to the Surface Pro 2’s 10.6 inch screen. Microsoft also appears to keep the battery size very consistent across all models. Lastly the Surface Pro

4 was given a 12.3 inch screen resulting in a larger resolution. A user can choose between an m3, i5, or i7 processor. The last improvement was an upgraded back camera from 5

MP to 8 MP.

2.2.3. Surface Book Series:

General Details:

The Surface Book is unique because it is both a laptop and tablet. The tablet acts as the laptops screen and can be removed while also providing touch capabilities. There is currently only one version of the Surface Book and its specifications are outlined in

Appendix A, Table VII [116 - 119]. A picture of the hybrid Surface Book can be seen in

Figure 15 [116].The highest currently supported operating system for the Surface Book is Windows 10 [73]. The tablet acts as the laptop screen and can be undocked from the base [95]. The tablet has a 13.5 inch screen with a resolution of 3000 x 2000 which is the largest resolution available for Microsoft’s tablets [95]. There is an increased amount of choice when it comes to storage and memory in the Book. The Surface Book can be purchased with 128, 256, 512, or 1024 GB of hard drive space [95]. Unlike other

Microsoft tablets the Book, can have either 8GB or 16GB of memory no matter what hard drive size is chosen [95]. There is a front camera with 5MP and a back camera with

8MP just like the Surface Pro 4 [95]. Just like every other Surface Series Bluetooth and A Study of Modern Mobile Tablets - 36

Wi-Fi are the available wireless capabilities. Included with the Surface Book are the

following sensors an ambient light sensor, accelerometer, gyroscope, and magnetometer

[95].

Figure 15 Pictures of what the Surface Book looks like the screen is a removable tablet.

CPU and GPU:

The Surface Book has two different CPU choices based on Intel’s 6th Generation

architecture they include the Intel Core i5-6300U or Intel Core i7-6600U [103, 117,118].

Both CPU’s contain the same integrated Intel HD Graphics 520 GPU [103, 117,118]. An

optional NVIDIA Geforce GPU with 1GB of GDDR5 RAM can be bought with the

Surface Book’s base [95, 117]. This allows the Surface Book to accomplish more

graphic intensive tasks then if it was to rely upon the CPU’s integrated graphics alone. If A Study of Modern Mobile Tablets - 37

the tablet is undocked from the laptop base it will switch to using Intel’s integrated graphics.

Observations:

The Surface Book is kind of like the iPad Pro it is a larger version of the Surface tablets.

The Surface Book is half laptop and half tablet. The Surface Book has the largest display size of 13.5 inches and a resolution that is better than any iPad available. For processors only two choices are given an i5 or i7 processor. Both processors have the same integrated graphics. To enable graphic intensive applications a custom GPU can be purchased that is used when the tablet is attached to the laptop base. Another feature is that the RAM available is not tied to the amount of storage purchased. Previous Surface products could only get more RAM if more storage was also purchased. The Surface

Book has most of the same features as the Surface Pro 4 including camera, sensors, and wireless technology. The Surface Book is very different because of its dual purpose it is both a tablet and laptop.

A Study of Modern Mobile Tablets - 38

Chapter Three: Programming Languages

3.1. Objective C

3.2. C-Sharp

3.3. Comparison

3.4. Development

3.1. Objective C

Brief History:

Apple uses a superset of ANSI C called Objective-C [120]. Objective-C is the main

language used for writing most Apple applications. Objective-C provides object-oriented

properties to the C programming language. The syntax, primitives, and control

statements are all the same. However Objective-C defines a new syntax for classes and

methods. Objective-C was originally developed by Brad Cox and Tom Love for the

company Stepstone in the early 1980s [121]. Next Computers started developing the

NeXTStep framework that Apples Cocoa is based on [121]. Apple then purchased Next

Software for four hundred million dollars in 1996 [122]. Cocoa is a collection of object-

oriented libraries, runtimes, and integrated development environment [120]. Cocoa has

two main frameworks for OSX and IOS. OSX uses the Foundation and AppKit libraries

while IOS uses Foundation and UIKit libraries [120]. When declaring arrays in

Objective-C a collection class is used such as NSArray, NSSet, or NSDictionary. This is

a significant difference when compared to the C language that Objective-C is based A Study of Modern Mobile Tablets - 39

upon, while it is possible to create arrays similar to ANSI C [123]. If a data type starts with the NS prefix it indicates that it was originally created by NeXTStep.

Garbage Collection:

Garbage collection is an important part of almost every programming language.

Objective-C uses a form of Automatic Reference Counting (ARC) which provides automatic memory management through the compiler [124]. The original garbage collection libraries were deprecated to be replaced with ARC [124]. In Objective-C variables are given qualifier names of either strong, weak, unsafe_unretained, or auto releasing [124]. By default when a variable is created and no property is set it is assigned the strong property [124]. Strong keeps an object alive as long as a strong pointer is pointing to it [124]. Weak is a reference that does not keep an object alive, when no strong pointer is pointing to the object it is set to nil [124]. Nil is objective-C’s versions of Null, just like Self is Objective-C’s version of This. Unsafe_unretained is like the weak property but the object is not set to Nil which could result in dangling pointers

[124]. Auto releasing is used to note arguments that are passed by reference and auto released when they are returned [124]. ARC works by examining variable and class lifetimes based on the qualifiers given ARC then adds memory management calls at compile time [124].

Object Oriented

Objective C although built on top of ANSI C is an object oriented language. One benefit of Objective-C is that existing C applications can be ported to run using Objective-C A Study of Modern Mobile Tablets - 40

frameworks [121]. Objective-C is considered very dynamic because it uses dynamic

typing, binding, and loading [120]. Objective-C’s dynamic typing determines an objects

class at runtime [120]. Dynamic binding is used to determine the methods that can be

invoked at runtime [120]. Lastly dynamic loading allows new modules to be added at

runtime [120]. An example of dynamic typing can be seen in Figure 16 the method

(IBAction)resetAccelerometer:(id)sender uses the generic object type called (id) [120].

“The id data type makes it possible to substitute any type of object at runtime.” [120].

Figure 16 The AccelerometerViewController class shows ARC properties weak and uses

(id) which is an example of dynamic typing.

Dynamic binding works by binding method invocations only when a message is

delivered to a method. During runtime a message dispatcher is used to create dynamic

binding [120]. When a message is sent to an object its Isa pointer locates the appropriate

class once the class is found the method is invoked [120]. The Isa pointer points to an A Study of Modern Mobile Tablets - 41

objects class which was compiled from its class definition [120]. Dynamic loading

allows a program to load code and assets as needed instead of loading everything at the

beginning [120].

3.2. C-Sharp

General Information

Microsoft created a language inspired by C called C-Sharp it however is not a derivative

of C. C-Sharp version 1.0 was originally released in 2002 the most current version is C#

6.0 released in 2015 [126]. C-Sharp supports unsafe code, or code that runs outside of

the common language runtime. It allows pointers to reference specific locations in

memory; however these pointers must be pinned to prevent the garbage collector from

altering their location. Thread synchronization constructs for C-Sharp include, lock,

monitor, mutex, and interlock. C-Sharp has a problem with priority inversion, in which a

lower priority thread blocks a higher priority thread possibly resulting in starvation.

Unlike Java which runs in a virtual machine C-Sharp can gain information about the

systems CPU and memory [127]. C-Sharp is able to call the Win32 API to obtain system

performance counters, CPU characteristics, memory usage at both the machine and

process level. When exceptions occur within a C-Sharp program an exception object is

created allowing developers to extend an error message based on an application. Type

safety is a key feature of C-Sharp, any program errors are caught at compile time while

also catching errors during runtime. Type safety ensures that objects are always

allocated and accessed in appropriate ways [127].

A Study of Modern Mobile Tablets - 42

Garbage Collection

C-Sharp uses the .Net garbage collector to manage the allocation and deallocation of

memory [128]. New objects are created and added to the heap as long as memory is

available. If no memory is available to garbage collector must free up some space. The

garbage collector provides the ability to write applications without worrying about

memory allocation and deallocation [128]. Garbage collection occurs when the system

has low physical memory, allocated objects on the heap passes a specific limit, or the

garbage collector is called by the program [129]. When the garbage collection is started

the collector reclaims memory associated with dead objects [129]. The garbage

collectors heap is actually two heaps the large and small heap. The large heap is for

objects with very large sizes such as arrays [129]. The garbage collection has three main

phases marking, relocating, and compacting. During the marking phase a list is created

of all the living objects or objects with a reference. The relocation phase updates the

references to any objects that need to be compacted. Lastly the compacting phase

reclaims dead object space and moves live objects to the top of the heap [129].

3.3. Comparison

In this section some example code will be outlined to compare objective-c and c-sharp.

Six applications were written to help demonstrate and research application development

for both platforms. The first program that will be examined is the AccelerometerTest

application. Figure 17 shows the C-Sharp code for the stop accelerometer method that is

executed when the stop button is pressed. Figure 18 shows the Objective-C code that is

run when its stop button is pressed. The C-Sharp code was written to include a boolean A Study of Modern Mobile Tablets - 43

condition to check if a button had already been pressed, because of how event handlers

are attached. If no boolean value was used then every time a user pressed the start or

stop button an event handler would be added or removed. For example if the user

pressed the start button three times then three TypedEventHandlers would be added to

ReadingChanged. The result of this is that the user would need to press the stop button

three times as well. This bug does not occur in objective-c making the

stopAccelerometer method extremely simple as can be seen in Figure 18.

private void StopAccelerometer(object sender, RoutedEventArgs e) { if (startPressed == true) { startPressed = false; accelerometer.ReadingChanged -= new TypedEventHandler(AccelerometerChanged); accelerometer.ReportInterval = 0; } } Figure 17 C# stop accelerometer method from accelerometerTest class

-(IBAction)stopAccelerometer:(id)sender { [self.motionManager stopAccelerometerUpdates]; } Figure 18 Objective-C stop accelerometer method from the accelerometerTest class.

The startAccelerometer method attaches a TypedEventHandler using the Accelerometer

which sends data to the AccelerometerChanged method as seen in Figure 19. The

accelerometer reading only changes when the device is actually being moved it does not

update while stationary. A check must also be done to determine if an accelerometer

sensor exists if not then it will be null. In C# the start and stop methods are almost

identical adding and subtracting event handlers. Objective C uses a CMMotionManager

class that has methods for accessing sensor data called updateToQueue. If no sensors are

available and CMMotionManager is called the system will crash. In both applications an

event handler is used to update the UI labels. Figure 20 shows the objective c code A Study of Modern Mobile Tablets - 44

needed to retrieve accelerometer data. Once data is retrieved by the queue the inner

block of code is executed which calls two methods setLabel and checkMaximum. In

Figure 19 the AccelerometerChanged method is called which is outlined in Figure 21.

The AccelerometerChanged also calls two methods to setLabels and checkMaximum

values.

private void StartAccelerometer(object sender, RoutedEventArgs e) { if (accelerometer != null && startPressed == false) { startPressed = true; accelerometer.ReportInterval = interval; accelerometer.ReadingChanged += new TypedEventHandler(AccelerometerChanged); } } Figure 19 The StartAccelerometer method which adds an event handler.

-(IBAction)startAccelerometer:(id)sender { //Create a queue of accelerometerData which can be retrieved [self.motionManager startAccelerometerUpdatesToQueue:[NSOperationQueue currentQueue] withHandler:^(CMAccelerometerData *accelerometerData, NSError *error) { //pass the acceleration.x y and z values into the setLabel method. [self setLabel_X:accelerometerData.acceleration.x Label_Y:accelerometerData.acceleration.y Label_Z:accelerometerData.acceleration.z]; //pass the acceleration.x y and z values into the checkMaximum method to set the maximum amount of acceleration [self checkMaximumValue_CurrentX:accelerometerData.acceleration.x CurrentY:accelerometerData.acceleration.y CurrentZ:accelerometerData.acceleration.z]; //If an error occurs at any point while the accelerometer is trying to retrieve data write it out to the console. if (error) { NSLog(@"%@", error); } } ]; }

Figure 20 The StartAccelerometer method which updates accelerometer data using a

block.

Both languages update labels in a similar fashion making direct reference to the labels

that need to be modified. For example self.xLabel.text is the same as xLabel.Text in

addition both labels require that a formatted string be added. The syntax for the

formatted strings look different but they both show the same data. When the label is A Study of Modern Mobile Tablets - 45

displayed it includes two decimal places and a sign value such as positive or negative.

One big difference in implementing accelerometer updates was that the

AccelerometerChanged method needed to be asynchronous. Objective-C uses the queue

to retrieve data from the sensors independently while C-Sharp requires that a separate

thread be started to update the accelerometer values. If it is not done this way the user

interface will not run and respond smoothly. Figure 21 shows how to create an

asynchronous method, which must implement the await keyword and assign a

dispatcher.

async private void AccelerometerChanged(object sender, AccelerometerReadingChangedEventArgs e) { //unload the acceleration readings to another thread await Dispatcher.RunAsync(CoreDispatcherPriority.Normal, () => { //call update labels and update max with the acceleration values SetLabels(e.Reading.AccelerationX, e.Reading.AccelerationY, e.Reading.AccelerationZ); CheckMaximumValue(e.Reading.AccelerationX, e.Reading.AccelerationY, e.Reading.AccelerationZ); }); } Figure 21 AccelerometerChanged is used to update all the different labels.

The set label method’s in Figure 22 are very simple and needs little explanation. When a

call is made to the method the corresponding user interface labels are updated with the

double values.

-(void)setLabel_X:(double)x Label_Y:(double)y Label_Z:(double)z { //set the text displayed by the labels to the NSString object self.xLabel.text = [NSString stringWithFormat:@"Accelerometer X: %+0.2f",x]; self.yLabel.text = [NSString stringWithFormat:@"Accelerometer Y: %+0.2f",y]; self.zLabel.text = [NSString stringWithFormat:@"Accelerometer Z: %+0.2f",z]; }

private void SetLabels(double x, double y, double z) { xLabel.Text = String.Format("Accelerometer X: {0,5:+0.00;-0.00}", x); yLabel.Text = String.Format("Accelerometer Y: {0,5:+0.00;-0.00}", y); zLabel.Text = String.Format("Accelerometer Z: {0,5:+0.00;-0.00}", z); }

A Study of Modern Mobile Tablets - 46

Figure 22 The methods used to update labels the first is objective c and the second is

c-sharp.

The checkMaximumValues methods shown in Figure 23 are similar to the setLabels

method. One of the key differences is that the maximum value method must determine the

absolute value of a double. The absolute value is required because depending on the

direction of the accelerometer it can be negative or positive. Objective c uses the fabs()

method and C-Sharp uses Math.Abs() to retrieve the absolute value.

-(void)checkMaximumValue_CurrentX:(double)x CurrentY:(double)y CurrentZ:(double)z { if(fabs(currentX) <= fabs(x)) { currentX = x; self.xMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f",x]; } if(fabs(currentY) <= fabs(y)) { currentY = y; self.yMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f",y]; } if (fabs(currentZ) <= fabs(z)) { currentZ = z; self.zMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f",z]; } } private void CheckMaximumValue(double x, double y, double z) { if(Math.Abs(currentX) <= Math.Abs(x)) { currentX = x; xMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", x); } if (Math.Abs(currentY) <= Math.Abs(y)) { currentY = y; yMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", y); } if (Math.Abs(currentZ) <= Math.Abs(z)) { currentZ = z; zMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", z); } } Figure 23 The checkMaximumValue method that updates the max labels based on

the old current value and the new one being checked.

A Study of Modern Mobile Tablets - 47

The last thing to look at is the resetAccelerometer methods. The reset method sets the

current double values to 0.0 and then calls setLabel, and checkMaximumValues as seen

in Figure 24.

//Reset the accelerometer and max labels and reset the max values to zero -(IBAction)resetAccelerometer:(id)sender { //reset current maximum values currentX = 0.0; currentY = 0.0; currentZ = 0.0; //call setLabel so the all the Accelerometer X: , Accelerometer Y: , Accelerometer Z: labels are set to +0.0 [self setLabel_X: currentX Label_Y: currentY Label_Z: currentZ]; //call checkMaximumValue_CurrentX so the all the Max: labels are set to +0.0 [self checkMaximumValue_CurrentX: currentX CurrentY: currentY CurrentZ: currentZ]; }

private void ResetAccelerometer(object sender, RoutedEventArgs e) { //reset the current max values to 0 currentX = 0.0; currentY = 0.0; currentZ = 0.0; //update the max values CheckMaximumValue(currentX, currentY, currentZ); //update the accelerometer labels SetLabels(currentX, currentY, currentZ); }

Figure 24 ResetAccelerometer method is used to reset all the user interface labels

back to zero.

The layout for the gyroscopeTest application is also nearly identical however instead of

using the accelerometer class the gyroscope is used. The full source code is available in

Appendix C including the XAML code necessary to recreate the user interfaces.

3.4. Development

3.4.1. Apple

Developing applications for Apple requires that the developer has access to a

computer running OSX. Apple has developed its own integrated development A Study of Modern Mobile Tablets - 48

environment called Xcode. Xcode version 7.3 is the most recent stable release and

can be run on OSX 10.11 called El Capitan [130, 131]. Xcode 7.3 can be used to

produce applications for the following operating systems IOS 9.3, OSX 10.11.4,

WatchOS 2.2, and tvOS 9.2 [131]. The earliest Xcode version that can be

downloaded is 4 which can be installed on OSX 10.6.3 known as Snow Leopard

[132]. Xcode 4 can be used to implement IOS 3.2 and OSX 10.5. The Xcode editor

is broken into five different areas as seen in Figure 25 [133].

Figure 25 The Xcode IDE showing the different areas and controls.

A Study of Modern Mobile Tablets - 49

The navigator area is used to move between files that are displayed in the editor

area. If an objective c file is selected it can be directly edited within the editor area.

In addition if a storyboard is selected then a storyboard view will appear in the

editor area. Once the storyboard is loaded controls can be dragged onto the different

views or new views can be added. A blank storyboard file and some controls that

could be added to the view are displayed in Figure 26.

Figure 26 An example of a storyboard view and some controls that can be added.

(“Screenshot from author”)

To attach controls to source code the developer can open the assistance editor and drag

the control to the code as seen in Figure 27 [134]. The developer can also drag the control

to an already existing method as long as the return type is an IBAction. A Study of Modern Mobile Tablets - 50

Figure 27 An example of a control being attached to the code using the assistance

editor on the right and storyboard editor on the left.

The result of hooking the control to the code is an empty method that can be filled with

whatever the developer wishes. Images, effects, 3D models, and data should all be placed

in the Assets folder so they can be accessed in the storyboard editor. The Asset folder is

also used to create sets of icon that will act as the application image for each of the target

devices or operating systems. It is relatively simple to test and side load applications

using Xcode. A developer can test an application using the Xcode simulator which allows

a developer to simulate their project on a few supported devices. The Xcode 7 device

simulators are shown in Figure 28 they include iPad, iPhone, and Apple TV systems.

A Study of Modern Mobile Tablets - 51

Figure 28 An image of the simulators available in Xcode 7.3 devices shows the Mac

being used. (“Screenshot from author”)

To facilitate side loading an application on a device the developer requires a team be

assigned within the Xcode project page as seen in Figure 29. To side load an application

three things must be present. First a device must be connected to the Mac being used for

development. Secondly the developer must have an Apple Developer Account that is

validated and connected to the current project. Lastly the device must be provisioned for

development. In general these three steps are accomplished using Xcode [135]. When a

new project is created the general settings in the project page must be modified. The team

dropdown by default does not contain any users. The developer must sign into their

Apple ID account for it to be added to the team list. The developer then selects the

appropriate team and can attach a device such as the iPad. Once the iPad is attached a

message will appear asking if the computer is a trusted device. If the developer agrees

that it is a trusted device it will appear under devices as seen in Figure 28. When the

developer goes to test their application while the device is attached the program will be

pushed to the connected system. The application will then be built, installed, and started

on the device. While the device is connected any errors will be output to the debug

section as seen in Figure 25. The project page can also be used to set the desired target

system, application capabilities, resource tags, build settings, and info.plist. A Study of Modern Mobile Tablets - 52

Figure 29 The project settings page which allows the developer to set important

details like the developer account, operating system version, and target

devices. (“Screenshot from author”)

Most of the information in the general tab is setup when the developer creates the initial

project. The information is filled out based on a few different message dialogs presented

to the developer [136]. The general page can be modified to change the initial decisions

made at project creation. The capabilities tab is used to add different Apple technologies

to the device so they can be used in development. An example of some of the

technologies can be seen in Figure 30 [136]. The capabilities available for a project are

determined by the target operating system IOS, OSX, WatchOS, and tvOS applications

have different choices. A Study of Modern Mobile Tablets - 53

Figure 30 The capabilities tab in the project page showing different Apple

technologies that can be merged into an IOS application.

The capabilities offered are similar to interfaces, drivers, or plugins they provide an easy

way to integrate additional functionality. For example the tvOS operating system contains

a game controller capability which provides controls and actions that can be triggered by

a controller. When capabilities are added Xcode automatically imports the required

framework and adds it to the projects. The frameworks and dependencies are added to the

entitlements and info.plist [137]. The resource tag tab is used to provide on-demand

content for applications when requested. Resource tags allow a program to host files

online and download them when required instead of bundling them with the application

[136]. The benefits include smaller app sizes, lazy loading, remote storage of rarely used

items and in-app purchases [138]. Resource tags can be stored locally however if too A Study of Modern Mobile Tablets - 54

many tags exist on the device then the system will start removing tags with low priorities

[139]. Priorities can be set when a tag is created in-app purchases often have higher priorities then other content. Tags must have varying levels of priority if every tag has the same priority the system will remove one at random [139]. The build settings, phase, and rules tab are almost never modified directly by the developer. These settings are modified by Xcode when a developer selects a specific target platform [136]. The last section to examine is the info tab which directly corresponds with the info.plist file created with any default project. The info.plist is used by the application to indicate the icons, entry storyboard, device orientations, localization, and device capabilities as seen in Figure 31

[136]. Xcode is a very easy to learn integrated development environment with almost everything required built in. There is almost no reason that a developer would need to use another program to design or implement an application targeting IOS, OSX, WatchOS, or tvOS. Once a developer has learned how to use Xcode it would be very easy to implement an application for any of the operating systems.

A Study of Modern Mobile Tablets - 55

Figure 31 The info tab for a demo application created by Apple showing what is

contained in the info.plist file.

One small issue however is that to really utilize Xcode a developer must keep their

system updated. It is harder to create an application for example using Xcode 4, because

it does not support the most current operating systems. Xcode does have a slight learning

curve but is very intuitive. Storyboards are an excellent way to show how an application

flows and how views are connected. Side loading an application is much more convenient

when compared to alternatives like android and windows. The programmer must simply

setup their development team and attach a physical device. Once attached the developer A Study of Modern Mobile Tablets - 56

can select start and the application will be loaded and run on the device. If any errors are

encountered Xcode can offer solutions or attempt to fix them so testing can begin.

3.4.2. Microsoft

Developing applications for the Surface requires that the developer has access to a

computer running Windows 8. Microsoft uses their popular Visual Studio integrated

development environment. The most current version supported is Visual Studio

2015 which allows developers to create Windows 8.1, Windows 10, and Windows

Phone 8 applications [140]. To develop Windows Store apps, Universal apps, or

Windows Phone apps Visual Studio’s must be installed on a machine running

Windows 8 or higher. Visual Studio 2012 is the lowest version available that can be

used to create Windows Store and Windows Phone applications [141]. Visual

Studio 2012 is broken into six sections that are shown in Figure 32.

Figure 32 Visual Studio’s 2012 development environment.

(“Screenshot from author”) A Study of Modern Mobile Tablets - 57

The editor area changes based on the type of file being manipulated. Visual Studio

uses an Extensible Application Markup Language (XAML) which is pronounced

zammel [142]. XAML is a markup language developed by Microsoft to represent

the visual style of Windows applications [142]. When a developer opens a XAML

file the editor area changes to become the design editor which is depicted in Figure

33.

Figure 33 Visual Studio 2012 editing a XAML file on the left is a toolbox that can

be used to add controls into the design area. Underneath the design area is

the XAML code generated by adding controls. (“Screenshot from author”)

To access controls added into the designer each control must be given a name in the

properties area. Once a name is given it can be directly referenced in whatever

language was chosen such as C-Sharp, C++, or JavaScript. When writing code the A Study of Modern Mobile Tablets - 58

names of controls are added to the intellisense system. The properties area is also

used to specify action listener for interactable controls as seen in Figure 34. The

developer can choose to use the properties editor or write the XAML code by hand.

The properties that were set in Figure 34 include a name, and event handler the

corresponding XAML code is in Figure 35.

Figure 34 What the properties area looks like when a button is created using the designer.

The left picture represents the properties of the control while the right picture

represents the event handlers available. (“Screenshot from author”)

HorizontalAlignment="Stretch" VerticalAlignment="Top" Height="60" Click="StopGyroscope"/>

Figure 35 XAML code corresponding with Figure 34’s properties. (“Screenshot from

author”)

A Study of Modern Mobile Tablets - 59

During various testing it was found that using a combination of the property area and editing the XAML by hand was the simplest approach. When the XAML code is edited by hand it is immediately updated in the designer. If pictures are to be added to the application they must first be imported into the Assets directory. The

Asset directory is created by default when a new Windows Store project is created.

If the project will contain multiple types of assets then subdirectories can be created for organization purposes. All assets should be stored in the Asset directory because that is where Visual Studios looks first. Unlike Xcode Visual Studios does not combine application icons into its own image set instead they are all separate files.

The icon and splash screen images must be set within the app.manifest page.

Another significant difference is how the splash screens are done. Xcode uses a separate storyboard that can be modified to display a start-up screen. In comparison a Windows Store app uses an image. It is much easier to make changes to a storyboard then it is to open up a photo editor, modify the image, save it, and import it into Visual Studio. It is also more cumbersome to try and test an application on a supported device. The Surface 2 was used for testing a simple application in order to test the application on the device it had to be built into an App Package. To create an App Package go to the Project tab in the toolbar, and then proceed to the

Store dropdown shown in Figure 36. A Study of Modern Mobile Tablets - 60

Figure 36 The Project dropdown menu and Store dropdown menu.

(“Screenshot from author”)

Once the Store dropdown opens the developer must register their current operating

system by selecting Acquire Developer License. Once the developer begins the

process they will be accessed to sign into their developer account as seen in Figure

37.

Figure 37 The three dialogs that appear when registering an operating system with a

developer account. (“Screenshot from author”)

A Study of Modern Mobile Tablets - 61

When the process has finished the operating system has the required certificates so that App Packages can be signed and tested on a personal device. At this point the application can be run on the local computer because it has a developer certificate.

To test the application on the Surface 2 a developer certificate also needs to be registered. To register the Surface 2 for side loading an administrator must open power shell and run the command “Show-WindowsDeveloperLicenseRegistration”

[143]. Once this command is run the same dialogs as in Figure 37 will be presented to the developer. After the developer license is setup the App Package can be copied to the device. When the App Package has been copied it needs to be opened and a certificate needs to be installed as seen in Figure 38. The certificate file needs to be opened and Install Certificate needs to be pressed. Next the certificate should be installed to the local machine because it will be installed as the administrator.

The certificate must then be added to the TrustedRoot Certification Authorities group. Finally the developer can select finish which results in the certificate being added to the system.

A Study of Modern Mobile Tablets - 62

Figure 38 These are the steps required to install an App Package to a personal

device. (“Screenshot from author”)

Once the certificate is installed the developer can right click the Add-

AppDevPackage file and run using powershell. This script installs the application to

the current device where it can be run using the start menu. It is easy to see that side

loading an application using Xcode is much simpler than its windows alternative.

To setup project specific settings the package.appxmanifest is used. The

package.appxmanifest consists of four different tabs Application UI, Capabilities,

Declarations, and Packaging [144]. The Application UI tab is used to set your

applications display name, languages, orientation, and image assets. Figure 39

shows most of the available fields in the Application UI tab. A Study of Modern Mobile Tablets - 63

Figure 39 The Application UI tab for the SensorApplication.

(“Screenshot from author”)

The Capabilities tab is used to specify what system features an application can use

as seen in Figure 40. The capabilities indicate to the user what system access the

application requires. For example if Music Library is selected the application can

read and write information to the operating systems music folder [145]. A Study of Modern Mobile Tablets - 64

Figure 40 Application capabilities available to Windows Store Apps.

(“Screenshot from author”)

By default the Internet capability is selected this allows the application to make

outgoing connections. If the application requires incoming information from the

internet then the client server capability needs to be selected [145]. The Declaration

tab is used to show what interactions and API’s are supported by the application.

Declarations can be added and are categorized into two groups’ contracts or

extensions [146]. Contracts define requirements that applications must meet to

interact with others applications making use of the same contracts [146]. Extensions

are used to access specific operating system features they allow developers to A Study of Modern Mobile Tablets - 65

customize features for use in their applications [146]. Figure 41 shows the default

declaration tab which has no extensions or contracts. If a declaration is added some

initial information will be required to fulfil the extension or contracts requirements.

Figure 41 Default Declaration tab with no extensions or contracts added.

(“Screenshot from author”)

The packaging tab is the last tab in the package.appxmanifest it is responsible for

identifying the package when deployed. The packaging tab can be seen in Figure 42

displaying the unique package name, display name, version, and publisher. The

publisher display name is associated with the user account writing the application.

When a developer registers for a developer’s license as seen in Figure 37 the

certificate information is added to the publisher field. The package name is also set

by default and cannot be changed.

A Study of Modern Mobile Tablets - 66

Figure 42 Packaging tab within the app.manifest for the SensorApplication.

(“Screenshot from author”)

A Study of Modern Mobile Tablets - 67

Chapter Four: Publishing Applications

4.1. Apple Application Store

4.2. Microsoft Store

4.3. Developer Licenses

4.1. Apple Application Store

The Apple Application Store is used to distribute thousands of apps for IOS, OSX,

WatchOS, and tvOS operating systems. Anyone can download an application from the

store using an Apple ID. The Apple ID is used to uniquely identify a user across all

Apple devices and applications. To create an Apple ID a user must sign up with an email

address and password. Once the Apple ID is created payment options and security

settings can be used across many Apple services [147]. When a user first logs into an

Apple ID a dialog is presented asking for the user to enter some security questions. At a

minimum three security questions must be added as seen in Figure 43. A Study of Modern Mobile Tablets - 68

Figure 43 Trying to access Apple ID settings page for the first time prompts for

security questions. (“Screenshot from author”)

Once the security questions have been filled out the user can modify their account

information, security settings, registered device, and payment options. After an Apple ID

is setup the user can choose to download free applications or add a credit card number

for purchases. To submit products to the Apple App store a developer account is

required. The first step is to login using an Apple ID to the Developer portal as seen in

Figure 44 [148]. A Study of Modern Mobile Tablets - 69

Figure 44 Apple developer account sign-in page. (“Screenshot from author”)

After signing into the developer portal the member center is opened and displayed. The

member center can be used to download older versions of Xcode, manage certifications,

and apps published on the App Store. To upload an application to the App Store the

iTunes Connect feature must be used as seen in Figure 45.

Figure 45 The Apple member center home page. (“Screenshot from author”)

The iTunes Connect portal allows a developer to upload applications, view statistics,

sales, payments, advertisements, and users. The layout of iTunes Connect is shown in A Study of Modern Mobile Tablets - 70

Figure 46. Using the My Apps button allows a developer to create application record. An

application record is required before an application can be uploaded to the App Store

[149]. Once the iTunes Connect record is created additional information can be

configured such as store technologies and languages. Store technologies include iAd,

Game Center, In-App Purchases, and iCloud [150]. Apples iCloud can be used to

provide a single data location for users of an application [150]. To generate income the

iAd App Network can be used to provide media ads into an IOS application [150]. The

Game Center connects players and their devices to post scores and information [150]. In-

App purchases can be used to generate wealth by allowing users to purchase add-on

features.

Figure 46 iTunes Connect dashboard. (“Screenshot from author”)

Once an application record has been created and all other optional technologies

incorporated a application build needs to be uploaded. Using Xcode a developer with the

appropriate permission can start the upload process. Xcode receives the metadata from

iTunes Connect records linked with a developer account and attaches the build files to

the matching record [151]. After the build files are attached to a record the application

can be submitted for approval. It is also possible to get user feedback by entering an A Study of Modern Mobile Tablets - 71

application into the TestFlight Beta Testing program [152]. When an application is ready

for submission the developer open the My Apps section and select the application record

that will be submitted. The next step is to open the App Details page as shown in Figure

47 [149].

Figure 47 Apple application record and detail page.

The developer must then select the application to be submitted choose prepare for

submission. Afterwards one of the builds attached to the record needs to be selected and

saved [152]. The build can now be sent for submission to the App Store assuming it is

less than four billion bytes when compressed. To finally submit the application click the

Submit for Review button as seen in Figure 48 [152]. A Study of Modern Mobile Tablets - 72

Figure 48 The location of the Submit to Review button found in My Apps.

When an app is submitted for review there are many situations where it may be rejected

and not uploaded to the store. The most common reasons an application is rejected is

crashes, bugs, broken links, placeholder content, incomplete information, inaccurate

descriptions, misleading information, and not enough lasting value [153]. It is also

important that the user interface is outlined nicely. Content should fit any iOS screen,

controls should be easy to press, and text should be readable without the need to zoom in

[154]. There is a document that outlines all of the App Review Guidelines which

contains about thirty sections on why an application will be rejected. Apple will reject

applications for many reasons for example promoting damage or injury, personal attacks,

violence, objectionable content, pornography, and religious defamation [155]. The

general theme appears to be that applications should be kid friendly, easy to use, and

inoffensive.

4.2. Microsoft Store

The Microsoft Store is used to download applications for Windows 8, 8.1, and Windows

10. The store is used by thousands of people every day. To start developing applications A Study of Modern Mobile Tablets - 73

for the Microsoft Store a developer must have a Microsoft Account. The Microsoft

Account works just like an Apple ID it is one account for many windows services [156].

A user can manage their account settings through the account portal. The account portal

allows an individual to update their personal information, payment options,

subscriptions, and any registered devices such as a Surface tablet or windows phone.

Once an individual has created an account and added a payment option a developer

account can be created. To register as a developer a user must use the Dev Center as

seen in Figure 49.

Figure 49 The Dev Center sign up page. (“Screenshot from author”)

When a developer selects the sign up button a sign in page will appear asking for a

Microsoft Account. The first time a developer logs in a publisher name will need to be

selected. The publisher name will appear on any applications to indicate the author.

Once signed into the Development Center the Dashboard can be accessed to create an A Study of Modern Mobile Tablets - 74

application. The dashboard can be seen in Figure 50 the publisher name selected is J.K.

Thesis.

Figure 50 Windows Dev Center dashboard showing available options.

(“Screenshot from author”)

The Windows Dev Center can be used to find documentation, access Visual Studio

downloads, learn how to publish and promote applications. To start an application the

Create new app needs to be selected as seen in Figure 51. Once the new app button is

pressed the developer must reserve a name for their application. This name must be

unique and the developer must have the rights to use it [157]. The reserved if available is

then held for one year starting from the date it was reserved. It is recommended that a

name be short and original [157]. Once a name is reserved the submission process can

begin. A developer needs to select their newly registered app and create a submission

record. A submission record is shown in Figure 51 it contains five required steps. A A Study of Modern Mobile Tablets - 75

developer needs to fill out the pricing, app properties, age rating, packages, and

certification notes.

Figure 51 Creating a submission record for the J.K. Thesis Sensor application.

(“Screenshot from author”)

The pricing section allows the developer to pick different tier prices starting from free to

a maximum of $999.99. Application properties are used to set a category the application

falls into and a sub category. Age rating is determined by answering a simple

questionnaire that returns an international age rating coalition identifier. One of the most

important steps is the packages section. A developer needs to simply upload their final

app package from visual studios. Once the all these details are filled in the application

can be sent for approval. It is also optional to add notes that reviewers use to better

understand how the application should be used. The rules for submitting an application to

the Microsoft Store are not as restrictive when compared to the Apple App Store. Once A Study of Modern Mobile Tablets - 76

the form is finished and submitted for review it must go through the application

certification process which has four main steps preprocessing, certification, release, and

publishing [158]. The first phase called preprocessing runs the application package

through some basic testing to ensure it’s compatible with the Store. During the

certification phase three tests are done the security test, technical compliance test, and

content compliance test. The security test checks for any malware or viruses within your

application. A technical compliance test runs the Windows App Certification Kit while

the content compliance ensures you do not have any copyrighted or unsuitable material

[158]. If the certification phase fails a report will be generated that outlines what areas

failed and why. After the certification phase has passed the release step begins. The

release phase gives the developer the option to send the application immediately to the

store or set a specific date to wait for. The last phase is publishing in which the

application is digitally signed by Microsoft to signify it has not been tampered with. Once

all of these steps have been completed the application should be downloadable by anyone

using the Microsoft Store [158].

4.3. Developer Licenses

Apple

An Apple developer account requires that a developer already has an Apple ID. An Apple

Developer account costs $99.00 for an individual and $299.00 for an enterprise account [159].

Since the developer account is attached to an Apple ID no information needs to be collected other than a form of payment. An individual must use their own credit card for the simplest A Study of Modern Mobile Tablets - 77

setup, otherwise if someone else’s card is used Apple may request a copy of government issued photo identification [159]. Once the purchase is complete it will take approximately twenty four hours before the account becomes active. The enterprise account costs far more than an individual account because it allows the company to distribute applications within their organization [160]. An additional benefit is that two technical support cases are included and up to one hundred devices can be used for testing instead of the standard one device [160].

Microsoft

Signing up for a Microsoft developers account is a relatively simple experience. First the user must access the Microsoft Development Center by signing in to their Microsoft Account. If after signing in the user try’s to access the dashboard settings they will be requested to purchase a developers account. It costs $20.00 for an individual account and $99.99 for a company [161].

A small form is used to collect some personal information and a publishing name. The publishing name identifies who created the application. After this information is provided a payment screen appears requiring either a credit card or PayPal account [161]. Once payment is received by Microsoft the developer account becomes active enabling the ability to side load applications. For a company account to be created it must be verifiable through Symantec or Dun

& Bradstreet [161]. If enterprise authentication, shared user certificates, or document libraries are going to be implemented a company account is required [161]. Individual accounts do not have access to the aforementioned capabilities.

A Study of Modern Mobile Tablets - 78

Chapter Five: Operating Systems

5.1. IOS

5.2. Windows 8.1 RT

5.3. Windows 10

5.1. IOS

IOS is the operating system installed on iPad, iPhone, and iPod devices. Applications built

for IOS use the IOS SDK for creating, installing, running, and testing. The iOS Architecture

consists of four layers or interfaces. The layers include Cocoa Touch, Media, Core Services,

and Core OS as seen in Figure 52 [162]. Each version of IOS builds upon the last version

adding new functionality, and features.

Figure 52 The iOS programming layers.

5.1.1. IOS 5

IOS 5 is one of the lowest operating systems currently supported. When it was originally

released it added functionality for iCloud, Automatic Reference Counting, Storyboards,

Newsstand and Xcode 4.2 [163]. The iCloud features included an API integrating iCloud

so that information could be stored in one location [163]. IOS 5 was the first operating

system to remove manual garbage collection. A compiler level automatic reference A Study of Modern Mobile Tablets - 79

counter was added to make it easier for developers [163]. Storyboards were added in

IOS 5 making it far easier to visualize and modify interfaces. Storyboards are used to control the flow of your application. A single storyboard file is used to store all the view controllers and views associated with a project [163]. Newsstand is a convenient way for publishers to upload and distribute magazine subscriptions. A user can download and read magazines from a variety of sources [163]. Xcode 4.2 added support for many of the new features included with IOS 5. These features include implementing the automatic reference counting, storyboards, and IOS simulators [163].

5.1.2. IOS 6

IOS 6 introduced some further improvements when compared to IOS 5. New functionality includes Maps, GameCenter, Reminders, In-App Purchases, and Data privacy [164]. Improvements were made to the Map system making it easier to integrated maps into any application [164]. The GameCenter was updated to include challenges and make leader board implementation easier. A new feature was also added for turned based games, a timeout can be added to skip a player if they are taking too long [164]. Reminders can now be implemented by developers to notify device users of important information. Reminders created by developers will appear in the standard reminder area along with those created by users [164]. Microtransactions were also added in IOS 6 called In-App purchases. In-App Purchases provide a convenient way to manage purchases from within an application [164]. With IOS 6 if an application wants access to contacts, calendars, reminders, or the photo library a dialog will appear asking for permission. Applications can no longer access these locations without the user A Study of Modern Mobile Tablets - 80

knowing [164]. It is important that an application can still function even if a user does not allow access to these areas.

5.1.3. IOS 7

IOS 7 was considered a major update because the user interface had a major redesign.

The added features include Dynamic View Behaviours, 64-bit support, Game

Frameworks, Air Drop, and Peer-to-Peer connectivity [165]. Dynamic view behaviours allow a UIView object to be assigned specific behaviours. Behaviours can include attachment, collision, gravity, push, and snap [165]. Attachments can be used to link items together so that if one moves the other follows [165]. The collision behavior allows items to respond to other items using collision detection [165]. Gravity can be used to accelerate an object in a direction until it collides with a boundary [165]. Push can be used to move an item around and snap is used to snap an item to a specific point

[165]. IOS 7 was the first version to enable 64-bit support. This means that any application built targeting IOS 7 or above is built into a 32-bit and 64-bit package.

Improvements were also made to some game frameworks. The frameworks that received improvements are Sprite Kit, Game Controller, and Game Center. Sprite Kit received increased functionality for 2D and 2.5D games. Sprite kit includes libraries for rendering graphics, animations, sounds, and physics [165]. The game controller framework was added so that Bluetooth and apple controllers could be utilized. Game center added some more improvements for turn based games called exchanges which allow player to interact with one another [165]. The total number of leader boards available to a single application was increased from twenty five to one hundred. Challenges were modified slightly to allow developers to set conditions for a challenge to be met. Lastly A Study of Modern Mobile Tablets - 81

improvements were made to help prevent cheating [165]. A new technology called

AirDrop was added that allows a user to share photos, documents, and other data with nearby apple devices [165]. An application can be written to make use of AirDrop features for sharing information between nearby users of the same application. One of the last features to be added was peer-to-peer connectivity. The peer-to-peer connectivity makes it possible to create a session and communicate with nearby devices [165].

5.1.4. IOS 8

IOS 8 added further improvements to the operating system as a whole. IOS 8 introduced

App Extensions, Touch ID Authentication, Handoff and API modernization [166]. The biggest addition to IOS 8 is the app extensions that allow developers to add custom functionality to a user task. The user tasks that can be modified include sharing, actions, photo editing, storage providers, and custom keyboards [166]. Each extension task must define an API for the purposes it will accomplish [166]. Authentication through Touch

ID can now be added to any application if desired. Touch ID can be used to unlock individual content and alerts indicating why authentication is required [166]. The handoff feature was also added which allows a user to move between devices and resume the same activity. A user needs to be signed into the same Apple ID on both devices [166]. Hand off can send data from one device to another to resume the applications state and position. If an application needs to send lots of data for the hand off to work it can open a stream between devices [166]. API modernizations are slight changes to Objective-C syntax [166]. These changes include using @properties instead of getters and setters. Initialization methods now use instance type instead of id to help with dynamic binding [166]. A Study of Modern Mobile Tablets - 82

5.1.5. IOS 9

IOS 9 is the most current version and it includes all the features from previous releases.

IOS 9 added multitasking enhancements, 3D touch, search, app thinning, right to left languages, and watch connectivity [167]. The multitasking enhancements added include slide over, split view, and picture in picture. Slide over allows a user to pick a secondary application that can be interacted with quickly. Split view allows users to use two applications side by side on an iPad Air 2. Picture in Picture allows a user to watch videos in a floating window that sits above other applications [167]. 3D touch allows a user to interact with an application by using various pressures [167]. The varied pressures can be used to perform many different actions. Search was added so that users can access information from within any application [167]. Siri can be used while any application is running to find information within the application or from the internet. A developer needs to indicate what items within an application are searchable by assigning tags. App thinning is also a new feature that downloads only the information needed for a particular device [167]. For example an application requires that icons be included for all supported devices, instead of downloading every icon app thinning is used to download the icons that corresponds to the device. On-Demand resources are also a benefit of app thinning allowing an application to download information as it needs it

[167]. Previously it was possible to implement right to left languages but not everything would align correctly. IOS 9 introduces support for right to left languages which allows a standard application to flip into a right to left view [167]. One of the last major updates was watch connectivity. Watch connectivity provides communication between an iPhone A Study of Modern Mobile Tablets - 83

and apple watch. This allows developers to coordinate information and actions between

both devices [167].

5.2. Windows 8.1 RT

The original Microsoft surface tablet runs Windows RT, which is a version of Windows

8.1 for PCs utilizing ARM processors. The Surface RT does not allow you to share your

applications across the same operating system, and is missing a few features such as

windows media player, HomeGroups, remote connections, and the ability to join a

domain. [168]. Windows RT does have a desktop however it cannot run desktop

applications. Microsoft Office RT was created to run on the Windows RT desktop.

Applications must be installed using the Microsoft Store, printers, mice, keyboards, and

other devices must be Windows RT compatible [168]. Windows RT has many of the

same features that previous versions of windows had. Instead of a start menu a start page

is used to organize installed applications. The same control panel is used from windows

7 and almost all the tools perform the same functions.

5.3. Windows 10

Every Surface tablet except the Surface and Surface 2 can run Windows 10. Windows 10

is the most current operating system released by Microsoft. With Windows 10 the start

menu was used instead of the start page. The major difference is that the start menu now

contains the same tiles that were seen in the start page. The tiles can change to show

information like weather or statistics about that application. Figure 53 [169] shows the

Windows 10 start menu, which is a cross between the menu from windows 7 and

windows 8. A Study of Modern Mobile Tablets - 84

Figure 53 Windows 10 start menu the left side is what most users expect the right

side shows the different application tiles.

Windows 10 also introduced Cortana which was designed to act similar to a personal

assistant like Apples Siri [169]. Both desktop applications and windows store

applications can be installed on Windows 10. Devices running Windows 10 have a

nearly identical layout to make switching easy.

A Study of Modern Mobile Tablets - 85

Chapter Six: Materials and Methods

6.1. Materials and Methods

6.1.Materials and Methods

The materials needed are an Apple iPad, Microsoft Surface, Mac, and PC. The software

needed for development includes Xcode 6 and Visual Studios 2012. Xcode 6 must be

installed on a computer running OSX El Capitan while Visual Studio 2012 requires

Windows 8.1 to develop for Windows 8.1 RT. The last requirement includes one Apple

Developer Account and one Microsoft Developer Account.

An incremental waterfall methodology as seen in Figure 54 [170] will be used to design,

develop and test applications. All the requirements gathered in the planning phase are

broken into separate development cycles. Each cycle consists of design and

development, testing, and implementation. An example of an increment or cycle can be

seen in Figure 55 [171].The software to be implemented will utilize the unique and

common features for both tablets. In the requirements phase research will be conducted

to determine each tablets capabilities. Within the design phase systems analysis will be

used to create models, schemas, and business rules. The business rules however will be

related to the tablets capabilities and what it should do. From all the documents created

in the design phase software architecture will be outlined for each requirement. Each

requirement will be designed then developed and tested. The first requirement to be

completed will be based on the risk factors associated with each rule. After the first A Study of Modern Mobile Tablets - 86

design, develop, and test phase each other requirement will be done in the same fashion.

The application is a way to demonstrate the differences between C-Sharp and Objective-

C while highlighting each tablets unique features.

The thesis will be gradually built up over the following months. Research and

documentation will need to be done on a weekly basis. The timetable outlined below will

breakdown the approximate work required each week. To write the thesis a similar

methodology or structure will be used. First requirements will be gathered based on

objectives and aims. A general layout or design will be created for the document

outlining references gathered and possible subsections. Once the requirements and

layout are completed implementation can begin. Lastly will be the verification or review

process to ensure the thesis is coherent and correctly outlined.

Figure 54 This is a general overview of the incremental waterfall methodology. A Study of Modern Mobile Tablets - 87

Figure 55 This example shows three increments, which occur between the

requirement and acceptance phase.

Requirements Phase:

During the initial requirement phase a Statement of Scope was developed that explains exactly what must be created. The Statement of Scope is located in Appendix C. The statement of scope specifies the hardware, and software that was required. It was determined that the accelerometer, and gyroscope needed to be implemented on the iPad 2 and Surface 2. To accomplish this six increments were outlined following the Plan, Design, Research, Program work flow. The first three increments focus on implementing the iPad Accelerometer, Gyroscope, and then combining them together. Throughout each phase Unit Testing was used to ensure nothing breaks upon integrating all the components. The next three increments target the Microsoft

Surface device and follow the same pattern. First the Accelerometer is implemented, followed by the Gyroscope, and finishing with integration. A Study of Modern Mobile Tablets - 88

1st Increment

Plan:

Based on the information gathered in the Requirements phase and the Statement of Scope this incremental application must implement the Accelerometer. It will be made up of a single view that displays six labels. The first three labels will correspond with a three dimensional coordinate such as x, y, or z. The next three labels will hold the maximum values returned by the accelerometer when compared to the current x, y, or z values.

Design:

Xcode breaks files into headers, classes, and view controllers. The header file works like an interface or model. The class file manages a view and can update values displayed or perform actions. Lastly the view controller allows you to visually setup what the view will look like and link actions or outlets into the class file. The UML class diagram in Figure 56 outlines some of the basic information that will be contained within each class and how they are connected. First the main.m class initializes and calls AppDelegate. AppDelegate loads the splash screen storyboard and then calls AccelerometerViewController. AccelerometerViewController then loads the AccerelometerViewController storyboard file also known as a xib. Once the

AccelerometerViewController is loaded the user can interact with the application. A Study of Modern Mobile Tablets - 89

Figure 56 UML diagram showing approximately what the AccelerometerTest program will

look like for an IOS app. (“Created by author”)

Research:

To implement the accelerometer the iOS SDK provides a class called CMMotionManager. It is responsible for managing sensors including accelerometer updates, determining sensor availability, and accessing accelerometer data [172]. CMMotionManager has two ways to access sensor data either using periodic updates, or periodic sampling [172]. For simplicity the periodic updates will be used to collect blocks of accelerometer data. Xcode uses storyboards to easily manipulate UIViews by adding buttons and labels. Anything added to the UIView must be linked to a controller class in this case AccelerometerTest.m. Each Xcode project includes an A Study of Modern Mobile Tablets - 90

AppDelegate class that controls what to do on start-up and exit. Any cleanup or initialization should be done within the AppDelegate class. AppDelegate inherits a UIResponder class that handles iOS events, it implements a UIWindow that manages and coordinates UIViews. The

AppDelegate has five functions that include didFinishLaunchingWithOptions, applicationWillResignActive, applicationWillEnterForeground, applicationDidBecomeActive, and applicationWillTerminate. The AccelerometerTest.m class inherits the UIViewController class which allows the class to modify a view. The UIViewController requires that two methods exist viewDidLoad, and didReceiveMemoryWarning.

Programming:

The complete source code for the AccelerometerTest application can be found in Appendix C.1, it outlines exactly how the system works. In general the accelerometer application has three buttons start, stop and reset. Start enables the CMMotionManager so that accelerometer data can be updated and displayed every twenty milliseconds. When the CMMotionManager is started an event handler is added which calls updateLabels, and checkMaximumValues every twenty milliseconds. The application was created using a single view application template as seen in

Figure 57. A Study of Modern Mobile Tablets - 91

Figure 57 The options available for creating an new IOS project. (“Screenshot from author”)

Once the project has been created 9 files are added by default as seen in Figure 58. The default

ViewControllers were removed and new ones were created called AccelerometerViewController.

To hookup labels, buttons, and other controls to the header files a storyboard view needs to be created.

Figure 58 The default files created with a new project. (“Screenshot from author”)

A Study of Modern Mobile Tablets - 92

A storyboard allows the developer to manipulate a screen that will be shown to the user of the application. Figure 59 has an example of the LaunchScreen.storyboard file. The launch screen is the equivalent of a splash screen in windows 8 development. Storyboards are convenient because a separate image does not need to be created and modified if changes are required.

Figure 59 LaunchScreen.storyboard file which consists of four labels and two images.

(“Screenshot from author”)

In addition storyboards are an easy way to associate labels with variables as can be seen in

Figure 60. To add variables to a ViewController a developer needs only drag from the control to a variable as seen in Figure 61. This makes it extremely simple to setup a user interface; however it hides some of the functionality that most developers would expect to write. For example to switch between two different storyboard views no code actually needs to be written. A button is told to segue over to another storyboard when clicked instead of calling a method. A Study of Modern Mobile Tablets - 93

Figure 60 Right clicking a storyboard shows what controls are currently attached to

variables in the current ViewControllers header file. (“Screenshot from author”)

Figure 61 Associating the Start Accelerometer button within the storyboard or xib file with

a variable in the header file. (“Screenshot from author”) A Study of Modern Mobile Tablets - 94

One of the last things to do once the application has been written is to add icons, and update the info.plist. Icons are added to an image set which provides a list of icon sizes for each device. The icons that were used for every IOS increment can be seen in Figure 62.

Figure 62 The AppIcon image set for every iPad version available, the icon is a custom

image designed using GIMP. (“Screenshot from author”)

The info.plist is used to notify anyone downloading the application what the requirements are.

For the AccelerometerTest application the accelerometer sensor is required so it was added to the info.plist as seen in Figure 63. A Study of Modern Mobile Tablets - 95

Figure 63 The info.plist showing that the accelerometer key was added to the required

device capabilities, which will inform users that their device must meet these

requirements. (“Screenshot from author”)

The final product of the first increment is a standalone application that utilizes the accelerometer.

A label is used to display the acceleration of the device in the x, y, and z directions. The labels are updated very fast making it necessary to include maximum labels. The maximum labels will display just how fast the device got moving. The accelerometer application consists of two storyboards called launch screen and main which can be seen in Figure 64. Figure 64 is the final result of the first increment it was tested using an iPad 2. A Study of Modern Mobile Tablets - 96

Figure 64 The final storyboards for the AccelerometerTest application the left storyboard is

the launch screen while the right storyboard is the AccelerometerViewController

screen. (“Screenshot from author”)

2nd Increment

Plan:

Based on the information gathered in the Requirements phase and the Statement of Scope the 2nd incremental application must implement the Gyroscope. In addition it would be useful to include information related to the rotation of device based on its roll, pitch, or yaw. Using the Attitude sensor it is possible to collect this information. The GyroscopeTest application will be made up of a single view that displays 12 labels. The first three labels will correspond to the gyroscopes x, y, and z values. Directly beside them will be three more labels displaying the current maximum values that were read based on the gyroscope. Next to the gyroscope values will be six more A Study of Modern Mobile Tablets - 97

labels in the same layout but displaying the current and maximum values related to the roll, pitch, and yaw of the attitude sensor.

Design:

The overall architecture of the GyroscopeTest application can be seen in the Figure 65. The

UML diagram outlines the basic variables and how classes are connected. The layout of the second incremental application is almost identical to the Accelerometer application. First the main.m class initializes and calls AppDelegate. AppDelegate loads the splash screen storyboard and then calls GyroscopeViewController. GyroscopeViewController then loads the

GyroscopeViewController storyboard file. Once the GyroscopeViewController is loaded the user can interact with the application. A Study of Modern Mobile Tablets - 98

Figure 65 UML diagram showing approximately what the GyroscopeTest program will

look like for an IOS app. (“Created by author”)

Research:

The research for this application was not as extensive because many of the same data types and methods were learned in the first increment. The gyroscope uses the same class as the accelerometer called CMMotionManager. The gyroscope and attitude sensor can both be used in the same fashion by attaching an event handler that runs inner class methods. Figure 66 shows an example of an event handler’s inner class.

[self.motionManager startDeviceMotionUpdatesToQueue:[NSOperationQueue currentQueue] withHandler:^(CMDeviceMotion *deviceMotion, NSError *error) { //update the roll, pitch, and yaw labels [self setRoll:deviceMotion.attitude.roll Pitch:deviceMotion.attitude.pitch Yaw:deviceMotion.attitude.yaw]; A Study of Modern Mobile Tablets - 99

[self checkMaximumValue_Roll:deviceMotion.attitude.roll Pitch:deviceMotion.attitude.pitch Yaw:deviceMotion.attitude.yaw]; //if any errors occur display them in console if (error) { NSLog(@"%@", error); } Figure 66 Example of an event handler inner class used to update the roll, yaw, and pitch

labels.

Programming:

The complete source code for the GyroscopeTest application can be found in Appendix C.2, it outlines exactly how the system works. In general the gyroscope application has three buttons start, stop and reset. Start enables the CMMotionManager so that gyroscope and attitude data can be updated and displayed every twenty milliseconds. When the CMMotionManager is started an event handler is added which calls updateLabelsXYZ, checkMaximumValuesXYZ, updateLabelsRollPitchYaw, and checkMaximumValuesRollPitchYaw every twenty milliseconds. The application was created using a single view application template as seen in

Figure 67. There is one additional method added in the gyroscope application.

ConvertRadiansToDegrees makes it easier to understand the readings from the attitude sensor.

The attitude sensor returns values in radians but most of the general public can visualize degree’s better. Before the labels dealing with roll, yaw, and pitch are updated a call to

ConvertRadianstToDegrees is called. The info.plist was also modified to include the gyroscope key so that users know that a gyroscope is required before installing the application. The gyroscope application consists of two storyboards called launch screen and main which can be seen in Figure 67. Figure 67 is the final result of the second increment it was also tested using an iPad 2. A Study of Modern Mobile Tablets - 100

Figure 67 The final storyboards for the GyroscopeTest application the left storyboard is

the launch screen while the right storyboard is the GyroscopeViewController

screen. (“Screenshot from author”)

3rd Increment

Plan:

Using all the information gathered in both the first and second increment the final integrated application should be relatively easy. The final application must meet all of the essential software requirements as outlined in the Statement of Scope in Appendix C. These briefly include that the application must have a main page that opens an accelerometer and gyroscope page. When the user navigates to the accelerometer and gyroscope page a back button must exist so the user can return to the main page. The user can also quit the application at anytime. The

IOSSensorApplication will meet all these requirements by using the storyboards, and classes developed in both the AccelerometerTest and GyroscopeTest applications. A simple main page A Study of Modern Mobile Tablets - 101

will be created that displays the Algoma University logo and two buttons labeled open accelerometer and open gyroscope. To make the buttons move to another view segues will be used. One back button will be added to both the accelerometer and gyroscope storyboards to facilitate backwards navigation.

Design:

The overall architecture of the IOSSensorApplication can be seen in the Figure 68. The UML diagram outlines the basic variables and how classes are connected. The layout of the third incremental application is similar to both the gyroscope and accelerometer applications. First the main.m class initializes and calls AppDelegate. AppDelegate loads the splash screen storyboard and then calls MainViewController. MainViewController then loads the MainViewController storyboard file. Once the MainViewController is loaded the user can interact with the application. The MainViewController contains two buttons open accelerometer and open gyroscope. However these buttons require no code to activate instead they are programmed using the storyboards segue. Segues are a simple way to navigate from one view to another when a button is pressed. Segues can also be added programmatically for complex applications that create their views at runtime. A Study of Modern Mobile Tablets - 102

Figure 68 UML diagram showing approximately what the IOSSensorApplication program

will look like for an IOS app. (“Created by author”)

Research:

The research for this application was limited because many of the same data types and methods were learned in the first and second increment. This application simply combines the other two programs into one single system. One of the only things that had to be figured out was how to move between views using segues. If a button is right clicked while using the storyboard editor a window appears and the developer needs to simply drag from the button to the view they want to navigate towards. The menu that appears when a developer right clicks both buttons are shown in Figure 69 and Figure 70. A Study of Modern Mobile Tablets - 103

Figure 69 The action when a user selects the open accelerometer page button is to show the

AccelerometerViewController. (“Screenshot from author”)

Figure 70 The action when a user selects the open gyroscope page button is to show the

GyroscopeViewController. (“Screenshot from author”)

Programming:

The complete source code for the IOSSensorApplication can be found in Appendix C.3, it outlines exactly how the system works. The IOSSensorApplication is made up of four different storyboard views the Launch Screen, AccelerometerView, GyroscopeView, and MainView. For

MainView to work properly a MainViewController class needed to be created however it has no functionality. Navigating from the MainView to either the Accelerometer or Gyroscope pages is done behind the scenes. It is setup using segues that are added through the storyboard Figure 71 shows an example of the highlighted buttons and their direction. A Study of Modern Mobile Tablets - 104

Figure 71 The left image shows the highlighted segue from the open accelerometer page to

the accelerometer view controller. The right image shows the highlighted segue

from the Back button to the main view controller. (“Screenshot from author”)

The accelerometer view and gyroscope view controllers were imported directly from the applications developed in the first and second increments. In addition the accelerometer classes and gyroscope classes were also imported. In Figure 71 it is also possible to see the back button that was added to the accelerometer page. A back button was also added to the gyroscope view.

The final application was tested using an iPad 2 and its layout can be seen in Figure 72 and

Figure 73. A Study of Modern Mobile Tablets - 105

Figure 72 The final storyboards for the IOSSensorApplication the left storyboard is

the launch screen while the right storyboard is the MainViewController

screen. (“Screenshot from author”) A Study of Modern Mobile Tablets - 106

Figure 73 The final storyboards for the IOSSensorApplication the left storyboard is

the AccelerometerViewController screen while the right storyboard is the

GyroscopeViewController screen. (“Screenshot from author”)

4th Increment

Plan:

A basic application must be developed that will run on the Surface 2. The surface 2 runs

Windows 8.1 RT so it will only include system libraries that support this operating system. The application to be developed is based on the same requirements and statement of scope as outlined in previous increments the statement of scope is located in Appendix C. A windows store application is developed differently than its IOS counterpart. The fourth increment could be considered the first increment of the windows application. The fourth increment will implement the Accelerometer on the Surface 2 tablet. It will consist of a single view that displays six labels A Study of Modern Mobile Tablets - 107

like the IOS application. The first three labels will show the x, y, and z values while the last three will indicate the maximum value reached.

Design:

The overall architecture of the AccelerometerTest can be seen in the Figure 74. The UML diagram outlines the basic variables and how classes are connected. The layout of the fourth incremental application is very different then the IOS alternatives. First a splash screen image is shown while the App.xaml.cs class initializes and calls the MainPage.xaml. The MainPage.xaml is the user interface files specified using XML. The MainPage.xaml.cs file uses C-Sharp to perform actions in relation to the interface. When an application is first started a splash screen image is shown before the MainPage.xaml is shown. Once the MainPage.xaml interface is displayed the user can interact with any controls. The MainPage.xaml interface will contain a start, stop, and reset button. Six labels will also be added that show the current and maximum x, y, and z values of the accelerometer. A Study of Modern Mobile Tablets - 108

Figure 74 UML diagram showing approximately what the AccelerometerTest program

will look like for a Windows Store App. (“Created by author”)

Research:

One big difference between IOS and a Windows Store application is how they create splash screens. Splash screens in Xcode can be manipulated directly while a Windows Store application requires a splash screen to be developed using an image editing tool. Sensors can be used by including a reference to the Windows.Device.Sensor namespace. This namespace can be used to implement the accelerometer, gyro-meter, and inclinometer. These correspond with the IOS accelerometer, gyroscope, and attitude sensors. To use a sensor a request has to be made to find the default sensor of a particular type. If no sensor is found then the sensor variable gets set to A Study of Modern Mobile Tablets - 109

null and the developer must ensure it doesn’t get used otherwise an exception will occur. To retrieve data from the sensor two options can be used a loop that calls getReadings or an event handler can be created that responds to sensor changes [173]. Like the IOS versions the event handler solution will be used to implement all the sensors. Events are assigned to respond to a single sensor and a method is needed to perform actions on the data. Each Windows Store application includes by default an App.xaml, App.xaml.cs, MainPage.xaml, and

MainPage.xaml.cs. The App.xaml.cs manages which page is loaded first and what to do when the application closes. The MainPage.xaml.cs manages the functionality of controls added on the

MainPage.xaml file. MainPage.xaml.cs is a Page object while App.xaml.cs is an Application object.

Programming:

The complete source code for the AccelerometerTest application can be found in Appendix C.4, it outlines exactly how the system works. In general the accelerometer application has three buttons start, stop and reset. Start adds an event handler to the Accelerometer.ReadingChanged call so that accelerometer data can be updated and displayed. When the MainPage.xaml.cs is initialized for the first time it retrieves a default accelerometer sensor and set and interval to twenty milliseconds. The interval is assigned to the accelerometer when the start button is pressed. The event handler is setup to call the method AccelerometerChanged which intern calls setLabels, and checkMaximumValues. The application was created using a blank app template from Visual Studio’s 2012 as seen in Figure 75.

A Study of Modern Mobile Tablets - 110

Figure 75 Creating a new Blank App Windows Store application using XAML and C-Sharp.

(“Screenshot from author”)

Once the project has been created 4 files are added by default as seen in Figure 76. The default classes were used and their contents modified. To add buttons and labels a XAML designer is integrated with Visual Studio 2012. A Study of Modern Mobile Tablets - 111

Figure 76 The default files created with a blank application template.

(“Screenshot from author”)

The XAML designer can be seen in Figure 77. Controls can be added from a list by dragging and dropping them onto the canvas. When a control is added its can be modified using an XML like structure or through a properties menu. The XAML code can be found in Appendix C.4.3 however it is hard to understand and modify without being able to see it visually. A Study of Modern Mobile Tablets - 112

Figure 77 The designer being used to create the accelerometer applications main screen.

(“Screenshot from author”)

When a control is added to the designer it can immediately be referenced in the C-Sharp file as long as the control was given a name. Event handlers for buttons are also established using the designer looking at Figure 78 the Click=”StopAccelerometer” specifies the event handler.

XAML:

C#: private void StopAccelerometer(object sender, RoutedEventArgs e)

Figure 78 An example of the XAML code for the StopButton and its corresponding C-Sharp

event handler. (“Screenshot from author”)

Before the application is published the splash screen and icons must be setup in the package.appxmanifest which is similar to the IOS info.plist. Icons are added through the

Application UI tab as seen in Figure 79 and the device orientation settings can also be modified. A Study of Modern Mobile Tablets - 113

Figure 79 The Application UI tab inside the package.appxmanifest displaying the Logo icon

created using GIMP. (“Screenshot from author”)

The final product of the fourth increment is a standalone application that utilizes the accelerometer. A label is used to display the acceleration of the device in the x, y, and z directions. The labels are updated very fast making it necessary to include maximum labels. The maximum labels will display just how fast the device got moving. The accelerometer application consists of a single view which can be seen in Figure 77. Figure 77 is the final result of the fourth increment it was tested using the Surface 2.

A Study of Modern Mobile Tablets - 114

5th Increment

Plan:

Using the information from the Statement of Scope and Requirements phase the fifth increment will implement the Gyroscope. It will also utilize the inclinometer which is similar to the IOS attitude sensor. The inclinometer can detect the roll, pitch, and yaw of the tablet device. The

GyroscopeTest application will consist of a single view with 12 labels. The first three labels will correspond to the gyroscopes x, y, and z values. Directly beside them will be three more labels displaying the current maximum values that are read from the gyroscope. Next to the gyroscope values will be six more labels in the same layout displaying the current and maximum values related to the roll, pitch, and yaw of the inclinometer.

Design:

The overall architecture of the GyroscopeTest application can be seen in the Figure 80. The

UML diagram outlines the basic variables and how classes are connected. The layout of the fifth incremental application is almost identical to the Accelerometer application. The App.xaml first opens the MainPage.xaml once it loads then MainPage() is called and the initial variables are setup. Once MainPage() is called the user can interact with the application. Start Gyroscope creates an event handler that runs anytime a sensor detects a change. Stop Gyroscope removes the event handler and sets the interval to zero so resources can be returned. A Study of Modern Mobile Tablets - 115

Figure 80 UML diagram showing approximately what the GyroscopeTest program

will look like for a Windows Store App. (“Created by author”)

Research:

The fifth increment did not require as much research as the fourth increment because it was already determined how to implement the accelerometer. For the fifth increment a gyro-meter and inclinometer were examined to determine what each sensor could return. The gyro-meter returns angular velocity while the inclinometer retrieves rotations along the x, y and z axis. A Study of Modern Mobile Tablets - 116

Programming:

The complete source code for the GyroscopeTest application can be found in Appendix C.5, it outlines exactly how the system is programmed. In general the gyro-meter application has three buttons start, stop and reset. Start adds an event handler to the Gyrometer.ReadingChanged call so that gyro-meter data can be updated and displayed. When the MainPage.xaml.cs is initialized for the first time it retrieves a default gyro-meter and inclinometer. If either of the sensors exists when the user selects start then event handler will be attached to the InclinometerChanged and

GyroscopeChanged methods. The InclinometerChanged and GyroscopeChanged methods are run anytime that that a change in the sensors occurs. The InclinometerChanged method runs

SetLabelRollPitchYaw and CheckMaximumRollPitchYaw. GyroscopeChanged in comparison runs the SetLabelXYZ and CheckMaximumXYZ methods. The StopGyroscope method unhooks the event handlers for both sensors. The final applications interface design can be seen in Figure

81. A Study of Modern Mobile Tablets - 117

Figure 81 The GyroscopeTest applications user interface designed using a blank XAML

template. (“Screenshot from author”)

6th Increment

Plan:

Using all the information and knowledge gained from the fourth and fifth increment the final application should be simple. The final application must have a main page that can be used to open an accelerometer and gyroscope page. When the accelerometer or gyroscope page is loaded a button must be provided that allows the user to return to the main page. These rules are the same as outlined in the Statement of Scope in Appendix C. The final application will integrate both the AccelerometerTest and GyroscopeTest applications designed in increment four and five.

The final project will be created using a blank application template where the MainPage displays A Study of Modern Mobile Tablets - 118

two buttons open accelerometer and open gyroscope. The gyroscope and accelerometer class will be using a layout aware class so that elements resize when the device orientation is switched.

These classes will be created using a basic page template which includes a back button and title.

All the methods from the accelerometer and gyroscope test applications are to be copied into the new templates. The XAML files will also be copied into the new basic page template and modified to fit the new layout style.

Design:

The overall architecture of the WindowsSensorApplication can be seen in the Figure 82. The

UML diagram outlines the basic variables and how classes interact. The layout of the sixth incremental application is similar to both the gyroscope and accelerometer applications. First the splash screen is shown while loading the App class which then calls MainPage. MainPage loads the user interface and then waits for the user to select the open accelerometer or open gyroscope button. If open accelerometer is clicked then MainPage swaps out the current view for the

Accelerometer page. The user can now select start, stop, or reset accelerometer when they have finished the back button can be clicked to reload MainPage. The same process occurs for the open gyroscope button. Swapping between pages using a Windows Store application is not as simple as in the IOS application. When a button is clicked code must be written to swap out the current page. A Study of Modern Mobile Tablets - 119

Figure 82 UML diagram showing approximately what the WindowsSensorApplication

program will look like for a Windows Store App. (“Created by author”)

Research:

For the sixth increment the biggest item to research was how to swap pages and arrange items so they are readable on both a landscape and portrait orientation. To accomplish swapping pages a simple command is required: Frame.Navigate(typeof(GyroscopeSensor)). The typeof call requires a page namespace so that the currently visible frame is replaced with the appropriate view. To accomplish a smooth transition between landscape and portrait orientations a grid view A Study of Modern Mobile Tablets - 120

was used with multiple inner grids. When the device changes position the main grid view is stretched to fit the screen while rearranging the control positions.

Programming:

The complete source code for the WindowsSensorApplication can be found in Appendix C.6, it outlines the XAML files and C-Sharp code. The WindowsSensorApplication is made up of three different pages the MainPage, Accelerometer, and Gyroscope. The MainPage has two buttons and an image. When a button is pressed on MainPage an event is thrown and the appropriate page is shown. Navigating from the MainPage to either the Accelerometer or Gyroscope pages is done programmatically within the button event handlers. When the accelerometer or gyroscope page wants to return to the MainPage the back arrow can be pressed. Moving back to the MainPage is done behind the scenes because a basic template was used instead of a blank template. Finally some additional error detection was added so that messages would be displayed to users of the system if their sensors did not exist as seen in Figure 83. The final layout and screens for the WindowsSensorApplication can be seen in Figure 84 - 86. A Study of Modern Mobile Tablets - 121

Figure 83 Error messages if the accelerometer, gyroscope, or inclinometer are missing.

(“Screenshot from author”)

Figure 84 The MainPage is the first page the user can interact with.

(“Screenshot from author”) A Study of Modern Mobile Tablets - 122

Figure 85 The Accelerometer Page can be accessed by selecting open accelerometer page on

the MainPage. (“Screenshot from author”)

Figure 86 The Gyroscope Page can be accessed by selecting open gyroscope page on

the MainPage. (“Screenshot from author”) A Study of Modern Mobile Tablets - 123

Chapter Seven: Results and Conclusion

7.1 Results and Conclusion

7.1 Results

The IOS Sensor application was developed using Xcode within a virtual machine.

VMware workstation 12 was used to install OSX El Capitan 10.11. A physical Mac was

available however the virtual machine was more convenient. To create an OSX virtual

machine a third party program needs to install support for the file system. Using guides

online it was possible to install Snow Leopard and upgrade to El Capitan. Once El

Capitan was installed all of the display and graphics effects were disabled to improve

performance. Xcode 7 was then installed through the Mac App store and development

began. Research was conducted to determine how to setup an Apple ID and link it with a

developer account. Once the Apple ID developer account was activated Xcode could be

used to publish, and test applications. Xcode costs nothing and can be used for

development and local testing without a developer account. Once the development

environment was established the first increment began with two simple storyboards. The

first storyboard acts as a splash screen while the second contained the controls and

labels. The resulting storyboards are shown in Figure 64. Functionality was added that

updated the labels depending on the speed of the device. Every twenty milliseconds the

accelerometer would return the speed at which it was moving on the X, Y or Z axis. The

problem that occurred was that it was nearly impossible to determine how fast the device

was actually going. To overcome this additional labels were needed that would track the

maximum value regardless of the speed and direction. The absolute value was needed to A Study of Modern Mobile Tablets - 124

compare maximums because if the device was moving down the value returned would be negative and up would be positive. The accelerometer application was tested on an iPad 2 by throwing, sliding, and rotating the device. The second increment built off of the first by utilizing similar designs and code. Two storyboards were again created the first being the splash screen and the second being interactive. The second increment implemented the gyroscope and attitude sensor known as the inclinometer in the windows API. The attitude sensor was chosen because it provides information similar to the gyroscope. The attitude sensor returns the rotation from a starting point instead of the device orientation. A nearly identical layout was used labels show gyroscope and attitude updates every twenty milliseconds as seen in Figure 67. The maximum value is displayed on separate labels. The third increment required that the accelerometer and gyroscope application be combined so that a user could switch between them. Four storyboards were used the first one was a splash screen, the second a main screen with two buttons leading to two other screens. Figure 72 depicts the splash screen and main screen, when a button is pressed the corresponding screen is shown as seen in Figure 73.

A back button was added so that the user could return to the main screen. Testing was then again conducted to ensure the integrated components had not broken. Once the IOS sensor application was complete research was done regarding how to create an application record and submit the application. It was determined however that the application developed did not provide enough functionality for it to be accepted according to Apple’s submission requirements. Documentation provided by apple is extensive with many examples and images illustrating how to implement the accelerometer, gyroscope, and attitude sensors. Developing, testing, and setting up a A Study of Modern Mobile Tablets - 125

development environment for Apple was relatively straightforward. The most problems occurred when developing applications for the Surface 2. The leading cause of these problems is that the Surface 2 runs Windows 8 RT. This means that it only supports

Microsoft store applications. During the first wave of research it was determined that

Visual Studio’s was required. Initially the Surface SDK seemed like a reasonable place to start it required Visual Studio 2010 which was already installed. So the Surface SDK was added and some simple examples were created to see what the Surface SDK could do. It turns out that the Surface SDK contains most of the Surface API however it is missing some of the windows functionality most notably the sensor API. Once the

Surface SDK was determined not to work more research was done leading to the

Universal Windows Application (UWP). This application template was supposed to work with all versions of windows. To create UWP applications Visual Studio 2015 was required. Using the Algoma University Dreamspark service Visual Studio 2015 was downloaded and installed. Once installed the required sensor API was found and some test development began. From these tests it was then determined that the applications could not be run on Windows 8 RT. Finally it was determined that Microsoft store applications could only be created using Visual Studio 2012 or higher, running on

Windows 8 or 10. Once it was determined that Windows 8 was required virtual box was used to setup a virtual machine. The Algoma University Dreamspark service was used to obtain a copy of Windows 8 and Visual Studio 2012. Visual Studio 2012 was installed within the virtual machine and a Microsoft store application was created. A few test applications were created such as the simple hello world and testing was attempted.

Testing an application was particularly troublesome. First the development machine and A Study of Modern Mobile Tablets - 126

target device must login and accept a Microsoft developer certificate. Secondly the application must be built into an application package and transferred via USB to the target device. Once transferred to the device the application certificate must be added to the trusted group. Finally the application can be installed and tested on the device. It was possible to do some local testing as Microsoft store applications can run on Windows 8.

After it was determined exactly how to test and create applications for the Surface 2 the fourth increment was started. The fourth increment implemented the accelerometer. One interesting feature is that multiple event handlers can be attached to the same sensor.

This resulted in one bug where a user could press start three or more times and attach three event handlers. To disable the updates or event handlers the stop button would need to be pressed the same number of times as the start button. To fix this issue a boolean value was used to check if the button had already been pressed. Once everything was finished it was packaged and side loaded onto the Surface 2 where it was tested. The fifth increment built upon the information gathered in increment four by using the gyro- meter and inclinometer. The structure of the fourth and fifth increment was designed to be similar to the first and second increment. Similar naming conventions and methods are used for comparison purposes. The sixth and final increment required that the accelerometer and gyroscope increments be combined. Images of the main page can be found in Figure 84, which is used to navigate to the accelerometer and gyroscope examples seen in Figure 85 and 86. Just like the Apple applications labels are updated every twenty milliseconds and the maximum labels are determined by comparing absolute values. One interesting difference is that Apple will always update every twenty milliseconds however the Surface only updates when changes are detected. A Study of Modern Mobile Tablets - 127

7.2 Conclusion

The general goal of this thesis document was to research Apple and Microsoft tablets their histories, hardware, programming languages, application development, and operating systems. The task turned out to be exceptionally broad making it hard to pinpoint just what information should be examined. The first generation iPad was created in April, 2010 with the most recent version the iPad Pro released in November, 2015.

Apple is still developing new iPads and news about them should start appearing between

March and November as this is the standard pattern. Typically with each new iPad slight improvements are made most notably the system on a chip is almost always upgraded.

The SOC’s used by Apple are custom designed to meet specific requirements.

Occasionally an iPad is produced that is nearly identical such as the iPad Mini and iPad

2, probably as a way to cut costs. Microsoft started selling the Surface RT in October

2012 with its most recent version being the Surface Pro 4 in October 2015. The Surface

RT and Surface 2 both ran Windows RT which was developed to run on ARM architecture. The reason that Windows RT did not become popular is most likely due to it being unsuitable in a business environment, and unable to run desktop applications.

Windows RT was unable to connect to domain networks and HomeGroups. To further complicate thing Windows RT could not be connected to remotely for debugging purposes. For a business the lack of these features could result in a significant waste of resources and time. With the Surface 3 Microsoft changed directions away from ARM architecture. Once the Surface Pro was released Microsoft had moved away from SOC completely instead opting to use Intel processors with integrated graphics. This move allowed Microsoft to ship the tablets with Windows 10, opening up the tablets to desktop A Study of Modern Mobile Tablets - 128

applications. Most of the hardware improvements from one device to another are minor

and usually consist of a better processors and camera. Apple uses Objective-C as its

primary programming language, while Microsoft uses C-Sharp. Objective-C uses a

different syntax then most programming languages. C-Sharp on the other hand looks and

behaves very similarly to java. The reason that Apple uses Objective-C is because it was

used to develop applications for NeXTStep. NeXTStep was purchased by Apple in 1996

to be used as the basis for their OSX operating system. NeXTStep was one of the only

systems at the time to use Objective-C. C-Sharp on the other hand was developed to

replace C++ and was added into the .Net framework. C# is currently in the 4th position of

the TIOBE programming language index while objective-C sits in 15th [174]. Last year

Objective-C was in 3rd with C-Sharp in 4th it is unclear why Objective-C took such a

plunge in popularity but it could have something to do with the introduction of the Swift

programming language. Objective-C’s rise in popularity seems to have started right

around when the first iPad was released in 2010 as seen in Figure 87 [175]. Figure 88

[176] shows that C-Sharp has been relatively popular since its inception in 2002.

Figure 87 Objective-C programming language popularity. A Study of Modern Mobile Tablets - 129

Figure 88 C-Sharp programming language popularity

Developing applications for both C-Sharp and Objective-C are relatively simple once the

development environment is setup. To create applications two virtual machines were used

one running Windows 8.1 and another running OSX El Capitan. To develop applications

Visual Studio 2012 and Xcode were required. Developing applications for Apple is much

easier then Microsoft due to the extensive documentation and examples provided. It was

exceptionally hard to gather information on how to develop applications for Windows

RT. It was finally determined that at a minimum Visual Studio 2012 must be used on a

computer running Windows 8.1 or later. In addition it was very difficult to find concrete

examples and documentation related to what had to be implemented. Xcode appears to be

the only tool that is needed to create applications and submit them. Testing applications

using Xcode was as simple as connecting a device and registering it with a developer. In

comparison Visual Studios was used to create the application package however to test it a

developer license needed to be registered on both the device and development operating

system. Once both devices were registered the application package needed to be installed

via USB to the target device. Once the package was transferred a certificate needed to be

registered and then the application could be installed. Xcode does almost all the work for A Study of Modern Mobile Tablets - 130

a developer while Visual Studio requires a descent amount of work on the developer’s part. Developing applications for both systems requires that a Developer Account be created and using the appropriate web portal an application record needs to be created.

The application record is used to set the price, description, and current build. After the record is created Visual Studio’s or Xcode can automatically upload the current application build to the record. Once added to the record the developer is required to submit the application for review. If the review process proceeds and no issues are encountered the application will be placed into the Apple Store or Microsoft Store. It felt much simpler to develop applications using Apple products compared to Microsoft. A company trying to decide on what route to take should consider the cost of a development environment. The Apple developer account costs significantly more than a Microsoft account. In addition Apple development must be accomplished on Apple hardware. It may not be cost effective to purchase Apple Mac’s for the sole purpose of development because they cost far more compared to standard desktop systems. Microsoft development would be recommended if desktop hardware is already available because all it would require is a copy of Windows 8.1 or 10 installed. The only downside is that

Visual Studios must be purchased, while Xcode is free. The sample application that was developed made use of an accelerometer, gyroscope, and inclinometer. The inclinometer is called an attitude sensor in Apple applications, while the gyroscope is called a gyro- meter in Microsoft applications. Six increments were created that consisted of implementing the accelerometer, then the gyroscope, finishing with integrating them together. The first three increments were created using Xcode and Objective-C. The second three increments were built using Visual Studio 2012 and C-Sharp. Creating A Study of Modern Mobile Tablets - 131

applications for either Microsoft or Apple in a business environment has a few things that need to be considered. First what type of mobile devices are being used within the corporation are they mostly Apple or Microsoft? Secondly are the applications being developed going to be used for in-house applications? Lastly will additional hardware need to be purchased to create these applications and if so how many? Using this document it should be possible to get a general understanding on how applications are built for both Microsoft and Apple. The histories, hardware, programming languages, application development, and operating systems are all briefly explained and should be of considerable help.

A Study of Modern Mobile Tablets - 132

Appendices

Appendix A: Device Specifications Table I. iPad Series Hardware Specifications

Table II. iPad Air Series Hardware Specifications

Table III. iPad Mini Series Hardware Specifications

Table IV. iPad Pro Series Hardware Specifications

Table V. Surface Series Hardware Specifications

Table VI. Surface Pro Series Hardware Specifications

Table VII. Surface Book Series Hardware Specifications

A Study of Modern Mobile Tablets - 133

TABLE I.

THIS IS A COMPARISON OF THE IPAD 1, IPAD 2, IPAD 3, AND IPAD 4 HARDWARE

SPECIFICATIONS, AS OF JAN. 2016.

Model: iPad [1] iPad 2 [2] iPad 3 [3] iPad 4 [4] Released: Apr. 2010 [5] Mar. 2011 [6] Mar. 2012 [7] Nov. 2012 [8] Highest Supported iOS 5.1.1 [9] iOS 9.2 [10] iOS 9.2 [10] iOS 9.2 [10] Operating System: Display: 9.7” 9.7” 9.7” 9.7” 1024 x 768 1024 x 768 2048 x 1536 2048 x 1536 CPU (Architecture): ARM Cortex A8 ARM Cortex A9 ARM Cortex A9 Swift (ARMv7-A) (ARMv7-A) (ARMv7-A) (ARMv7-A) [11,12] [13,14] [15,14] [16] GPU: PowerVR Dual-Core Quad-Core Quad-Core SGX535 [9] PowerVR PowerVR PowerVR SGX543MP2 SGX543MP4 SGX554 [17] [17] MP4[18] System on a Chip: Apple A4 Apple A5 Apple A5X Apple A6X Motion coprocessor: N/A N/A N/A N/A Memory: 256 MB DRAM 512 MB 1 GB 1 GB DDR2[22] [19] DDR2[13] DDR2[20,21] Storage (GB): 16, 32, 64 16 16,32,64 16,32,64,128 Camera: Front: N/A VGA VGA 720p HD 0.3 Megapixels 0.3 Megapixels 1.2 Megapixels [23] [20] Back: N/A 720p HD 1080p HD 1080p HD 0.7 Megapixels 5 Megapixels 5 Megapixels [24] [20] Wireless: Wi-Fi Wi-Fi Wi-Fi Wi-Fi (802.11a/b/g/n) (802.11a/b/g/n) (802.11a/b/g/n) (802.11a/b/g/n) Bluetooth 2.1 + Bluetooth 2.1 + Bluetooth 4.0 Bluetooth 4.0 EDR EDR Geolocation: Wi-Fi Wi-Fi Wi-Fi Wi-Fi Digital Compass Digital Compass Digital Compass Digital Compass Sensors: Accelerometer Accelerometer Accelerometer Accelerometer Ambient Light Ambient Light Ambient Light Ambient Light Sensor Sensor Sensor Sensor Gyroscope Gyroscope Gyroscope Battery: 3.75V, 24.8 3.8V, 25 watt- 3.78V, 43.8 3.7V 43.0 watt- watt-hour [19] hour [25] watt-hours[20] hours[26] Dimensions: 9.56” x 7.47” x 9.50” x 7.31” x 9.50” x 7.31” x 9.50” x 7.31” x 0.5” 0.34” 0.37” 0.37” Weight: 1.5 lb 1.33 lb 1.44 lb 1.44lb

A Study of Modern Mobile Tablets - 134

TABLE II.

THIS IS A COMPARISON OF THE IPAD AIR 1 AND IPAD AIR 2 HARDWARE

SPECIFICATIONS, AS OF JAN. 2016.

Model: iPad Air 1 [34] iPad Air 2 [35] Released: Nov. 2013 [36] Oct. 2014 [37] Highest Supported iOS 9.2 [10] iOS 9.2 [10] Operating System: Display: 9.7” 9.7” 2048 x 1536 2048 x 1536 CPU (Architecture): Cyclone Typhoon (ARMv8-A) [16] (ARMv8-A) [22,38] GPU: PowerVR G6430 [39] PowerVR GXA6850 [22] System on a Chip: Apple A7 Apple A8X Motion coprocessor: Apple M7 Apple M8 Memory: 1 GB DDR3 [40] 2 GB DDR3 [22] Storage (GB): 16,32,64,128 16,64,128 Camera: Front: 720p HD 720p HD 1.2 Megapixels 1.2 Megapixels Back: 1080p HD 1080p HD 5 Megapixels 8 Megapixels Wireless: Wi-Fi - Dual Channel Wi-Fi - Dual Channel (802.11a/b/g/n) (802.11a/b/g/n) Bluetooth 4.0 Bluetooth 4.0 MIMO MIMO Geolocation: Wi-Fi Wi-Fi Digital Compass Digital Compass iBeacon Sensors: Accelerometer Accelerometer Ambient Light Sensor Ambient Light Sensor Gyroscope Gyroscope Touch ID Barometer Battery: 3.73V, 32.9 watt-hour [40] 3.76V, 27.62 watt-hour [41] Dimensions: 9.40” x 6.60” x 0.29” 9.40” x 6.60” x 0.24” Weight: 1 lb 0.98 lb

A Study of Modern Mobile Tablets - 135

TABLE III.

THIS IS A COMPARISON OF THE IPAD MINI 1, IPAD MINI 2, IPAD MINI 3, AND IPAD

MINI 4 HARDWARE SPECIFICATIONS, AS OF JAN. 2016.

Model: iPad Mini 1 [48] iPad Mini 2 [49] iPad Mini 3 [50] iPad Mini 4 [51] Released: Nov. 2012 [8] Nov. 2013 [36] Oct. 2014 [37] Sept. 2015 [52] Highest Supported iOS 9.2 [10] iOS 9.2 [10] iOS 9.2 [10] iOS 9.2 [10] Operating System: Display: 7.9” 7.9” 7.9” 7.9” 1024x768 2048 x 1536 2048 x 1536 2048 x 1536 CPU (Architecture): ARM Cortex A9 Cyclone Cyclone Typhoon (ARMv7-A) (ARMv8-A) (ARMv8-A) (ARMv8-A) [13,14] [16] [16] [38] GPU: PowerVR PowerVR PowerVR PowerVR SGX543MP2 G6430 [32] G6430 [32] GX6450[38] [17] System on a Chip: Apple A5 Apple A7 Apple A7 Apple A8 Motion coprocessor: N/A Apple M7 Apple M7 Apple M8 Memory: 512 MB DDR2 1 GB DDR3[54] 1 GB DDR3[55] 2 GB DDR3[56] [53] Storage (GB): 16,32,64 16,32,64,128 16,64,128 16,64,128 Camera: Front: 720p HD 720p HD 720p HD 720p HD 1.2 Megapixels 1.2 Megapixels 1.2 Megapixels 1.2 Megapixels Back: 1080p HD 1080p HD 1080p HD 1080p HD 5 Megapixels 5 Megapixels 5 Megapixels 8 Megapixels Wireless: Wi-Fi Wi-Fi - Dual Wi-Fi - Dual Wi-Fi - Dual (802.11a/b/g/n) Channel Channel Channel Bluetooth 4.0 (802.11a/b/g/n) (802.11a/b/g/n) (802.11a/b/g/n) Bluetooth 4.0 Bluetooth 4.0 Bluetooth 4.0 MIMO MIMO Geolocation: Wi-Fi Wi-Fi Wi-Fi Wi-Fi Digital Compass Digital Compass Digital Compass Digital Compass iBeacon iBeacon Sensors: Accelerometer Accelerometer Accelerometer Accelerometer Ambient Light Ambient Light Ambient Light Ambient Light Sensor Sensor Sensor Sensor Gyroscope Gyroscope Gyroscope Gyroscope Touch ID Touch ID Barometer Battery: 3.72V 16.5 3.75V, 24.3 3.75V, 24.3 3.75V, 24.3 watt-hour [53] watt-hour [54] watt-hour [57] watt-hour [56] Dimensions: 7.87” x 5.3” x 7.87” x 5.3” x 7.87” x 5.3” x 8.0” x 5.3” x 0.28” 0.29” 0.29” 0.24” Weight: 0.68 lb 0.73 lb 0.73 lb 0.65 lb A Study of Modern Mobile Tablets - 136

TABLE IV.

HARDWARE SPECIFICATIONS FOR THE IPAD PRO, AS OF JAN. 2016.

Model: iPad Pro [61] Released: Nov. 2015 [62] Highest Supported Operating iOS 9.2 [10] System: Display: 12.9” 2732 x 2048 CPU (Architecture): Twister (ARMv8-A)[22,63] GPU: PowerVR 7XT GPU with 12 cores [64] System on a Chip: Apple A9X Motion coprocessor: Apple M9 Memory: 4GB DDR4 [22] Storage (GB): 32,128 Camera: Front: 720p HD 1.2 Megapixels Back: 1080p HD 8 Megapixels Wireless: Wi-Fi - Dual Channel (802.11a/b/g/n) Bluetooth 4.0 MIMO Geolocation: Wi-Fi Digital Compass iBeacon Sensors: Accelerometer Ambient Light Sensor Gyroscope Touch ID Barometer Battery: 3.77V, 38.8 watt-hour[65] Dimensions: 12” x 8.68” x 0.27” Weight: 1.57 lb

A Study of Modern Mobile Tablets - 137

TABLE V.

THIS IS A COMPARISON OF THE SURFACE RT, SURFACE 2, AND SURFACE 3

HARDWARE SPECIFICATIONS, AS OF JAN. 2016.

Model: Surface RT [67] Surface 2 [68] Surface 3 [69] Released: Oct. 2012 [70] Feb. 2013 [71] May, 2015 [72] Highest Supported Windows RT Windows RT Windows 10 [73] Operating System: Display: 10.6” 10.6” 10.8” 1366 x 768 1920 x 1080 1920 x 1080 CPU (Architecture) ARM Cortex A9 4x ARM Atom x7-Z8700 {Max Frequency}: (ARMv7-A) Cortex-A15 (Airmont) [31,14] (ARMv7-A) [77] [74 - 76] GPU: GeForce ULP GeForce ULP HD Graphics (2012) [75] (2013) [75] Intel's Gen 8 [77] System on a Chip: NVIDIA Tegra NVIDIA Tegra Intel Atom x7- 3 4 Z8700 Storage / Memory 32/2GB 32/2GB 32/2GB (DDR3): 64/2GB [78] 64/2GB [79] 64/4GB Camera: Front: 1080p HD 1080p HD 1080p HD 3.5 Megapixels 3.5 Megapixels 3.5 Megapixels [80] [81] [82] Back: 1080p HD 1080p HD 1080p HD 5.0 Megapixels 5.0 Megapixels 8.0 Megapixels [80] [81] [82] Wireless: Wi-Fi Wi-Fi Wi-Fi (802.11a/b/g/n) (802.11a/b/g/n) (802.11a/b/g/n/ac) Bluetooth 4.0 Bluetooth 4.0 Bluetooth 4.0 Geolocation: N/A Digital Compass N/A Sensors: Ambient light Ambient light Ambient light sensor sensor sensor Accelerometer Accelerometer Accelerometer Gyroscope Gyroscope Gyroscope Magnetometer Magnetometer Magnetometer Proximity Sensor Battery: 7.4 V, 31.5 7.6V, 31.3 watt- 3.78V, 27.5 watt- watt-hour [78] hour [79] hour[83] Dimensions: 10.81” x 6.79” x 10.81” x 6.79” x 10.52” x 7.36” x 0.35” 0.35” 0.34” Weight: 1.5 lb 1.49 lb 1.37 lb

A Study of Modern Mobile Tablets - 138

TABLE VI.

THIS IS A COMPARISON OF THE SURFACE PRO, SURFACE PRO 2, SURFACE PRO 3,

AND SURFACE PRO 4 HARDWARE SPECIFICATIONS, AS OF JAN. 2016.

Model: Surface Pro [89] Surface Pro 2 Surface Pro 3 [91] Surface Pro 4 [92] [90] Released: Feb. 2013 [93] Oct. 2013 [71] Jun. 2014 [94] Oct. 2015 [95] Highest Windows 10 Windows 10 Windows 10 Windows 10 Supported [73] [73] [73] [73] Operating System: Display: 10.6” 10.6” 12” 12.3” 1920 x 1080 1920 x 1080 2160 x 1440 2736 x 1824 CPU (Intel 2 x Intel Core i5- 2 x Intel Core 2 x Intel Core i3- 2 x Intel Core Generation) 3317U i5-4200U 4020Y m3-6Y30 {Max (3rd Gen.) (4th Gen.) (4th Gen.) (6th Gen.) Frequency}: 1.7GHz 1.6GHz 1.5GHz 0.9GHz {2.6GHz} {2.6GHz} {1.5GHz} {2.2GHz} [96,97] [96,98] [96,99] [100,101] 2 x Intel Core 2 x Intel Core i5- 2 x Intel Core i5- i5-4300U 4300U 6300U (4th Gen.) (4th Gen.) (6th Gen.) 1.9GHz 1.9GHz 2.4Ghz {2.9GHz} {2.9GHz} {3.0Ghz} [96,102] [96, 102] [79,103] 2 x Intel Core i7- 2 x Intel Core i7- 4650U 6650U (4th Gen.) (6th Gen.) 1.7Ghz 2.2GHz { 3.3Ghz} {3.4GHz} [96,104] [100,105] GPU: Intel HD Intel HD i3 Intel HD m3 Intel HD Graphics 4000 Graphics 4400 Graphics Graphics [96] [96] 4200 [106] 515 [100] i5 Intel HD i5 Intel HD Graphics Graphics 4400 [107] 520 [100] i7 Intel HD i7 Intel Iris Graphics Graphics 5000 [108] 540 [100] CPU Options: Intel Core i5 Intel Core i5 Intel Core i3, i5 Intel Core m3, i5, or i7 or i7

A Study of Modern Mobile Tablets - 139

Storage / 64/4GB, 64/4GB, 64/4GB, 128/4GB, Memory 128/4GB 128/4GB, 128/4GB, 256/8GB, (DDR3): 256/8GB, 256/ 8GB, 256/16GB, 512/8GB [100] 512/8GB [100] 512/16GB, 1024/16GB [100] Camera: Front: 720p HD 720p HD 1080p HD 1080p HD 1.2 Megapixels 1.2 Megapixels 5.0 Megapixels 5.0 Megapixels [89, 100] [90,100] [109] Back: 720p HD 720p HD 1080p HD 1080p HD 1.2 Megapixels 1.2 Megapixels 5.0 Megapixels 8.0 Megapixels [89,100] [90,100] [109] Wireless: Wi-Fi Wi-Fi Wi-Fi Wi-Fi (802.11a/b/g/n) (802.11a/b/g/n) (802.11a/b/g/n/ac) (802.11a/b/g/n/ac) Bluetooth 4.0 Bluetooth 4.0 Bluetooth 4.0 Bluetooth 4.0 Geolocation: N/A N/A Digital Compass N/A Sensors: Ambient light Ambient light Ambient light Ambient light sensor sensor sensor sensor Accelerometer Accelerometer Accelerometer Accelerometer Gyroscope Gyroscope Gyroscope Gyroscope Magnetometer Magnetometer Magnetometer Magnetometer Battery: 7.4V, 42 watt- 7.4V, 42 watt- 7.6V, 42.2 watt- 7.5V, 38.2 watt- hour[109] hour[110] hour [111] hour [112] Dimensions: 10.81” x 6.81” x 10.81” x 6.81” 11.5” x 7.93” x 11.5” x 7.93” x 0.53” x 0.53” 0.3” 0.33” Weight: 2 lb [100] 2 lb 1.76 lb m3 1.69 lb i5 1.73 lb i7 1.73 lb

A Study of Modern Mobile Tablets - 140

TABLE VII.

HARDWARE SPECIFICATIONS FOR THE SURFACE BOOK, AS OF JAN. 2016.

Model: Surface Book [116] Released: Oct. 2015 [95] Highest Supported Operating Windows 10 [73] System: Display: 13.5” 3000 x 2000 CPU (Architecture) 2 x Intel Core i5-6300U {Max Frequency}: (6th Gen) 2.4Ghz {3.0Ghz} [117,103] 2 x Intel Core i7-6600U (6th Gen) 2.6GHz {3.4GHz} [117,118] GPU (Optional) {Similar GPU} : Laptop (NVIDIA Geforce GPU with 1GB GDDR5) {GT 940M} [117]

Tablet Intel HD Graphics 520

System on a Chip: 6th Generation Intel Core i5 or i7 Motion coprocessor: N/A Memory: 8GB/16GB Storage (GB): 128,256,512,1024 Camera: Front: 1080p HD 5.0 Megapixels Back: 1080p HD 8.0 Megapixels Wireless: Wi-Fi (802.11a/b/g/n/ac) Bluetooth 4.0 Geolocation: N/A Sensors: Ambient light sensor Accelerometer Gyroscope Magnetometer Battery: Laptop 7.5V, 51.0 watt-hour [119] Tablet 7.5V, 18.0 watt-hour [119] Dimensions: Laptop 9.14” x 12.3” x 0.51-0.90” [117] Tablet 8.67” x 12.3” x 0.30” [117] Weight: Laptop 3.34 - 3.48 lbs [117] Tablet 1.6 lbs [117] A Study of Modern Mobile Tablets - 141

Appendix B: Software Statement of Scope B.1. Project Inception B.2. Functional Requirements B.3. Non-Functional Requirements

Sensor Test Application Scope

B.1. Project Inception: Introduction: This Statement of Scope is prepared by Jordan Kahtava for Algoma University. The project leader and programmer is Jordan Kahtava. This thesis project is created with the help of Gerry Davies faculty supervisor. Two applications will be developed one for the iPad 2 and the second for the Microsoft Surface 2. The iPad 2 is running iOS 9.2 while the Surface 2 uses Windows 8.1 RT.

Purpose of the Project: The application will demonstrate how to use and implement the Accelerometer and Gyroscope on both systems. The iPad and Surface both contain all these two sensors which make it useful in comparing programming languages, and design.

Users of the Product: Anyone will be able to access and download both applications once they have been approved. The general public, teachers, and thesis presentation attendees are the targeted end users.

Application Environment of the Proposed System: This section identifies both the hardware and the software that must be in place in the operational (non-testing) environments and configuration details.

Hardware Requirements: Algoma University has agreed to provide a Microsoft Surface 2 Tablet running Windows 8.1 RT. Through Algoma Universities Dream spark website operating systems, and development environments can be downloaded. Algoma University will allow development to occur on a shared Apple Mac in the Computer Science Lab. Jordan Kahtava is responsible for acquiring the iPad 2.

Software Requirements: A Study of Modern Mobile Tablets - 142

During each increment of this project the Apple Development Center and Microsoft Development Center must be accessible. Each development center provides the ability to submit applications and modify developer account information. It is Jordan Kahtava’s responsibility to obtain an individual Microsoft Developer Account, and Apple Developer Account.

Data Requirements: The information that resides within any relevant database or website must remain available and accessible over the duration of the development process. Non-compliance with this data requirement will pose a high risk situation for design analysis and a medium risk situation which could jeopardize the testing schedule for the grouping aspects of the project.

Development Environment of the Proposed System: The Incremental Waterfall paradigm has been chosen for this project because the systems requirements are known and detailed.

Hardware Requirements: Algoma University has agreed to provide the following hardware:  Microsoft Surface 2 (Windows 8.1 RT)  1 iMac for Development Purposes  Access to Microsoft DreamSpark Service for software Jordan Kahtava has agreed to provide the following hardware:  iPad 2 (iOS 9.2)  1 Laptop for Development Purposes

Software Requirements: The Microsoft Surface 2 application will be developed using Windows 8.1 Pro, Visual Studios 2012, C#, Windows Runtime SDK, and 1 Microsoft Developer Account. The iPad 2 application will be developed using OS X el Capitan, Xcode 6, Objective-C, iOS 9.2 SDK, and 1 Apple Developer Account. The project documentation will be developed using Microsoft Word, and Dia, which is a data-modeling tool.

Research Requirements: Information related to how Sensors can be implemented using Objective-C and the C# must be determined.

B.2. Functional Requirements: A Study of Modern Mobile Tablets - 143

Functional requirements are functions or features that must be included in the system to satisfy the project requirements.

The Proposed System’s Context Diagram: The Windows Store App depicted in Figure 88 and the Apple iOS App depicted in Figure 89 contains all of the external entities that produce or consume data. Both of the proposed systems are are nearly identical. The context diagram assists in bounding the scope of the software requirements and also assists in determining the system interfaces.

Figure 89 Windows Store Sensor Test Application Context Diagram. A Study of Modern Mobile Tablets - 144

Figure 90 Apple iOS Sensor Test Application Context Diagram

The Sensor Test application for iOS and Windows RT is the software system that will be developed to meet the requirements outline in this Statement of Scope.

Only one external entity exists for both systems and they play an integral role in the operation of the Sensor Test system their roles is briefly described as follows:

 User: This User is granted full privileges such that the User can install the application, load sensor test pages, and interact with the implemented sensors to view data.

Functions Provided by the Project:

This section explicitly identifies the hardware and software functionality for the project. Each hardware and software requirement is prioritized as follows: A Study of Modern Mobile Tablets - 145

 Essential: These requirement must be included in the system  Useful: These requirements are those that would reduce system effectiveness if left out  Desirable: These requirements are those that are not part of the core, but make the system more attractive to the user

In addition, each requirement will be identified using a unique identifier: the letters “HW” for hardware, “SW” for software, followed by the priority category – “E” for Essential, “U” for Useful, or “D” for Desirable, and a number representing the order of priority within the category. This notation will be used in other documents to cross-reference the requirements back to this statement of scope.

Hardware Requirements:

Hardware requirements for this project are prioritized in the following paragraphs.

Essential Requirements:

The Sensor Test System has the following essential hardware requirements:

HWE1 The Sensor Test System shall first be deployed on the iOS 9.2 operating system.

HWE2 The Sensor Test System shall be developed on 1 laptop running an OS X 10.10 Virtual Machine.

HWE3 The Sensor Test System shall be deployed on the Windows RT operating system.

HWE4 The Sensor Test System shall be developed on 1 laptop running a Windows 8.1 Virtual Machine.

Useful Requirements:

The Sensor Test System has no identified useful hardware requirements at this time.

Desirable Requirements:

The Sensor Test System has no identified desirable hardware requirements.

A Study of Modern Mobile Tablets - 146

Software Requirements:

Software requirements for this project are prioritized in the following paragraphs.

Essential Requirements

The Sensor Test System has the following essential software requirements:

SWE1 The Sensor Test System shall allow the user to install the application.

SWE2 The Sensor Test System shall allow the user to open the application to a main page.

SWE3 The Sensor Test System shall allow the user to open the Accelerometer Test Page.

SWE4 The Sensor Test System shall allow the user to open the Gyroscope Test Page.

SWE5 The Sensor Test System shall allow the user to return to the main page from the accelerometer or gyroscope test pages.

SWE6 The Sensor Test System shall allow the user to exit the application from the main page.

Useful Requirements

The Sensor Test System has no identified desirable hardware requirements.

Desirable Requirements

The Sensor Test System has no identified desirable hardware requirements.

B.3. Non-Functional Requirements Non-functional requirements describe the features, characteristics, and attributes of the system as well as any constraints that may limit the boundaries of the proposed system and the eventual design of the product.

Mandated Constraints:

This section describes constraints on the requirements and the eventual design of the product.

Deadline:

 The deadline for this project is March 31 2016. A Study of Modern Mobile Tablets - 147

Solution Constraints:

 The system must be easy to use.  The system must be developed under the Incremental Waterfall model paradigm and conform to the identified software requirements (SWE, SWU, SWD).

Look and Feel Requirements:

The Interface:

 The System must have an intuitive interface for ease of use.  The interface must have a menu to access Sensor Test Pages.  The interface must display options to manipulate the sensors where interaction is possible.

Usability Requirements:

Ease of use:

 The product must be user friendly, such that controls are simple and easy to understand.  The product must be able to demonstrate the capabilities of accelerometers and gyroscopes.

Personalization and internationalization Requirements:

Language:

The Sensor Test System must comply with the country of origin localization. Being located in a predominately English/French geographic location, English will be the chosen language subset.

Ease of Learning:

Training:

Basic software navigation skills are required to use this product.

Deliverables: A Study of Modern Mobile Tablets - 148

At a minimum, the following constitute the deliverables for the Sensor Test System.

Project Deliverables:

The following list constitutes the project deliverables:

 Source code  Functional prototype software installed, and operating on chosen platform  Any associated documentation.

A Study of Modern Mobile Tablets - 149

Appendix C: Source Code C.1. Increment 1: Accelerometer, IOS

C.1. 1. main.m

C.1. 2. AppDelegate.h

C.1.3. AppDelegate.m

C.1.4. AccelerometerViewController.h

C.1.5. AccelerometerViewController.m

C.2. Increment 2: Gyroscope, IOS

C.2. 1. main.m

C.2. 2. AppDelegate.h

C.2.3. AppDelegate.m

C.2.4. GyroscopeViewController.h

C.2.5. GyroscopeViewController.m

C.3. Increment 3: Integration, IOS

C.3. 1. main.m

C.3. 2. AppDelegate.h

C.3.3. AppDelegate.m

C.3.4. AccelerometerViewController.h

C.3.5. AccelerometerViewController.m

C.3.6. GyroscopeViewController.h

C.3.7. GyroscopeViewController.m

C.3.8. MainViewController.h

C.3.9. MainViewController.m

C.4. Increment 4: Accelerometer, Windows 8

C.4.1. App.xaml A Study of Modern Mobile Tablets - 150

C.4.2. App.xaml.cs

C.4.3. MainPage.xaml

C.4.4. MainPage.xaml.cs

C.5. Increment 5: Gyroscope, Windows 8

C.5.1. App.xaml

C.5.2. App.xaml.cs

C.5.3. MainPage.xaml

C.5.4. MainPage.xaml.cs

C.6. Increment 6: Integration, Windows 8

C.6.1. App.xaml

C.6.2. App.xaml.cs

C.6.3. MainPage.xaml

C.6.4. MainPage.xaml.cs

C.6.5. Accelerometer.xaml

C.6.6. Accelerometer.xaml.cs

C.6.7. Gyroscope.xaml

C.6.8. Gyroscope.xaml.cs

A Study of Modern Mobile Tablets - 151

C.1. Increment 1: Accelerometer, IOS

C.1.1. main.m // // main.m // AccelerometerTest // // Created by Jordan on 2016-02-01. // Copyright © 2016 Jordan. All rights reserved. //

#import #import "AppDelegate.h" int main(int argc, char * argv[]) { @autoreleasepool { return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class])); } }

C.1.2. AppDelegate.h // // AppDelegate.h // AccelerometerTest // // Created by Jordan on 2016-02-01. // Copyright © 2016 Jordan. All rights reserved. //

#import

@interface AppDelegate : UIResponder

@property (strong, nonatomic) UIWindow *window;

@end

C.1.3. AppDelegate.m // // AppDelegate.m // AccelerometerTest // A Study of Modern Mobile Tablets - 152

// Created by Jordan on 2016-02-01. // Copyright © 2016 Jordan. All rights reserved. //

#import "AppDelegate.h"

@interface AppDelegate ()

@end

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { // Override point for customization after application launch. return YES; }

- (void)applicationWillResignActive:(UIApplication *)application { // Sent when the application is about to move from active to inactive state. This can occur for certain types of temporary interruptions (such as an incoming phone call or SMS message) or when the user quits the application and it begins the transition to the background state. // Use this method to pause ongoing tasks, disable timers, and throttle down OpenGL ES frame rates. Games should use this method to pause the game. }

- (void)applicationDidEnterBackground:(UIApplication *)application { // Use this method to release shared resources, save user data, invalidate timers, and store enough application state information to restore your application to its current state in case it is terminated later. // If your application supports background execution, this method is called instead of applicationWillTerminate: when the user quits. }

- (void)applicationWillEnterForeground:(UIApplication *)application { // Called as part of the transition from the background to the inactive state; here you can undo many of the changes made on entering the background. }

- (void)applicationDidBecomeActive:(UIApplication *)application { // Restart any tasks that were paused (or not yet started) while the application was inactive. If the application was previously in the background, optionally refresh the user interface. }

- (void)applicationWillTerminate:(UIApplication *)application { // Called when the application is about to terminate. Save data if appropriate. See also applicationDidEnterBackground:. }

@end

A Study of Modern Mobile Tablets - 153

C.1.4. AccelerometerViewController.h // // ViewController.h // AccelerometerTest // // Created by Jordan on 2016-02-01. // Copyright © 2016 Jordan. All rights reserved. //

#import #import

@interface AccelerometerViewController : UIViewController { double currentX; double currentY; double currentZ; } @property (weak, nonatomic) IBOutlet UIButton *startButton; @property (weak, nonatomic) IBOutlet UIButton *resetButton; @property (weak, nonatomic) IBOutlet UIButton *stopButton;

@property IBOutlet UILabel *xLabel; @property IBOutlet UILabel *yLabel; @property IBOutlet UILabel *zLabel;

@property IBOutlet UILabel *xMaxLabel; @property IBOutlet UILabel *yMaxLabel; @property IBOutlet UILabel *zMaxLabel;

@property CMMotionManager *motionManager;

-(IBAction)resetAccelerometer:(id)sender; -(IBAction)startAccelerometer:(id)sender; -(IBAction)stopAccelerometer:(id)sender; -(void)checkMaximumValue_CurrentX:(double)x CurrentY:(double)y CurrentZ:(double)z; -(void)setLabel_X:(double)x Label_Y:(double)y Label_Z:(double)z; @end

C.1.5. AccelerometerViewController.m // // ViewController.m // AccelerometerTest // // Created by Jordan on 2016-02-01. // Copyright © 2016 Jordan. All rights reserved. A Study of Modern Mobile Tablets - 154

//

#import "AccelerometerViewController.h"

@interface AccelerometerViewController ()

@end

@implementation AccelerometerViewController

//The viewDidLoad method is one of the first methods called when a new view is opened and should be used for initialization - (void)viewDidLoad { [super viewDidLoad];

//Set the initial values to 0.0 these will store the maximum values of the accelerometer. currentX = 0.0; currentY = 0.0; currentZ = 0.0;

//call the resetAccelerometer method which sets all the labels to their respective values. [self resetAccelerometer:self]; //Initialize the motion manager based on the CMMotionManager object self.motionManager = [[CMMotionManager alloc] init]; //This is the periodic timer that retreives accelerometer data every so many seconds //This periodic timer runs every twenty milliseconds self.motionManager.accelerometerUpdateInterval = 0.2;

}

- (void)didReceiveMemoryWarning { [super didReceiveMemoryWarning]; // Dispose of any resources that can be recreated. }

//Reset the accelerometer and max labels and reset the max values to zero -(IBAction)resetAccelerometer:(id)sender { //reset current maximum values currentX = 0.0; currentY = 0.0; currentZ = 0.0; //call setLabel so the all the Accelerometer X: , Accelerometer Y: , Accelerometer Z: labels are set to +0.0 [self setLabel_X:currentX Label_Y:currentY Label_Z:currentZ]; //call checkMaximumValue_CurrentX so the all the Max: labels are set to +0.0 [self checkMaximumValue_CurrentX:currentX CurrentY:currentY CurrentZ:currentZ]; } //startAccelerometer uses the motionmanager to create a queue of events that are displayed by labels A Study of Modern Mobile Tablets - 155

-(IBAction)startAccelerometer:(id)sender { //Create a queue of accelerometerData which can be retreived [self.motionManager startAccelerometerUpdatesToQueue:[NSOperationQueue currentQueue] withHandler:^(CMAccelerometerData *accelerometerData, NSError *error) { //pass the acceleration.x y and z valeus into the setLabel method. [self setLabel_X:accelerometerData.acceleration.x Label_Y:accelerometerData.acceleration.y Label_Z:accelerometerData.acceleration.z]; //pass the acceleration.x y and z values into the checkMaximum method to set the maximum amount of acceleration [self checkMaximumValue_CurrentX:accelerometerData.acceleration.x CurrentY:accelerometerData.acceleration.y CurrentZ:accelerometerData.acceleration.z]; //If an error occurs at anypoint while the accelerometer is trying to retreive data write it out to the console. if (error) { NSLog(@"%@", error); } } ];

} //Stops the acceleromter by telling the motionManager to stop retreiveing updates. -(IBAction)stopAccelerometer:(id)sender { [self.motionManager stopAccelerometerUpdates]; } //Sets the Acceleromter labels to the values passed as parameters -(void)setLabel_X:(double)x Label_Y:(double)y Label_Z:(double)z { //set the text displayed by the labels to the NSString object //The NSString uses the % to specifies that a variable should be substituted from a comma seperated list. //The + indicates that a sign should be placed in front of all values //The 0.2f indicates that only two decimal places should be shown. self.xLabel.text = [NSString stringWithFormat:@"Accelerometer X: %+0.2f",x]; self.yLabel.text = [NSString stringWithFormat:@"Accelerometer Y: %+0.2f",y]; self.zLabel.text = [NSString stringWithFormat:@"Accelerometer Z: %+0.2f",z]; } //determine what the maximum acceleration was -(void)checkMaximumValue_CurrentX:(double)x CurrentY:(double)y CurrentZ:(double)z { //fabs() returns the absolute value of the double given. //fabs() is required to get the maximum acceleration because it can be both positive or negative depending on the device orientation //The If statement uses the <= so that when the reset method is called it will reset the maximum values to +0.0 //This checks if the current maximum value is larger then the one being given. if(fabs(currentX) <= fabs(x)) { currentX = x; //set the maxlabel to the NSString object self.xMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f",x]; A Study of Modern Mobile Tablets - 156

} if(fabs(currentY) <= fabs(y)) { currentY = y; self.yMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f",y]; } if (fabs(currentZ) <= fabs(z)) { currentZ = z; self.zMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f",z]; } }

@end

C.2. Increment 2: Gyroscope, IOS

C.2.1. main.m // // main.m // GyroscopeTest // // Created by Jordan on 2016-02-15. // Copyright © 2016 Jordan. All rights reserved. //

#import #import "AppDelegate.h" int main(int argc, char * argv[]) { @autoreleasepool { return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class])); } }

C.2.2. AppDelegate.h // // AppDelegate.h // GyroscopeTest // // Created by Jordan on 2016-02-15. // Copyright © 2016 Jordan. All rights reserved. //

#import A Study of Modern Mobile Tablets - 157

@interface AppDelegate : UIResponder

@property (strong, nonatomic) UIWindow *window;

@end

C.2.3. AppDelegate.m // // AppDelegate.m // GyroscopeTest // // Created by Jordan on 2016-02-15. // Copyright © 2016 Jordan. All rights reserved. //

#import "AppDelegate.h"

@interface AppDelegate ()

@end

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { // Override point for customization after application launch. return YES; }

- (void)applicationWillResignActive:(UIApplication *)application { // Sent when the application is about to move from active to inactive state. This can occur for certain types of temporary interruptions (such as an incoming phone call or SMS message) or when the user quits the application and it begins the transition to the background state. // Use this method to pause ongoing tasks, disable timers, and throttle down OpenGL ES frame rates. Games should use this method to pause the game. }

- (void)applicationDidEnterBackground:(UIApplication *)application { // Use this method to release shared resources, save user data, invalidate timers, and store enough application state information to restore your application to its current state in case it is terminated later. // If your application supports background execution, this method is called instead of applicationWillTerminate: when the user quits. }

- (void)applicationWillEnterForeground:(UIApplication *)application { // Called as part of the transition from the background to the inactive state; here you can undo many of the changes A Study of Modern Mobile Tablets - 158

made on entering the background. }

- (void)applicationDidBecomeActive:(UIApplication *)application { // Restart any tasks that were paused (or not yet started) while the application was inactive. If the application was previously in the background, optionally refresh the user interface. }

- (void)applicationWillTerminate:(UIApplication *)application { // Called when the application is about to terminate. Save data if appropriate. See also applicationDidEnterBackground:. }

@end

C.2.4. GyroscopeViewController.h // // ViewController.h // GyroscopeTest // // Created by Jordan on 2016-02-15. // Copyright © 2016 Jordan. All rights reserved. //

#import #import

@interface GyroscopeViewController : UIViewController { double max_X; double max_Y; double max_Z;

double max_Roll; double max_Pitch; double max_Yaw; }

@property IBOutlet UILabel *xLabel; @property IBOutlet UILabel *yLabel; @property IBOutlet UILabel *zLabel;

@property IBOutlet UILabel *xMaxLabel; @property IBOutlet UILabel *yMaxLabel; @property IBOutlet UILabel *zMaxLabel;

@property IBOutlet UILabel *xRollLabel; @property IBOutlet UILabel *yPitchLabel; A Study of Modern Mobile Tablets - 159

@property IBOutlet UILabel *zYawLabel;

@property IBOutlet UILabel *xRollMaxLabel; @property IBOutlet UILabel *yPitchMaxLabel; @property IBOutlet UILabel *zYawMaxLabel;

@property (weak, nonatomic) IBOutlet UIButton *startButton; @property (weak, nonatomic) IBOutlet UIButton *resetButton; @property (weak, nonatomic) IBOutlet UIButton *stopButton;

@property CMMotionManager *motionManager;

-(IBAction)resetGyroscope:(id)sender; -(IBAction)startGyroscope:(id)sender; -(IBAction)stopGyroscope:(id)sender;

-(double)convertRadianToDegree:(double)radian; -(void)checkMaximumValue_CurrentX:(double)x CurrentY:(double)y CurrentZ:(double)z; -(void)checkMaximumValue_Roll:(double)x Pitch:(double)y Yaw:(double)z; -(void)setRoll:(double)x Pitch:(double)y Yaw:(double)z; -(void)setLabel_X:(double)x Label_Y:(double)y Label_Z:(double)z;

@end

C.2.5. GyroscopeViewController.m // // ViewController.m // GyroscopeTest // // Created by Jordan on 2016-02-15. // Copyright © 2016 Jordan. All rights reserved. //

#import "GyroscopeViewController.h"

@interface GyroscopeViewController ()

@end

@implementation GyroscopeViewController

- (void)viewDidLoad { [super viewDidLoad];

//call the resetGyroscope method which sets all the labels to their initial values. [self resetGyroscope:self]; //Initialize the motion manager based on the CMMotionManager object so we can access the gyroscope and attitude A Study of Modern Mobile Tablets - 160

self.motionManager = [[CMMotionManager alloc] init]; //This is the periodic timer that retreives gyroscope data every so many seconds //This periodic timer runs every twenty milliseconds self.motionManager.gyroUpdateInterval = 0.2; //this is another timer for getting attitude changes set to twenty milliseconds self.motionManager.deviceMotionUpdateInterval = 0.2;

}

- (void)didReceiveMemoryWarning { [super didReceiveMemoryWarning]; // Dispose of any resources that can be recreated. } -(IBAction)resetGyroscope:(id)sender { //reset current maximum values max_X = 0.0; max_Y = 0.0; max_Z = 0.0; max_Roll = 0.0; max_Pitch = 0.0; max_Yaw = 0.0; //call setLabel so the all the Gyroscope X: , Gyroscope Y: , Gyroscope Z: labels are set to +0.0 [self setLabel_X:max_X Label_Y:max_Y Label_Z:max_Z];

//call checkMaximumValue_CurrentX so the all the Max: labels are set to +0.0 [self checkMaximumValue_CurrentX:max_X CurrentY:max_Y CurrentZ:max_Z]; //call setRoll so that Roll: , Pitch: , and Yaw: labels are set to +0.0 [self setRoll:max_X Pitch:max_Y Yaw:max_Z]; //call setMaxValues_Roll so that Max: labels are set to +0.0 [self checkMaximumValue_Roll:max_Roll Pitch:max_Pitch Yaw:max_Yaw]; } -(IBAction)startGyroscope:(id)sender { //attitude is the change in rotation based on the devices initial position. //Create a queue of containing raw attitude data which can be used and displayed [self.motionManager startDeviceMotionUpdatesToQueue:[NSOperationQueue currentQueue] withHandler:^(CMDeviceMotion *deviceMotion, NSError *error) { //update the roll, pitch, and yaw labels [self setRoll:deviceMotion.attitude.roll Pitch:deviceMotion.attitude.pitch Yaw:deviceMotion.attitude.yaw]; [self checkMaximumValue_Roll:deviceMotion.attitude.roll Pitch:deviceMotion.attitude.pitch Yaw:deviceMotion.attitude.yaw]; //if any errors occur display them in console A Study of Modern Mobile Tablets - 161

if (error) { NSLog(@"%@", error); } } ];

//Create a queue of containing raw gyroscope data which can be used and displayed [self.motionManager startGyroUpdatesToQueue:[NSOperationQueue currentQueue] withHandler:^(CMGyroData *gyroscopeData, NSError *error) { //pass the rotationRate.x y and z values into the setLabel method. [self setLabel_X:gyroscopeData.rotationRate.x Label_Y:gyroscopeData.rotationRate.y Label_Z:gyroscopeData.rotationRate.z]; //pass the rotationRate.x y and z values into the checkMaximum method to set the maximum rotationrate [self checkMaximumValue_CurrentX:gyroscopeData.rotationRate.x CurrentY:gyroscopeData.rotationRate.y CurrentZ:gyroscopeData.rotationRate.z];

//If an error occurs because of the gyroscope write it out to the console. if (error) { NSLog(@"%@", error); } } ];

} -(IBAction)stopGyroscope:(id)sender { //make sure to stop the gyroupdates and motion updates [self.motionManager stopGyroUpdates]; [self.motionManager stopDeviceMotionUpdates];

}

//Sets the Gyroscope labels to the values passed as parameters -(void)setLabel_X:(double)x Label_Y:(double)y Label_Z:(double)z { //set the text displayed by the labels to the NSString object //The NSString uses the % to specifies that a variable should be substituted from a comma seperated list. //The + indicates that a sign should be placed in front of all values //The 0.2f indicates that only two decimal places should be shown. //The \u00b0 is the unicode representation of the degree symbol //The convertRadianToDegree method is used because it is easier to visualize compared to radians self.xLabel.text = [NSString stringWithFormat:@"Gyroscope X: %+0.2f\u00b0",[self convertRadianToDegree:x]]; self.yLabel.text = [NSString stringWithFormat:@"Gyroscope Y: %+0.2f\u00b0",[self convertRadianToDegree:y]]; self.zLabel.text = [NSString stringWithFormat:@"Gyroscope Z: %+0.2f\u00b0",[self convertRadianToDegree:z]]; }

//Sets the Gyroscope labels to the values passed as parameters A Study of Modern Mobile Tablets - 162

-(void)setRoll:(double)x Pitch:(double)y Yaw:(double)z { //set the text displayed by the labels to the NSString object //The NSString uses the % to specifies that a variable should be substituted from a comma seperated list. //The + indicates that a sign should be placed in front of all values //The 0.2f indicates that only two decimal places should be shown. //The \u00b0 is the unicode representation of the degree symbol //The convertRadianToDegree method is used because it is easier to visualize compared to radians self.xRollLabel.text = [NSString stringWithFormat:@"Roll: %+0.2f\u00b0",[self convertRadianToDegree:x]]; self.yPitchLabel.text = [NSString stringWithFormat:@"Pitch: %+0.2f\u00b0",[self convertRadianToDegree:y]]; self.zYawLabel.text = [NSString stringWithFormat:@"Yaw: %+0.2f\u00b0",[self convertRadianToDegree:z]]; }

//determine what the maximum gyroscope rotation rate was -(void)checkMaximumValue_CurrentX:(double)x CurrentY:(double)y CurrentZ:(double)z { //fabs() returns the absolute value of the double given. //fabs() is required to get the maximum acceleration because it can be both positive or negative depending on the device orientation //The If statement uses the <= so that when the reset method is called it will reset the maximum values to +0.0 //This checks if the current maximum value is larger then the one being given. if(fabs(max_X) <= fabs(x)) { max_X = x; //set the maxlabel to the NSString object self.xMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f\u00b0",[self convertRadianToDegree:x]]; } if(fabs(max_Y) <= fabs(y)) { max_Y = y; self.yMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f\u00b0",[self convertRadianToDegree:y]]; } if (fabs(max_Z) <= fabs(z)) { max_Z = z; self.zMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f\u00b0",[self convertRadianToDegree:z]]; } }

-(void)checkMaximumValue_Roll:(double)x Pitch:(double)y Yaw:(double)z { //fabs() returns the absolute value of the double given. //fabs() is required to get the maximum acceleration because it can be both positive or negative depending on the device orientation //The If statement uses the <= so that when the reset method is called it will reset the maximum values to +0.0 //This checks if the current maximum value is larger then the one being given. if(fabs(max_Roll) <= fabs(x)) { max_Roll = x; //set the maxlabel to the NSString object self.xRollMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f\u00b0",[self convertRadianToDegree:x]]; } A Study of Modern Mobile Tablets - 163

if(fabs(max_Pitch) <= fabs(y)) { max_Pitch = y; self.yPitchMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f\u00b0",[self convertRadianToDegree:y]]; } if (fabs(max_Yaw) <= fabs(z)) { max_Yaw = z; self.zYawMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f\u00b0",[self convertRadianToDegree:z]]; } } //converts radians to degrees -(double)convertRadianToDegree:(double)radian { return (radian * (180.0/M_PI)); } @end C.3. Increment 3: Integration, IOS

C.3.1. main.m // // main.m // IOSSensorApplication // // Created by Jordan on 2016-03-23. // Copyright © 2016 Jordan. All rights reserved. //

#import #import "AppDelegate.h" int main(int argc, char * argv[]) { @autoreleasepool { return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class])); } }

C.3.2. AppDelegate.h // // AppDelegate.h // IOSSensorApplication // // Created by Jordan on 2016-02-29. // Copyright © 2016 Jordan. All rights reserved. //

#import

@interface AppDelegate : UIResponder A Study of Modern Mobile Tablets - 164

@property (strong, nonatomic) UIWindow *window;

@end

C.3.3. AppDelegate.m // // AppDelegate.m // IOSSensorApplication // // Created by Jordan on 2016-02-29. // Copyright © 2016 Jordan. All rights reserved. //

#import "AppDelegate.h"

@interface AppDelegate ()

@end

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { // Override point for customization after application launch. return YES; }

- (void)applicationWillResignActive:(UIApplication *)application { // Sent when the application is about to move from active to inactive state. This can occur for certain types of temporary interruptions (such as an incoming phone call or SMS message) or when the user quits the application and it begins the transition to the background state. // Use this method to pause ongoing tasks, disable timers, and throttle down OpenGL ES frame rates. Games should use this method to pause the game. }

- (void)applicationDidEnterBackground:(UIApplication *)application { // Use this method to release shared resources, save user data, invalidate timers, and store enough application state information to restore your application to its current state in case it is terminated later. // If your application supports background execution, this method is called instead of applicationWillTerminate: when the user quits. }

- (void)applicationWillEnterForeground:(UIApplication *)application { // Called as part of the transition from the background to the inactive state; here you can undo many of the changes made on entering the background. A Study of Modern Mobile Tablets - 165

}

- (void)applicationDidBecomeActive:(UIApplication *)application { // Restart any tasks that were paused (or not yet started) while the application was inactive. If the application was previously in the background, optionally refresh the user interface. }

- (void)applicationWillTerminate:(UIApplication *)application { // Called when the application is about to terminate. Save data if appropriate. See also applicationDidEnterBackground:. }

@end

C.3.4. AccelerometerViewController.h // // ViewController.h // AccelerometerTest // // Created by Jordan on 2016-02-01. // Copyright © 2016 Jordan. All rights reserved. //

#import #import

@interface AccelerometerViewController : UIViewController { double currentX; double currentY; double currentZ; } @property (weak, nonatomic) IBOutlet UIButton *startButton; @property (weak, nonatomic) IBOutlet UIButton *resetButton; @property (weak, nonatomic) IBOutlet UIButton *stopButton;

@property IBOutlet UILabel *xLabel; @property IBOutlet UILabel *yLabel; @property IBOutlet UILabel *zLabel;

@property IBOutlet UILabel *xMaxLabel; @property IBOutlet UILabel *yMaxLabel; @property IBOutlet UILabel *zMaxLabel;

@property CMMotionManager *motionManager;

-(IBAction)resetAccelerometer:(id)sender; -(IBAction)startAccelerometer:(id)sender; A Study of Modern Mobile Tablets - 166

-(IBAction)stopAccelerometer:(id)sender; -(void)checkMaximumValue_CurrentX:(double)x CurrentY:(double)y CurrentZ:(double)z; -(void)setLabel_X:(double)x Label_Y:(double)y Label_Z:(double)z; @end

C.3.5. AccelerometerViewController.m // // ViewController.m // AccelerometerTest // // Created by Jordan on 2016-02-01. // Copyright © 2016 Jordan. All rights reserved. //

#import "AccelerometerViewController.h"

@interface AccelerometerViewController ()

@end

@implementation AccelerometerViewController

//The viewDidLoad method is one of the first methods called when a new view is opened and should be used for initialization - (void)viewDidLoad { [super viewDidLoad];

//Set the initial values to 0.0 these will store the maximum values of the accelerometer. currentX = 0.0; currentY = 0.0; currentZ = 0.0;

//call the resetAccelerometer method which sets all the labels to their respective values. [self resetAccelerometer:self]; //Initialize the motion manager based on the CMMotionManager object self.motionManager = [[CMMotionManager alloc] init]; //This is the periodic timer that retreives accelerometer data every so many seconds //This periodic timer runs every twenty milliseconds self.motionManager.accelerometerUpdateInterval = 0.2;

}

- (void)didReceiveMemoryWarning { [super didReceiveMemoryWarning]; // Dispose of any resources that can be recreated. }

//Reset the accelerometer and max labels and reset the max values to zero A Study of Modern Mobile Tablets - 167

-(IBAction)resetAccelerometer:(id)sender { //reset current maximum values currentX = 0.0; currentY = 0.0; currentZ = 0.0; //call setLabel so the all the Accelerometer X: , Accelerometer Y: , Accelerometer Z: labels are set to +0.0 [self setLabel_X:currentX Label_Y:currentY Label_Z:currentZ]; //call checkMaximumValue_CurrentX so the all the Max: labels are set to +0.0 [self checkMaximumValue_CurrentX:currentX CurrentY:currentY CurrentZ:currentZ]; } //startAccelerometer uses the motionmanager to create a queue of events that are displayed by labels -(IBAction)startAccelerometer:(id)sender { //Create a queue of accelerometerData which can be retreived [self.motionManager startAccelerometerUpdatesToQueue:[NSOperationQueue currentQueue] withHandler:^(CMAccelerometerData *accelerometerData, NSError *error) { //pass the acceleration.x y and z valeus into the setLabel method. [self setLabel_X:accelerometerData.acceleration.x Label_Y:accelerometerData.acceleration.y Label_Z:accelerometerData.acceleration.z]; //pass the acceleration.x y and z values into the checkMaximum method to set the maximum amount of acceleration [self checkMaximumValue_CurrentX:accelerometerData.acceleration.x CurrentY:accelerometerData.acceleration.y CurrentZ:accelerometerData.acceleration.z]; //If an error occurs at anypoint while the accelerometer is trying to retreive data write it out to the console. if (error) { NSLog(@"%@", error); } } ];

} //Stops the acceleromter by telling the motionManager to stop retreiveing updates. -(IBAction)stopAccelerometer:(id)sender { [self.motionManager stopAccelerometerUpdates]; } //Sets the Acceleromter labels to the values passed as parameters -(void)setLabel_X:(double)x Label_Y:(double)y Label_Z:(double)z { //set the text displayed by the labels to the NSString object //The NSString uses the % to specifies that a variable should be substituted from a comma seperated list. //The + indicates that a sign should be placed in front of all values //The 0.2f indicates that only two decimal places should be shown. self.xLabel.text = [NSString stringWithFormat:@"Accelerometer X: %+0.2f",x]; self.yLabel.text = [NSString stringWithFormat:@"Accelerometer Y: %+0.2f",y]; self.zLabel.text = [NSString stringWithFormat:@"Accelerometer Z: %+0.2f",z]; A Study of Modern Mobile Tablets - 168

} //determine what the maximum acceleration was -(void)checkMaximumValue_CurrentX:(double)x CurrentY:(double)y CurrentZ:(double)z { //fabs() returns the absolute value of the double given. //fabs() is required to get the maximum acceleration because it can be both positive or negative depending on the device orientation //The If statement uses the <= so that when the reset method is called it will reset the maximum values to +0.0 //This checks if the current maximum value is larger then the one being given. if(fabs(currentX) <= fabs(x)) { currentX = x; //set the maxlabel to the NSString object self.xMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f",x]; } if(fabs(currentY) <= fabs(y)) { currentY = y; self.yMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f",y]; } if (fabs(currentZ) <= fabs(z)) { currentZ = z; self.zMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f",z]; } }

@end

C.3.6. GyroscopeViewController.h // // ViewController.h // GyroscopeTest // // Created by Jordan on 2016-02-15. // Copyright © 2016 Jordan. All rights reserved. //

#import #import

@interface GyroscopeViewController : UIViewController { double max_X; double max_Y; double max_Z;

double max_Roll; double max_Pitch; A Study of Modern Mobile Tablets - 169

double max_Yaw; }

@property IBOutlet UILabel *xLabel; @property IBOutlet UILabel *yLabel; @property IBOutlet UILabel *zLabel;

@property IBOutlet UILabel *xMaxLabel; @property IBOutlet UILabel *yMaxLabel; @property IBOutlet UILabel *zMaxLabel;

@property IBOutlet UILabel *xRollLabel; @property IBOutlet UILabel *yPitchLabel; @property IBOutlet UILabel *zYawLabel;

@property IBOutlet UILabel *xRollMaxLabel; @property IBOutlet UILabel *yPitchMaxLabel; @property IBOutlet UILabel *zYawMaxLabel;

@property (weak, nonatomic) IBOutlet UIButton *startButton; @property (weak, nonatomic) IBOutlet UIButton *resetButton; @property (weak, nonatomic) IBOutlet UIButton *stopButton;

@property CMMotionManager *motionManager;

-(IBAction)resetGyroscope:(id)sender; -(IBAction)startGyroscope:(id)sender; -(IBAction)stopGyroscope:(id)sender;

-(double)convertRadianToDegree:(double)radian; -(void)checkMaximumValue_CurrentX:(double)x CurrentY:(double)y CurrentZ:(double)z; -(void)checkMaximumValue_Roll:(double)x Pitch:(double)y Yaw:(double)z; -(void)setRoll:(double)x Pitch:(double)y Yaw:(double)z; -(void)setLabel_X:(double)x Label_Y:(double)y Label_Z:(double)z;

@end

C.3.7. GyroscopeViewController.m // // ViewController.m // GyroscopeTest // // Created by Jordan on 2016-02-15. // Copyright © 2016 Jordan. All rights reserved. //

#import "GyroscopeViewController.h"

@interface GyroscopeViewController () A Study of Modern Mobile Tablets - 170

@end

@implementation GyroscopeViewController

- (void)viewDidLoad { [super viewDidLoad];

//call the resetGyroscope method which sets all the labels to their initial values. [self resetGyroscope:self]; //Initialize the motion manager based on the CMMotionManager object so we can access the gyroscope and attitude self.motionManager = [[CMMotionManager alloc] init]; //This is the periodic timer that retreives gyroscope data every so many seconds //This periodic timer runs every twenty milliseconds self.motionManager.gyroUpdateInterval = 0.2; //this is another timer for getting attitude changes set to twenty milliseconds self.motionManager.deviceMotionUpdateInterval = 0.2;

}

- (void)didReceiveMemoryWarning { [super didReceiveMemoryWarning]; // Dispose of any resources that can be recreated. } -(IBAction)resetGyroscope:(id)sender { //reset current maximum values max_X = 0.0; max_Y = 0.0; max_Z = 0.0; max_Roll = 0.0; max_Pitch = 0.0; max_Yaw = 0.0; //call setLabel so the all the Gyroscope X: , Gyroscope Y: , Gyroscope Z: labels are set to +0.0 [self setLabel_X:max_X Label_Y:max_Y Label_Z:max_Z];

//call checkMaximumValue_CurrentX so the all the Max: labels are set to +0.0 [self checkMaximumValue_CurrentX:max_X CurrentY:max_Y CurrentZ:max_Z]; //call setRoll so that Roll: , Pitch: , and Yaw: labels are set to +0.0 [self setRoll:max_X Pitch:max_Y Yaw:max_Z]; //call setMaxValues_Roll so that Max: labels are set to +0.0 [self checkMaximumValue_Roll:max_Roll Pitch:max_Pitch Yaw:max_Yaw]; } -(IBAction)startGyroscope:(id)sender { //attitude is the change in rotation based on the devices initial position. //Create a queue of containing raw attitude data which can be used and displayed A Study of Modern Mobile Tablets - 171

[self.motionManager startDeviceMotionUpdatesToQueue:[NSOperationQueue currentQueue] withHandler:^(CMDeviceMotion *deviceMotion, NSError *error) { //update the roll, pitch, and yaw labels [self setRoll:deviceMotion.attitude.roll Pitch:deviceMotion.attitude.pitch Yaw:deviceMotion.attitude.yaw]; [self checkMaximumValue_Roll:deviceMotion.attitude.roll Pitch:deviceMotion.attitude.pitch Yaw:deviceMotion.attitude.yaw]; //if any errors occur display them in console if (error) { NSLog(@"%@", error); } } ];

//Create a queue of containing raw gyroscope data which can be used and displayed [self.motionManager startGyroUpdatesToQueue:[NSOperationQueue currentQueue] withHandler:^(CMGyroData *gyroscopeData, NSError *error) { //pass the rotationRate.x y and z values into the setLabel method. [self setLabel_X:gyroscopeData.rotationRate.x Label_Y:gyroscopeData.rotationRate.y Label_Z:gyroscopeData.rotationRate.z]; //pass the rotationRate.x y and z values into the checkMaximum method to set the maximum rotationrate [self checkMaximumValue_CurrentX:gyroscopeData.rotationRate.x CurrentY:gyroscopeData.rotationRate.y CurrentZ:gyroscopeData.rotationRate.z];

//If an error occurs because of the gyroscope write it out to the console. if (error) { NSLog(@"%@", error); } } ];

} -(IBAction)stopGyroscope:(id)sender { //make sure to stop the gyroupdates and motion updates [self.motionManager stopGyroUpdates]; [self.motionManager stopDeviceMotionUpdates];

}

//Sets the Gyroscope labels to the values passed as parameters -(void)setLabel_X:(double)x Label_Y:(double)y Label_Z:(double)z { //set the text displayed by the labels to the NSString object A Study of Modern Mobile Tablets - 172

//The NSString uses the % to specifies that a variable should be substituted from a comma seperated list. //The + indicates that a sign should be placed in front of all values //The 0.2f indicates that only two decimal places should be shown. //The \u00b0 is the unicode representation of the degree symbol //The convertRadianToDegree method is used because it is easier to visualize compared to radians self.xLabel.text = [NSString stringWithFormat:@"Gyroscope X: %+0.2f\u00b0",[self convertRadianToDegree:x]]; self.yLabel.text = [NSString stringWithFormat:@"Gyroscope Y: %+0.2f\u00b0",[self convertRadianToDegree:y]]; self.zLabel.text = [NSString stringWithFormat:@"Gyroscope Z: %+0.2f\u00b0",[self convertRadianToDegree:z]]; }

//Sets the Gyroscope labels to the values passed as parameters -(void)setRoll:(double)x Pitch:(double)y Yaw:(double)z { //set the text displayed by the labels to the NSString object //The NSString uses the % to specifies that a variable should be substituted from a comma seperated list. //The + indicates that a sign should be placed in front of all values //The 0.2f indicates that only two decimal places should be shown. //The \u00b0 is the unicode representation of the degree symbol //The convertRadianToDegree method is used because it is easier to visualize compared to radians self.xRollLabel.text = [NSString stringWithFormat:@"Roll: %+0.2f\u00b0",[self convertRadianToDegree:x]]; self.yPitchLabel.text = [NSString stringWithFormat:@"Pitch: %+0.2f\u00b0",[self convertRadianToDegree:y]]; self.zYawLabel.text = [NSString stringWithFormat:@"Yaw: %+0.2f\u00b0",[self convertRadianToDegree:z]]; }

//determine what the maximum gyroscope rotation rate was -(void)checkMaximumValue_CurrentX:(double)x CurrentY:(double)y CurrentZ:(double)z { //fabs() returns the absolute value of the double given. //fabs() is required to get the maximum acceleration because it can be both positive or negative depending on the device orientation //The If statement uses the <= so that when the reset method is called it will reset the maximum values to +0.0 //This checks if the current maximum value is larger then the one being given. if(fabs(max_X) <= fabs(x)) { max_X = x; //set the maxlabel to the NSString object self.xMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f\u00b0",[self convertRadianToDegree:x]]; } if(fabs(max_Y) <= fabs(y)) { max_Y = y; self.yMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f\u00b0",[self convertRadianToDegree:y]]; } if (fabs(max_Z) <= fabs(z)) { max_Z = z; self.zMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f\u00b0",[self convertRadianToDegree:z]]; } }

-(void)checkMaximumValue_Roll:(double)x Pitch:(double)y Yaw:(double)z { A Study of Modern Mobile Tablets - 173

//fabs() returns the absolute value of the double given. //fabs() is required to get the maximum acceleration because it can be both positive or negative depending on the device orientation //The If statement uses the <= so that when the reset method is called it will reset the maximum values to +0.0 //This checks if the current maximum value is larger then the one being given. if(fabs(max_Roll) <= fabs(x)) { max_Roll = x; //set the maxlabel to the NSString object self.xRollMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f\u00b0",[self convertRadianToDegree:x]]; } if(fabs(max_Pitch) <= fabs(y)) { max_Pitch = y; self.yPitchMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f\u00b0",[self convertRadianToDegree:y]]; } if (fabs(max_Yaw) <= fabs(z)) { max_Yaw = z; self.zYawMaxLabel.text = [NSString stringWithFormat:@"Max: %+0.2f\u00b0",[self convertRadianToDegree:z]]; } } //converts radians to degrees -(double)convertRadianToDegree:(double)radian { return (radian * (180.0/M_PI)); } @end

C.3.8. MainViewController.h // // ViewController.h // IOSSensorApplication // // Created by Jordan on 2016-02-29. // Copyright © 2016 Jordan. All rights reserved. //

#import

@interface MainViewController : UIViewController

@end

D.3.9. MainViewController.m // // ViewController.m A Study of Modern Mobile Tablets - 174

// IOSSensorApplication // // Created by Jordan on 2016-02-29. // Copyright © 2016 Jordan. All rights reserved. //

#import "MainViewController.h"

@interface MainViewController ()

@end

@implementation MainViewController

- (void)viewDidLoad { [super viewDidLoad]; // Do any additional setup after loading the view, typically from a nib. }

- (void)didReceiveMemoryWarning { [super didReceiveMemoryWarning]; // Dispose of any resources that can be recreated. }

@end

C.4. Increment 4: Accelerometer, Windows 8

C.4.1. App.xaml

A Study of Modern Mobile Tablets - 175

C.4.2. App.xaml.cs using System; using System.Collections.Generic; using System.IO; using System.Linq; using Windows.ApplicationModel; using Windows.ApplicationModel.Activation; using Windows.Foundation; using Windows.Foundation.Collections; using Windows.UI.Xaml; using Windows.UI.Xaml.Controls; using Windows.UI.Xaml.Controls.Primitives; using Windows.UI.Xaml.Data; using Windows.UI.Xaml.Input; using Windows.UI.Xaml.Media; using Windows.UI.Xaml.Navigation;

/* * This page was not modified in this version other then a few additional comments * When creating a windows store application using a blankApp the App.xaml, App.xaml.cs, MainPage.xaml, and MainPage.xaml.cs * are all created using a default template. * Author: Jordan Kahtava * Date: 2016-03-07 * */ namespace AccelerometerTest { ///

/// Provides application-specific behavior to supplement the default Application class. ///

sealed partial class App : Application { ///

/// Initializes the singleton application object. This is the first line of authored code /// executed, and as such is the logical equivalent of main() or WinMain(). ///

public App() { this.InitializeComponent(); this.Suspending += OnSuspending; }

///

/// Invoked when the application is launched normally by the end user. Other entry points /// will be used when the application is launched to open a specific file, to display /// search results, and so forth. ///

A Study of Modern Mobile Tablets - 176

/// Details about the launch request and process. protected override void OnLaunched(LaunchActivatedEventArgs args) { Frame rootFrame = Window.Current.Content as Frame;

// Do not repeat app initialization when the Window already has content, // just ensure that the window is active if (rootFrame == null) { // Create a Frame to act as the navigation context and navigate to the first page rootFrame = new Frame();

if (args.PreviousExecutionState == ApplicationExecutionState.Terminated) { // Load state from previously suspended application }

// Place the frame in the current Window Window.Current.Content = rootFrame; }

if (rootFrame.Content == null) { // When the navigation stack isn't restored navigate to the first page, // configuring the new page by passing required information as a navigation // parameter

//This is what opens the first page or mainpage if (!rootFrame.Navigate(typeof(MainPage), args.Arguments)) { throw new Exception("Failed to create initial page"); } } // Ensure the current window is active Window.Current.Activate(); }

///

/// Invoked when application execution is being suspended. Application state is saved /// without knowing whether the application will be terminated or resumed with the contents /// of memory still intact. ///

/// The source of the suspend request. /// Details about the suspend request. private void OnSuspending(object sender, SuspendingEventArgs e) { var deferral = e.SuspendingOperation.GetDeferral(); // Save application state and stop any background activity deferral.Complete(); } } }

A Study of Modern Mobile Tablets - 177

C.4.3. MainPage.xaml

Foreground="Black" FontSize="14.667"/>

C.4.4. MainPage.xaml.cs using System; using System.Collections.Generic; using System.IO; using System.Linq; using Windows.Foundation; using Windows.Foundation.Collections; using Windows.UI.Xaml; using Windows.UI.Xaml.Controls; using Windows.UI.Xaml.Controls.Primitives; using Windows.UI.Xaml.Data; using Windows.UI.Xaml.Input; using Windows.UI.Xaml.Media; using Windows.UI.Xaml.Navigation; using Windows.Devices.Sensors; using Windows.UI.Core;

/* * A very basic test that displays accelerometer data onto 3 labels * The maximum values are displayed on 3 different labels so you can determine how fast the device is moving * The maximum labels are required otherwise it would be nearly impossible to determine how fast the device was moving * It is hard to focus on the labels when the device is moving * * Accelerometer: "This sensor returns G-force values with respect to the x, y, and z axes." * (https://msdn.microsoft.com/en-us/library/windows/apps/windows.devices.sensors.accelerometer.aspx) * Author: Jordan Kahtava * Date: 2016-03-07 */ namespace AccelerometerTest {

public sealed partial class MainPage : Page { private Accelerometer accelerometer; private uint interval; private double currentX; private double currentY; private double currentZ; private Boolean startPressed = false;

public MainPage() { this.InitializeComponent(); //retreive the current accelerometer sensor null if none exists accelerometer = Accelerometer.GetDefault(); A Study of Modern Mobile Tablets - 179

interval = 20; //call the resetAccelerometer Button method to perform reset actions ResetAccelerometer(null, null);

}

///

/// Invoked when this page is about to be displayed in a Frame. ///

/// Event data that describes how this page was reached. The Parameter /// property is typically used to configure the page. protected override void OnNavigatedTo(NavigationEventArgs e) {

} //an asynchronous message is used so that no lag occurs between the UI and retreiving accelerometer readings async private void AccelerometerChanged(object sender, AccelerometerReadingChangedEventArgs e) { //unload the acceleration readings to another thread await Dispatcher.RunAsync(CoreDispatcherPriority.Normal, () => { //call update labels and update max with the acceleration values SetLabels(e.Reading.AccelerationX, e.Reading.AccelerationY, e.Reading.AccelerationZ); CheckMaximumValue(e.Reading.AccelerationX, e.Reading.AccelerationY, e.Reading.AccelerationZ); }); }

//update all the Accelerometer X: labels to show accleroemeter readings or any other double value private void SetLabels(double x, double y, double z) { //0,5 indicates that numbers should be aligned to the right //+0.## indicates to show 2 decimal places and always show + sign //-0.## indicates to show 2 decimal places and always show - sign if value is negative xLabel.Text = String.Format("Accelerometer X: {0,5:+0.00;-0.00}", x); yLabel.Text = String.Format("Accelerometer Y: {0,5:+0.00;-0.00}", y); zLabel.Text = String.Format("Accelerometer Z: {0,5:+0.00;-0.00}", z);

} //update the maximum labels so they show the highest acceleration private void CheckMaximumValue(double x, double y, double z) { //Math.Abs returns the absolute value of the given double so we can check which was higher //This is required since values can be both positive and negative representing the movement in opposite directions if(Math.Abs(currentX) <= Math.Abs(x)) { currentX = x; xMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", x); } if (Math.Abs(currentY) <= Math.Abs(y)) { currentY = y; yMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", y); } if (Math.Abs(currentZ) <= Math.Abs(z)) { currentZ = z; zMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", z); } A Study of Modern Mobile Tablets - 180

} //Reset all the labels when a user clicks on the Reset Accelerometer Button as specified by MainPage.xaml private void ResetAccelerometer(object sender, RoutedEventArgs e) { //reset the current max values to 0 currentX = 0.0; currentY = 0.0; currentZ = 0.0; //update the max values CheckMaximumValue(currentX, currentY, currentZ); //update the accelerometer labels SetLabels(currentX, currentY, currentZ); }

//Stop the Accelerometer event handler when a user clicks on the Stop Accelerometer Button as specified by MainPage.xaml private void StopAccelerometer(object sender, RoutedEventArgs e) { //only attempt to turn off the accelerometer if an accelerometer event handler was already attached if(startPressed == true) { //tell the application that the start button can be pressed again startPressed = false; //This disables the accelerometers event handler so that AccelerometerChanged is nolonger called accelerometer.ReadingChanged -= new TypedEventHandler(AccelerometerChanged); //set the reportinterval to 0 so we can release resources accelerometer.ReportInterval = 0; }

}

//Start the accelerometer when a user clicks on the Start Accelerometer Button as specified by MainPage.xaml private void StartAccelerometer(object sender, RoutedEventArgs e) { //check to make sure an accelerometer exists null indicates no sensor detected. //check to make sure the button wasnt already clicked otherwise multiple accelerometer event handlers will be attached if(accelerometer != null && startPressed == false) { //tell the application that start was pressed startPressed = true; //enables the accelerometer using the interval specified in milliseconds //events are only run if the device is moved otherwise it waits accelerometer.ReportInterval = interval; //attach a readingchanged event handler that runs the AccelerometerChanged() method accelerometer.ReadingChanged += new TypedEventHandler(AccelerometerChanged);

} } } }

A Study of Modern Mobile Tablets - 181

C.5. Increment 5: Gyroscope, Windows 8

C.5.1. App.xaml

D.5.2. App.xaml.cs using System; using System.Collections.Generic; using System.IO; using System.Linq; using Windows.ApplicationModel; using Windows.ApplicationModel.Activation; using Windows.Foundation; using Windows.Foundation.Collections; using Windows.UI.Xaml; using Windows.UI.Xaml.Controls; using Windows.UI.Xaml.Controls.Primitives; using Windows.UI.Xaml.Data; using Windows.UI.Xaml.Input; using Windows.UI.Xaml.Media; using Windows.UI.Xaml.Navigation;

/* * This page was not modified in this version other then a few additional comments * When creating a windows store application using a blankApp the App.xaml, App.xaml.cs, MainPage.xaml, and MainPage.xaml.cs * are all created using a default template. * Author: Jordan Kahtava * Date: 2016-03-14 * */ namespace GyroscopeTest { ///

/// Provides application-specific behavior to supplement the default Application class. ///

sealed partial class App : Application A Study of Modern Mobile Tablets - 182

{ ///

/// Initializes the singleton application object. This is the first line of authored code /// executed, and as such is the logical equivalent of main() or WinMain(). ///

public App() { this.InitializeComponent(); this.Suspending += OnSuspending; }

///

/// Invoked when the application is launched normally by the end user. Other entry points /// will be used when the application is launched to open a specific file, to display /// search results, and so forth. ///

/// Details about the launch request and process. protected override void OnLaunched(LaunchActivatedEventArgs args) { Frame rootFrame = Window.Current.Content as Frame;

// Do not repeat app initialization when the Window already has content, // just ensure that the window is active if (rootFrame == null) { // Create a Frame to act as the navigation context and navigate to the first page rootFrame = new Frame();

if (args.PreviousExecutionState == ApplicationExecutionState.Terminated) { // Load state from previously suspended application }

// Place the frame in the current Window Window.Current.Content = rootFrame; }

if (rootFrame.Content == null) { // When the navigation stack isn't restored navigate to the first page, // configuring the new page by passing required information as a navigation // parameter

//This is what opens the first page or mainpage if (!rootFrame.Navigate(typeof(MainPage), args.Arguments)) { throw new Exception("Failed to create initial page"); } } // Ensure the current window is active Window.Current.Activate(); }

///

/// Invoked when application execution is being suspended. Application state is saved /// without knowing whether the application will be terminated or resumed with the contents /// of memory still intact. ///

A Study of Modern Mobile Tablets - 183

/// The source of the suspend request. /// Details about the suspend request. private void OnSuspending(object sender, SuspendingEventArgs e) { var deferral = e.SuspendingOperation.GetDeferral(); //Save application state and stop any background activity deferral.Complete(); } } }

C.5.3. MainPage.xaml

A Study of Modern Mobile Tablets - 184

C.5.4. MainPage.xaml.cs using System; using System.Collections.Generic; using System.IO; using System.Linq; using Windows.Foundation; using Windows.Foundation.Collections; using Windows.UI.Xaml; using Windows.UI.Xaml.Controls; using Windows.UI.Xaml.Controls.Primitives; using Windows.UI.Xaml.Data; using Windows.UI.Xaml.Input; using Windows.UI.Xaml.Media; using Windows.UI.Xaml.Navigation; using Windows.Devices.Sensors; using Windows.UI.Core; /* A very basic test that outputs gyroscope data and inclinometer data to 6 different labels * The maximum values are also updated on 6 other labels * Inclinometer: "This sensor returns pitch, roll, and yaw values that correspond to rotation angles around the x, y, and z axes, respectively." * (https://msdn.microsoft.com/en-us/library/windows/apps/windows.devices.sensors.inclinometer.aspx) * A Study of Modern Mobile Tablets - 185

* Gyroscope: "This sensor returns angular velocity values with respect to the x, y, and z axes." * (https://msdn.microsoft.com/en-us/library/windows/apps/windows.devices.sensors.gyrometer.aspx) * * Author: Jordan Kahtava * Date: 2016-03-14 */ namespace GyroscopeTest {

///

/// A Page that can be used for navigation ///

public sealed partial class MainPage : Page { private Gyrometer gyroscope; private Inclinometer inclinometer; private uint interval; private double max_X; private double max_Y; private double max_Z; private double max_Roll; private double max_Pitch; private double max_Yaw; private Boolean startPressed = false;

public MainPage() { this.InitializeComponent(); //gather the default gyroscope sensor implementation gyroscope = Gyrometer.GetDefault(); //gather the default inclinomter sensor implementation inclinometer = Inclinometer.GetDefault(); //pick a reasonable interval that the event handlers will run at in milliseconds interval = 20; //call the resetGyroscope button method without actually clicking the button ResetGyroscope(null, null); }

///

/// Invoked when this page is about to be displayed in a Frame. ///

/// Event data that describes how this page was reached. The Parameter /// property is typically used to configure the page. protected override void OnNavigatedTo(NavigationEventArgs e) { }

private void StopGyroscope(object sender, RoutedEventArgs e) { //only attempt to turn off the Gyroscope and Inclinometer if an event handler was already attached for them //event handlers are attached when the start button is pressed if (startPressed == true) { //If the gyroscope exists on the device turn it off if (gyroscope != null) { //tell the application that the start button can be pressed again A Study of Modern Mobile Tablets - 186

startPressed = false; //This disables the gyroscope event handler so that GyroscopeChanged() is nolonger called gyroscope.ReadingChanged -= new TypedEventHandler(GyroscopeChanged); //set the reportinterval to 0 so we can release the gyroscope resources so it stops updating gyroscope.ReportInterval = 0; } //If the inclinometer exists on the device turn it off if (inclinometer != null) { //tell the application that the start button can be pressed again this is to limits the total number of event handlers attached startPressed = false; //This disables the inclinometer event handler so that InclinometerChanged() method is nolonger called inclinometer.ReadingChanged -= new TypedEventHandler(InclinometerChanged); //set the reportinterval to 0 so we can release the inclinometer resources so it stops updating inclinometer.ReportInterval = 0; }

} } private void StartGyroscope(object sender, RoutedEventArgs e) { //check to make sure the start button has not already been pressed //check to make sure the button wasnt already clicked otherwise multiple event handlers would be attached if(startPressed == false) {

if (gyroscope != null) { //set startPressed to true so the startbutton can not be clicked multiple times startPressed = true; //enables the gyroscope using the interval specified in milliseconds //events are only run if the device is moved otherwise it waits gyroscope.ReportInterval = interval; //attach a readingchanged event handler that runs the GyroscopeChanged() method which updates x y and z labels gyroscope.ReadingChanged += new TypedEventHandler(GyroscopeChanged);

} if(inclinometer != null) { //set startPressed to true so the startbutton cant be clicked multiple times //if startPressed wasnt used many event handlers would be created for each click of the start button //meaning you would have to click stop the same number of times //startPressed = true is set in both if statements incase only 1 of the 2 sensors exist startPressed = true; //enables the inclinometer using the interval specified in milliseconds //events are only run if the device is moved otherwise it waits inclinometer.ReportInterval = interval; //attach a readingchanged event handler that runs the InclinometerChanged() method which updates yaw pitch and roll labels A Study of Modern Mobile Tablets - 187

inclinometer.ReadingChanged += new TypedEventHandler(InclinometerChanged); } }

} //This method is called when the reset button is pressed private void ResetGyroscope(object sender, RoutedEventArgs e) { //set the default values of all the max calculations max_X = 0.0; max_Y = 0.0; max_Z = 0.0; max_Roll = 0.0; max_Pitch = 0.0; max_Yaw = 0.0; //update the labels so they show +0.0 for everthing SetLabelRollPitchYaw(max_X, max_Y, max_Z); SetLabelXYZ(max_X, max_Y, max_Z); CheckMaximumValueRollPitchYaw(max_Roll, max_Pitch, max_Yaw); CheckMaximumValueXYZ(max_Roll, max_Pitch, max_Yaw); }

//an asynchronous message is used so that no lag occurs between the UI button presses and retreiving Gyroscope readings async private void GyroscopeChanged(object sender, GyrometerReadingChangedEventArgs e) { //unload the gyroscope readings to another thread await Dispatcher.RunAsync(CoreDispatcherPriority.Normal, () => { //call update labelsXYZ and updatemaxXYZ with the Gyroscope velocity values SetLabelXYZ(e.Reading.AngularVelocityX, e.Reading.AngularVelocityY, e.Reading.AngularVelocityZ); CheckMaximumValueXYZ(e.Reading.AngularVelocityX, e.Reading.AngularVelocityY, e.Reading.AngularVelocityZ); }); }

//an asynchronous message is used so that no lag occurs between the UI button presses and retreiving inclinometer readings async private void InclinometerChanged(object sender, InclinometerReadingChangedEventArgs e) {

//unload the inclinometer readings to another thread await Dispatcher.RunAsync(CoreDispatcherPriority.Normal, () => { //call update labelRollPitchYar and updatemaxRollPitchYaw with the inclinometer degree values SetLabelRollPitchYaw(e.Reading.RollDegrees, e.Reading.PitchDegrees, e.Reading.YawDegrees); CheckMaximumValueRollPitchYaw(e.Reading.RollDegrees, e.Reading.PitchDegrees, e.Reading.YawDegrees); }); }

//update all the Gyroscope X: ,Y , and Z labels to show gyroscope readings or any other double value private void SetLabelXYZ(double x, double y, double z) { //0,5 indicates that numbers should be aligned to the right //+0.## indicates to show 2 decimal places and always show + sign //-0.## indicates to show 2 decimal places and always show - sign if value is negative A Study of Modern Mobile Tablets - 188

xLabel.Text = String.Format("Gyroscope X: {0,5:+0.00;-0.00}", x); yLabel.Text = String.Format("Gyroscope Y: {0,5:+0.00;-0.00}", y); zLabel.Text = String.Format("Gyroscope Z: {0,5:+0.00;-0.00}", z);

}

//update all the Inclinometer X: ,Y , and Z labels to show inclinometer readings or any other double value private void SetLabelRollPitchYaw(double roll, double pitch, double yaw) { //0,5 indicates that numbers should be aligned to the right //+0.## indicates to show 2 decimal places and always show + sign //-0.## indicates to show 2 decimal places and always show - sign if value is negative xRollLabel.Text = String.Format("Roll: {0,5:+0.00;-0.00}", roll); yPitchLabel.Text = String.Format("Pitch: {0,5:+0.00;-0.00}", pitch); zYawLabel.Text = String.Format("Yaw: {0,5:+0.00;-0.00}", yaw);

}

//determine if inclinometer current values are higher then the current maximum value private void CheckMaximumValueRollPitchYaw(double roll, double pitch, double yaw) { //Math.Abs returns the absolute value of the given double so we can check which was higher //This is required since values can be both positive and negative representing the rotation in opposite directions if (Math.Abs(max_Roll) <= Math.Abs(roll)) { max_Roll = roll; xRollMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", roll); } if (Math.Abs(max_Pitch) <= Math.Abs(pitch)) { max_Pitch = pitch; yPitchMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", pitch); } if (Math.Abs(max_Yaw) <= Math.Abs(yaw)) { max_Yaw = yaw; zYawMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", yaw); } }

//determine if gyroscope current values are higher then the current maximum value private void CheckMaximumValueXYZ(double x, double y, double z) { //Math.Abs returns the absolute value of the given double so we can check which was higher //This is required since values can be both positive and negative representing the rotation in opposite directions if (Math.Abs(max_X) <= Math.Abs(x)) { max_X = x; xMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", x); } if (Math.Abs(max_Y) <= Math.Abs(y)) { max_Y = y; yMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", y); } A Study of Modern Mobile Tablets - 189

if (Math.Abs(max_Z) <= Math.Abs(z)) { max_Z = z; zMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", z); } } } }

C.6. Increment 6: Integration, Windows 8

C.6.1. App.xaml

C.6.2. App.xaml.cs using System; using System.Collections.Generic; using System.IO; using System.Linq; using Windows.ApplicationModel; using Windows.ApplicationModel.Activation; using Windows.Foundation; using Windows.Foundation.Collections; using Windows.UI.Xaml; using Windows.UI.Xaml.Controls; using Windows.UI.Xaml.Controls.Primitives; using Windows.UI.Xaml.Data; using Windows.UI.Xaml.Input; using Windows.UI.Xaml.Media; using Windows.UI.Xaml.Navigation;

/* * This page was not modified other then a few comments were added. A Study of Modern Mobile Tablets - 190

* When creating a windows store blankApp the App.xaml, App.xaml.cs, MainPage.xaml, and MainPage.xaml.cs * are all created using a template * Author: Jordan Kahtava * Date: 2016-03-21 */ namespace WindowsSensorApplication { ///

/// Provides application-specific behavior to supplement the default Application class. ///

sealed partial class App : Application { ///

/// Initializes the singleton application object. This is the first line of authored code /// executed, and as such is the logical equivalent of main() or WinMain(). ///

public App() { this.InitializeComponent(); this.Suspending += OnSuspending; }

///

/// Invoked when the application is launched normally by the end user. Other entry points /// will be used when the application is launched to open a specific file, to display /// search results, and so forth. ///

/// Details about the launch request and process. protected override void OnLaunched(LaunchActivatedEventArgs args) { Frame rootFrame = Window.Current.Content as Frame;

// Do not repeat app initialization when the Window already has content, // just ensure that the window is active if (rootFrame == null) { // Create a Frame to act as the navigation context and navigate to the first page rootFrame = new Frame();

if (args.PreviousExecutionState == ApplicationExecutionState.Terminated) { //TODO: Load state from previously suspended application }

// Place the frame in the current Window Window.Current.Content = rootFrame; }

if (rootFrame.Content == null) { // When the navigation stack isn't restored navigate to the first page, // configuring the new page by passing required information as a navigation // parameter if (!rootFrame.Navigate(typeof(MainPage), args.Arguments)) { throw new Exception("Failed to create initial page"); } } A Study of Modern Mobile Tablets - 191

// Ensure the current window is active Window.Current.Activate(); }

///

/// Invoked when application execution is being suspended. Application state is saved /// without knowing whether the application will be terminated or resumed with the contents /// of memory still intact. ///

/// The source of the suspend request. /// Details about the suspend request. private void OnSuspending(object sender, SuspendingEventArgs e) { var deferral = e.SuspendingOperation.GetDeferral(); //TODO: Save application state and stop any background activity deferral.Complete(); } } }

C.6.3. MainPage.xaml

A Study of Modern Mobile Tablets - 192

C.6.4. MainPage.xaml.cs using System; using System.Collections.Generic; using System.IO; using System.Linq; using Windows.Foundation; using Windows.Foundation.Collections; using Windows.UI.Xaml; using Windows.UI.Xaml.Controls; using Windows.UI.Xaml.Controls.Primitives; using Windows.UI.Xaml.Data; using Windows.UI.Xaml.Input; using Windows.UI.Xaml.Media; using Windows.UI.Xaml.Navigation;

/* * This is the first page shown to the user it has two buttons * open accelerometer which opens the accelerometer page * open gyroscope which opens the gyroscope page * Author: Jordan Kahtava * Date: 2016-03-21 */ namespace WindowsSensorApplication { ///

/// An empty page that can be used on its own or navigated to within a Frame. ///

public sealed partial class MainPage : Page {

public MainPage() { this.InitializeComponent();

}

///

/// Invoked when this page is about to be displayed in a Frame. ///

/// Event data that describes how this page was reached. The Parameter /// property is typically used to configure the page. protected override void OnNavigatedTo(NavigationEventArgs e) { }

private void OpenGyroscopePage(object sender, RoutedEventArgs e) { //switch the current active frame to the gyroscopesensor page this.Frame.Navigate(typeof(GyroscopeSensor)); }

A Study of Modern Mobile Tablets - 193

private void OpenAccelerometerPage(object sender, RoutedEventArgs e) { //switch the current active frame to the accelerometersensor page this.Frame.Navigate(typeof(AccelerometerSensor));

} } }

C.6.5. Accelerometer.xaml

Accelerometer Example

A Study of Modern Mobile Tablets - 194

C.6.6. Accelerometer.xaml.cs using System; using System.Collections.Generic; using System.IO; using System.Linq; using Windows.Foundation; using Windows.Foundation.Collections; using Windows.UI.Xaml; using Windows.UI.Xaml.Controls; using Windows.UI.Xaml.Controls.Primitives; using Windows.UI.Xaml.Data; using Windows.UI.Xaml.Input; using Windows.UI.Xaml.Media; using Windows.UI.Xaml.Navigation; using Windows.Devices.Sensors; using Windows.UI.Core; using Windows.UI.Popups; /* * A very basic test that displays accelerometer data onto 3 labels * The maximum values are displayed on 3 different labels so you can determine how fast the device is moving * The maximum labels are required otherwise it would be nearly impossible to determine how fast the device was moving * It is hard to focus on the labels when the device is moving * * Accelerometer: "This sensor returns G-force values with respect to the x, y, and z axes." * (https://msdn.microsoft.com/en-us/library/windows/apps/windows.devices.sensors.accelerometer.aspx) * Author: Jordan Kahtava * Date: 2016-03-07 * Updated: 2016-03-21 * Update: Some error messages were added if a sensor is not available */ namespace WindowsSensorApplication { ///

/// A basic page that provides characteristics common to most applications. ///

public sealed partial class AccelerometerSensor : WindowsSensorApplication.Common.LayoutAwarePage {

private Accelerometer accelerometer; private uint interval; private double currentX; private double currentY; A Study of Modern Mobile Tablets - 196

private double currentZ; private Boolean startPressed = false;

public AccelerometerSensor() { this.InitializeComponent(); //retreive the current accelerometer sensor null if none exists accelerometer = Accelerometer.GetDefault(); interval = 20; //call the resetAccelerometer Button method to perform reset actions ResetAccelerometer(null, null); }

///

/// Populates the page with content passed during navigation. Any saved state is also /// provided when recreating a page from a prior session. ///

/// The parameter value passed to /// when this page was initially requested. /// /// A dictionary of state preserved by this page during an earlier /// session. This will be null the first time a page is visited. protected override void LoadState(Object navigationParameter, Dictionary pageState) { }

///

/// Preserves state associated with this page in case the application is suspended or the /// page is discarded from the navigation cache. Values must conform to the serialization /// requirements of . ///

/// An empty dictionary to be populated with serializable state. protected override void SaveState(Dictionary pageState) { }

//an asynchronous message is used so that no lag occurs between the UI and retreiving accelerometer readings async private void AccelerometerChanged(object sender, AccelerometerReadingChangedEventArgs e) { //unload the acceleration readings to another thread await Dispatcher.RunAsync(CoreDispatcherPriority.Normal, () => { //call update labels and update max with the acceleration values SetLabels(e.Reading.AccelerationX, e.Reading.AccelerationY, e.Reading.AccelerationZ); CheckMaximumValue(e.Reading.AccelerationX, e.Reading.AccelerationY, e.Reading.AccelerationZ); }); }

//update all the Accelerometer X: labels to show accleroemeter readings or any other double value private void SetLabels(double x, double y, double z) { //0,5 indicates that numbers should be aligned to the right //+0.## indicates to show 2 decimal places and always show + sign //-0.## indicates to show 2 decimal places and always show - sign if value is negative xLabel.Text = String.Format("Accelerometer X: {0,5:+0.00;-0.00}", x); yLabel.Text = String.Format("Accelerometer Y: {0,5:+0.00;-0.00}", y); A Study of Modern Mobile Tablets - 197

zLabel.Text = String.Format("Accelerometer Z: {0,5:+0.00;-0.00}", z);

} //update the maximum labels so they show the highest acceleration private void CheckMaximumValue(double x, double y, double z) { //Math.Abs returns the absolute value of the given double so we can check which was higher //This is required since values can be both positive and negative representing the movement in opposite directions if (Math.Abs(currentX) <= Math.Abs(x)) { currentX = x; xMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", x); } if (Math.Abs(currentY) <= Math.Abs(y)) { currentY = y; yMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", y); } if (Math.Abs(currentZ) <= Math.Abs(z)) { currentZ = z; zMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", z); }

}

//Stop the Accelerometer event handler when a user clicks on the Stop Accelerometer Button as specified by MainPage.xaml private void StopAccelerometer(object sender, RoutedEventArgs e) { //only attempt to turn off the accelerometer if an accelerometer event handler was already attached if (startPressed == true) { //tell the application that the start button can be pressed again startPressed = false; //This disables the accelerometers event handler so that AccelerometerChanged is nolonger called accelerometer.ReadingChanged -= new TypedEventHandler(AccelerometerChanged); //set the reportinterval to 0 so we can release resources accelerometer.ReportInterval = 0; }

}

//Start the accelerometer when a user clicks on the Start Accelerometer Button as specified by MainPage.xaml private void StartAccelerometer(object sender, RoutedEventArgs e) { //check to make sure an accelerometer exists null indicates no sensor detected. //check to make sure the button wasnt already clicked otherwise multiple accelerometer event handlers will be attached if (accelerometer != null && startPressed == false) { //tell the application that start was pressed startPressed = true; A Study of Modern Mobile Tablets - 198

//enables the accelerometer using the interval specified in milliseconds //events are only run if the device is moved otherwise it waits accelerometer.ReportInterval = interval; //attach a readingchanged event handler that runs the AccelerometerChanged() method accelerometer.ReadingChanged += new TypedEventHandler(AccelerometerChanged);

} else if (accelerometer == null) { //if the accelerometer is null then no sensor was found display a message messageBox("No Accelerometer Found!", "Accelerometer Error"); } else { //if the accelerometer is not null then the sensor must already be started display a message messageBox("Accelerometer Already Started!", "Accelerometer Notification"); }

} //Reset all the labels when a user clicks on the Reset Accelerometer Button as specified by MainPage.xaml private void ResetAccelerometer(object sender, RoutedEventArgs e) { //reset the current max values to 0 currentX = 0.0; currentY = 0.0; currentZ = 0.0; //update the max values CheckMaximumValue(currentX, currentY, currentZ); //update the accelerometer labels SetLabels(currentX, currentY, currentZ); }

async private void messageBox(string message, string title) { //create a message dialog using the message and title provided MessageDialog messageDialog = new MessageDialog(message, title); //Create a button for the dialog called Close that doesnt run any command //null can be replaced with an event handler to perform an action if desired. messageDialog.Commands.Add(new UICommand("Close",null)); // Show the message dialog asynchronously await messageDialog.ShowAsync(); } } }

C.6.7. Gyroscope.xaml

xmlns:d="http://schemas.microsoft.com/expression/blend/2008" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" mc:Ignorable="d">

Gyroscope Example

A Study of Modern Mobile Tablets - 200

A Study of Modern Mobile Tablets - 201

C.6.8. Gyroscope.xaml.cs using System; using System.Collections.Generic; using System.IO; using System.Linq; using Windows.Foundation; using Windows.Foundation.Collections; using Windows.UI.Xaml; using Windows.UI.Xaml.Controls; using Windows.UI.Xaml.Controls.Primitives; using Windows.UI.Xaml.Data; using Windows.UI.Xaml.Input; using Windows.UI.Xaml.Media; using Windows.UI.Xaml.Navigation; using Windows.Devices.Sensors; using Windows.UI.Core; using Windows.UI.Popups;

/* A very basic test that outputs gyroscope data and inclinometer data to 6 different labels * The maximum values are also updated on 6 other labels * Inclinometer: "This sensor returns pitch, roll, and yaw values that correspond to rotation angles around the x, y, and z axes, respectively." * (https://msdn.microsoft.com/en-us/library/windows/apps/windows.devices.sensors.inclinometer.aspx) * * Gyroscope: "This sensor returns angular velocity values with respect to the x, y, and z axes." * (https://msdn.microsoft.com/en-us/library/windows/apps/windows.devices.sensors.gyrometer.aspx) * * Author: Jordan Kahtava * Date: 2016-03-14 * Updated: 2016-03-21 * Update: Some error messages were added if a sensor is not available */ namespace WindowsSensorApplication { ///

/// A basic page that provides characteristics common to most applications. ///

public sealed partial class GyroscopeSensor : WindowsSensorApplication.Common.LayoutAwarePage { private Gyrometer gyroscope; private Inclinometer inclinometer; private uint interval; private double max_X; private double max_Y; private double max_Z; private double max_Roll; private double max_Pitch; private double max_Yaw; private Boolean startPressed = false;

public GyroscopeSensor() { this.InitializeComponent(); A Study of Modern Mobile Tablets - 202

//gather the default gyroscope sensor implementation gyroscope = Gyrometer.GetDefault(); //gather the default inclinomter sensor implementation inclinometer = Inclinometer.GetDefault(); //pick a reasonable interval that the event handlers will run at in milliseconds interval = 20; //call the resetGyroscope button method without actually clicking the button ResetGyroscope(null, null); }

///

/// Populates the page with content passed during navigation. Any saved state is also /// provided when recreating a page from a prior session. ///

/// The parameter value passed to /// when this page was initially requested. /// /// A dictionary of state preserved by this page during an earlier /// session. This will be null the first time a page is visited. protected override void LoadState(Object navigationParameter, Dictionary pageState) { }

///

/// Preserves state associated with this page in case the application is suspended or the /// page is discarded from the navigation cache. Values must conform to the serialization /// requirements of . ///

/// An empty dictionary to be populated with serializable state. protected override void SaveState(Dictionary pageState) { }

private void StopGyroscope(object sender, RoutedEventArgs e) { //only attempt to turn off the Gyroscope and Inclinometer if an event handler was already attached for them //event handlers are attached when the start button is pressed if (startPressed == true) { //If the gyroscope exists on the device turn it off if (gyroscope != null) { //tell the application that the start button can be pressed again startPressed = false; //This disables the gyroscope event handler so that GyroscopeChanged() is nolonger called gyroscope.ReadingChanged -= new TypedEventHandler(GyroscopeChanged); //set the reportinterval to 0 so we can release the gyroscope resources so it stops updating gyroscope.ReportInterval = 0; } //If the inclinometer exists on the device turn it off if (inclinometer != null) { //tell the application that the start button can be pressed again this is to limits the total number of event handlers attached startPressed = false; //This disables the inclinometer event handler so that InclinometerChanged() method is A Study of Modern Mobile Tablets - 203

nolonger called inclinometer.ReadingChanged -= new TypedEventHandler(InclinometerChanged); //set the reportinterval to 0 so we can release the inclinometer resources so it stops updating inclinometer.ReportInterval = 0; }

} } private void StartGyroscope(object sender, RoutedEventArgs e) { //check to make sure the start button has not already been pressed //check to make sure the button wasnt already clicked otherwise multiple event handlers would be attached if (startPressed == false) { if (gyroscope != null) { //set startPressed to true so the startbutton can not be clicked multiple times startPressed = true; //enables the gyroscope using the interval specified in milliseconds //events are only run if the device is moved otherwise it waits gyroscope.ReportInterval = interval; //attach a readingchanged event handler that runs the GyroscopeChanged() method which updates x y and z labels gyroscope.ReadingChanged += new TypedEventHandler(GyroscopeChanged);

} if (inclinometer != null) { //set startPressed to true so the startbutton cant be clicked multiple times //if startPressed wasnt used many event handlers would be created for each click of the start button //meaning you would have to click stop the same number of times //startPressed = true is set in both if statements incase only 1 of the 2 sensors exist startPressed = true; //enables the inclinometer using the interval specified in milliseconds //events are only run if the device is moved otherwise it waits inclinometer.ReportInterval = interval; //attach a readingchanged event handler that runs the InclinometerChanged() method which updates yaw pitch and roll labels inclinometer.ReadingChanged += new TypedEventHandler(InclinometerChanged); } //Display a message if both sensors are missing if (inclinometer == null && gyroscope == null) { messageBox("No Inclinometer or Gyroscope Found!", "Gyroscope and Inclinometer Error"); } //Display a message if only the inclinometer is missing else if (inclinometer == null) { messageBox("No Inclinometer Found!", "Inclinometer Error"); } //Display a message if only the Gyroscope is missing else if (gyroscope == null) A Study of Modern Mobile Tablets - 204

{ messageBox("No Gyroscope Found!", "Gyroscope Error"); } } //Display a message if the start button was already pressed previously else { messageBox("Sensors Already Started!", "Sensor Notification"); }

} //This method is called when the reset button is pressed private void ResetGyroscope(object sender, RoutedEventArgs e) { //set the default values of all the max calculations max_X = 0.0; max_Y = 0.0; max_Z = 0.0; max_Roll = 0.0; max_Pitch = 0.0; max_Yaw = 0.0; //update the labels so they show +0.0 for everthing SetLabelRollPitchYaw(max_X, max_Y, max_Z); SetLabelXYZ(max_X, max_Y, max_Z); CheckMaximumValueRollPitchYaw(max_Roll, max_Pitch, max_Yaw); CheckMaximumValueXYZ(max_Roll, max_Pitch, max_Yaw); }

//an asynchronous message is used so that no lag occurs between the UI button presses and retreiving Gyroscope readings async private void GyroscopeChanged(object sender, GyrometerReadingChangedEventArgs e) { //unload the gyroscope readings to another thread await Dispatcher.RunAsync(CoreDispatcherPriority.Normal, () => { //call update labelsXYZ and updatemaxXYZ with the Gyroscope velocity values SetLabelXYZ(e.Reading.AngularVelocityX, e.Reading.AngularVelocityY, e.Reading.AngularVelocityZ); CheckMaximumValueXYZ(e.Reading.AngularVelocityX, e.Reading.AngularVelocityY, e.Reading.AngularVelocityZ); }); }

//an asynchronous message is used so that no lag occurs between the UI button presses and retreiving inclinometer readings async private void InclinometerChanged(object sender, InclinometerReadingChangedEventArgs e) {

//unload the inclinometer readings to another thread await Dispatcher.RunAsync(CoreDispatcherPriority.Normal, () => { //call update labelRollPitchYar and updatemaxRollPitchYaw with the inclinometer degree values SetLabelRollPitchYaw(e.Reading.RollDegrees, e.Reading.PitchDegrees, e.Reading.YawDegrees); CheckMaximumValueRollPitchYaw(e.Reading.RollDegrees, e.Reading.PitchDegrees, e.Reading.YawDegrees); }); }

//update all the Gyroscope X: ,Y , and Z labels to show gyroscope readings or any other double value A Study of Modern Mobile Tablets - 205

private void SetLabelXYZ(double x, double y, double z) { //0,5 indicates that numbers should be aligned to the right //+0.## indicates to show 2 decimal places and always show + sign //-0.## indicates to show 2 decimal places and always show - sign if value is negative xLabel.Text = String.Format("Gyroscope X: {0,5:+0.00;-0.00}", x); yLabel.Text = String.Format("Gyroscope Y: {0,5:+0.00;-0.00}", y); zLabel.Text = String.Format("Gyroscope Z: {0,5:+0.00;-0.00}", z);

}

//update all the Inclinometer X: ,Y , and Z labels to show inclinometer readings or any other double value private void SetLabelRollPitchYaw(double x, double y, double z) { //0,5 indicates that numbers should be aligned to the right //+0.## indicates to show 2 decimal places and always show + sign //-0.## indicates to show 2 decimal places and always show - sign if value is negative xRollLabel.Text = String.Format("Roll: {0,5:+0.00;-0.00}", x); yPitchLabel.Text = String.Format("Pitch: {0,5:+0.00;-0.00}", y); zYawLabel.Text = String.Format("Yaw: {0,5:+0.00;-0.00}", z);

}

//determine if inclinometer current values are higher then the current maximum value private void CheckMaximumValueRollPitchYaw(double x, double y, double z) { //Math.Abs returns the absolute value of the given double so we can check which was higher //This is required since values can be both positive and negative representing the rotation in opposite directions if (Math.Abs(max_Roll) <= Math.Abs(x)) { max_Roll = x; xRollMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", x); } if (Math.Abs(max_Pitch) <= Math.Abs(y)) { max_Pitch = y; yPitchMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", y); } if (Math.Abs(max_Yaw) <= Math.Abs(z)) { max_Yaw = z; zYawMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", z); } }

//determine if gyroscope current values are higher then the current maximum value private void CheckMaximumValueXYZ(double x, double y, double z) { //Math.Abs returns the absolute value of the given double so we can check which was higher //This is required since values can be both positive and negative representing the rotation in opposite directions if (Math.Abs(max_X) <= Math.Abs(x)) { max_X = x; xMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", x); } A Study of Modern Mobile Tablets - 206

if (Math.Abs(max_Y) <= Math.Abs(y)) { max_Y = y; yMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", y); } if (Math.Abs(max_Z) <= Math.Abs(z)) { max_Z = z; zMaxLabel.Text = String.Format("Max: {0,5:+0.00;-0.00}", z); }

}

async private void messageBox(string message, string title) { //create a message dialog using the message and title provided MessageDialog messageDialog = new MessageDialog(message, title); //Create a button for the dialog called Close that doesnt run any command //null can be replaced with an event handler to perform an action if desired. messageDialog.Commands.Add(new UICommand("Close", null)); // Show the message dialog asynchronously await messageDialog.ShowAsync();

} } }

A Study of Modern Mobile Tablets - 207

Glossary

SOC – System on a Chip

MP - Megapixel

MB - Megabyte

GB - Gigabyte

RAM - Random Access Memory

DRAM - Dynamic Random Access Memory

DDR2 - Double data rate version 2

DDR3 - Double data rate version 3

GPS - Global Positioning System

A Study of Modern Mobile Tablets - 208

References

[1] Support.apple.com, "iPad - Technical Specifications", 2013. [Online]. Available:

https://support.apple.com/kb/SP580?viewlocale=en_US&locale=en_US. [Accessed: 28-

Jan- 2016].

[2] Support.apple.com, "iPad 2 - Technical Specifications", 2013. [Online]. Available:

https://support.apple.com/kb/SP622?viewlocale=en_US&locale=en_US. [Accessed: 28-

Jan- 2016].

[3] Support.apple.com, "iPad (3rd generation) - Technical Specifications", 2013. [Online].

Available: https://support.apple.com/kb/SP647?viewlocale=en_US&locale=en_US.

[Accessed: 28- Jan- 2016].

[4] Support.apple.com, "iPad (4th generation) - Technical Specifications", 2013. [Online].

Available: https://support.apple.com/kb/SP662?viewlocale=en_US&locale=en_US.

[Accessed: 28- Jan- 2016].

[5] "Apple - Press Info - iPad Available in US on April 3", Apple.com, 2010. [Online].

Available: http://www.apple.com/pr/library/2010/03/05iPad-Available-in-US-on-April-

3.html. [Accessed: 17- Mar- 2016].

[6] "Apple - Press Info - iPad 2 Arrives Tomorrow", Apple.com, 2011. [Online]. Available:

http://www.apple.com/pr/library/2011/03/10iPad-2-Arrives-Tomorrow.html. [Accessed:

17- Mar- 2016]. A Study of Modern Mobile Tablets - 209

[7] "Apple - Press Info - Apple Launches New iPad", Apple.com, 2012. [Online]. Available:

http://www.apple.com/pr/library/2012/03/07Apple-Launches-New-iPad.html. [Accessed:

17- Mar- 2016].

[8] "Apple - Press Info - Apple Introduces iPad mini", Apple.com, 2012. [Online]. Available:

http://www.apple.com/pr/library/2012/10/23Apple-Introduces-iPad-mini.html.

[Accessed: 17- Mar- 2016].

[9] M. deAgonia, "Still got a first-gen iPad? Don't ditch it yet", Computerworld, 2016.

[Online]. Available: http://www.computerworld.com/article/2485945/tablets/tablets-still-

got-a-first-gen-ipad-don-t-ditch-it-yet.html. [Accessed: 16- Feb- 2016].

[10] Support.apple.com, "Download iOS 9.0 - 9.2.1 Information", 2016. [Online]. Available:

https://support.apple.com/kb/DL1842?locale=en_US. [Accessed: 16- Feb- 2016].

[11] iFixit, "Apple A4 Teardown", 2010. [Online]. Available:

https://www.ifixit.com/Teardown/Apple+A4+Teardown/2204. [Accessed: 28- Jan-

2016].

[12] Arm.com, "Cortex-A8 Processor - ARM", 2016. [Online]. Available:

http://www.arm.com/products/processors/cortex-a/cortex-a8.php. [Accessed: 16- Feb-

2016].

[13] “The Teardown: Apple iPad 2.,” Engineering & Technology, vol. 6, no. 5, pp. 94–95,

Jun. 2011.

[14] Arm.com, "Cortex-A9 Processor - ARM", 2016. [Online]. Available:

http://www.arm.com/cortex-a9.php. [Accessed: 16- Feb- 2016]. A Study of Modern Mobile Tablets - 210

[15] A. Shimpi and V. Gowri, "The Apple iPad Review (2012)", Anandtech.com, 2016.

[Online]. Available: http://www.anandtech.com/show/5688/apple-ipad-2012-review/11.

[Accessed: 16- Feb- 2016].

[16] A. Shimpi, "Apple's Cyclone Microarchitecture Detailed", Anandtech.com, 2016.

[Online]. Available: http://www.anandtech.com/show/7910/apples-cyclone-

microarchitecture-detailed. [Accessed: 16- Feb- 2016].

[17] A. Shimpi and V. Gowri, "The Apple iPad Review (2012)", Anandtech.com, 2016.

[Online]. Available: http://www.anandtech.com/show/5688/apple-ipad-2012-review/12.

[Accessed: 16- Feb- 2016].

[18] A. Shimpi, "iPad 4 GPU Performance Analyzed: PowerVR SGX 554MP4 Under the

Hood", Anandtech.com, 2016. [Online]. Available:

http://www.anandtech.com/show/6426/ipad-4-gpu-performance-analyzed-powervr-sgx-

554mp4-under-the-hood. [Accessed: 16- Feb- 2016].

[19] iFixit, "iPad Wi-Fi Teardown", 2010. [Online]. Available:

https://www.ifixit.com/Teardown/iPad+Wi-Fi+Teardown/2183. [Accessed: 28- Jan-

2016].

[20] iFixit, "iPad 3 4G Teardown", 2012. [Online]. Available:

https://www.ifixit.com/Teardown/iPad+3+4G+Teardown/8277. [Accessed: 28- Jan-

2016]. A Study of Modern Mobile Tablets - 211

[21] A. Shimpi, "Apple's A5X Die (and Size?) Revealed", Anandtech.com, 2016. [Online].

Available: http://www.anandtech.com/show/5681/apples-a5x-die-and-size-revealed.

[Accessed: 16- Feb- 2016].

[22] J. Ho and R. Smith, "The iPad Pro Preview: Taking Notes With iPad Pro",

Anandtech.com, 2016. [Online]. Available:

http://www.anandtech.com/show/9780/taking-notes-with-ipad-pro/2. [Accessed: 16- Feb-

2016].

[23] K. Dems, "What is a VGA Camera? Understanding Video Graphics Array", Bright Hub,

2016. [Online]. Available: http://www.brighthub.com/electronics/cameras-

camcorders/articles/67210.aspx. [Accessed: 16- Feb- 2016].

[24] J. Nguyen, "The New iPad 3 and iPad 2 Side by Side Comparison - ITJungles",

Itjungles.com, 2016. [Online]. Available: http://www.itjungles.com/the-new-ipad-3-and-

ipad-2-side-by-side-comparison.html. [Accessed: 16- Feb- 2016].

[25] iFixit, "iPad 2 Wi-Fi EMC 2415 Teardown", 2011. [Online]. Available:

https://www.ifixit.com/Teardown/iPad+2+Wi-Fi+EMC+2415+Teardown/5071.

[Accessed: 28- Jan- 2016].

[26] iFixit, "iPad 4 Wi-Fi Teardown", 2012. [Online]. Available:

https://www.ifixit.com/Teardown/iPad+4+Wi-Fi+Teardown/11462. [Accessed: 28- Jan-

2016].

A Study of Modern Mobile Tablets - 212

[27] "iOS 5 is compatible with:", News.softpedia.com, 2011. [Online]. Available: http://news.softpedia.com/images/extra/MAC2/large/ios5compatibledevicesscr_001-large.jpg.

[Accessed: 13- Apr- 2016].

[28]"iOS 9 is compatible with these devices.", Cdn2.macworld.co.uk. [Online]. Available: http://cdn2.macworld.co.uk/cmsdata/reviews/3613323/iOS_9_compatible_devices_iPhone_iPad

_iPod_touch_1000.jpg. [Accessed: 10- Apr- 2016].

[29] B. Jones, "Apple Retina Display – Jonesblog", Prometheus.med.utah.edu, 2016. [Online].

Available: http://prometheus.med.utah.edu/~bwjones/2010/06/apple-retina-display/.

[Accessed: 02- Mar- 2016].

[30] S. Anthony, "SoC vs. CPU – The battle for the future of computing | ExtremeTech",

ExtremeTech, 2012. [Online]. Available:

http://www.extremetech.com/computing/126235-soc-vs-cpu-the-battle-for-the-future-of-

computing. [Accessed: 13- Feb- 2016].

[31] A. Shimpi, "NVIDIA's Tegra 3 Launched: Architecture Revealed", Anandtech.com,

2016. [Online]. Available: http://www.anandtech.com/show/5072/nvidias-tegra-3-

launched-architecture-revealed. [Accessed: 18- Feb- 2016].

[32] "What is GPU Computing? | High-Performance Computing | NVIDIA | NVIDIA",

Nvidia.ca. [Online]. Available: http://www.nvidia.ca/object/what-is-gpu-computing.html.

[Accessed: 12- Apr- 2016].

[33] Imagination Technologies, "Imagination Technologies Group plc - Interim Management

Statement", 2016. [Online]. Available: https://imgtec.com/news/press- A Study of Modern Mobile Tablets - 213

release/imagination-technologies-group-plc-interim-management-statement-7/.

[Accessed: 02- Mar- 2016].

[34] Support.apple.com, "iPad Air - Technical Specifications", 2016. [Online]. Available:

https://support.apple.com/kb/SP692?viewlocale=en_US&locale=en_US. [Accessed: 16-

Feb- 2016].

[35] Support.apple.com, "iPad Air 2 - Technical Specification", 2016. [Online]. Available:

https://support.apple.com/kb/SP708?viewlocale=en_US&locale=en_US. [Accessed: 16-

Feb- 2016].

[36] "Apple - Press Info - Apple Announces iPad Air—Dramatically Thinner, Lighter & More

Powerful iPad", Apple.com, 2013. [Online]. Available:

http://www.apple.com/pr/library/2013/10/23Apple-Announces-iPad-Air-Dramatically-

Thinner-Lighter-More-Powerful-iPad.html. [Accessed: 17- Mar- 2016].

[37] "Apple - Press Info - Apple Introduces iPad Air 2—The Thinnest, Most Powerful iPad

Ever", Apple.com, 2014. [Online]. Available:

http://www.apple.com/pr/library/2014/10/16Apple-Introduces-iPad-Air-2-The-Thinnest-

Most-Powerful-iPad-Ever.html. [Accessed: 17- Mar- 2016].

[38] R. Smith, "Chipworks Disassembles Apple's A8 SoC: GX6450, 4MB L3 Cache & More",

Anandtech.com, 2016. [Online]. Available:

http://www.anandtech.com/show/8562/chipworks-a8. [Accessed: 16- Feb- 2016]. A Study of Modern Mobile Tablets - 214

[39] A. Shimpi, "The iPad Air Review", Anandtech.com, 2016. [Online]. Available:

http://www.anandtech.com/show/7460/apple-ipad-air-review/4. [Accessed: 16- Feb-

2016].

[40] iFixit, "iPad Air LTE Teardown", 2016. [Online]. Available:

https://www.ifixit.com/Teardown/iPad+Air+LTE+Teardown/18907. [Accessed: 16- Feb-

2016].

[41] iFixit, "iPad Air 2 Teardown", 2016. [Online]. Available:

https://www.ifixit.com/Teardown/iPad+Air+2+Teardown/30592. [Accessed: 16- Feb-

2016].

[42] H. Lipfert, "MIMO OFDM - Space Time Coding – Spatial Multiplexing, Increasing

Performance and Spectral Efficiency in Wireless Systems, Part I Technical Basis",

Institut für Rundfunktechnik, 2007. [Online]. Available:

http://www.irt.de/webarchiv/showdoc.php?z=OTAyIzEwMDYwMTMxMCNwZGY=.

[Accessed: 02- Mar- 2016].

[43] Support.apple.com, "iOS: Understanding iBeacon - Apple Support", 2015. [Online].

Available: https://support.apple.com/en-gb/HT202880. [Accessed: 02- Mar- 2016].

[44] developer.apple.com, "Getting Started with iBeacon", 2014. [Online]. Available:

https://developer.apple.com/ibeacon/Getting-Started-with-iBeacon.pdf. [Accessed: 02-

Mar- 2016].

[45] Apple, "iPad Air 2 - Performance - Apple". [Online]. Available:

http://www.apple.com/ipad- air-2/performance/. [Accessed: 02- Mar- 2016]. A Study of Modern Mobile Tablets - 215

[46] A. Shimpi, "Imagination's PowerVR GX6650: Competition for Mobile Kepler",

Anandtech.com, 2014. [Online]. Available:

http://www.anandtech.com/show/7796/imagination-technologies-announces-new-high-

end-mobile-gpu-powervr-gx6650. [Accessed: 02- Mar- 2016].

[47] R. Smith, "Apple A8X’s GPU - GXA6850, Even Better Than I Thought",

Anandtech.com, 2014. [Online]. Available: http://www.anandtech.com/show/8716/apple-

a8xs-gpu-gxa6850-even-better-than-i-thought. [Accessed: 02- Mar- 2016].

[48] Support.apple.com, "iPad mini - Technical Specifications", 2016. [Online]. Available:

https://support.apple.com/kb/SP661?viewlocale=en_US&locale=en_US. [Accessed: 16-

Feb- 2016].

[49] Support.apple.com, "iPad mini 2 with Retina display - Technical Specifications", 2016.

[Online]. Available:

https://support.apple.com/kb/SP693?viewlocale=en_US&locale=en_US. [Accessed: 16-

Feb- 2016].

[50] Support.apple.com, "iPad mini 3 - Technical Specification", 2016. [Online]. Available:

https://support.apple.com/kb/SP709?viewlocale=en_US&locale=en_US. [Accessed: 16-

Feb- 2016].

[51] Support.apple.com, "iPad mini 4 - Technical Specifications", 2016. [Online]. Available:

https://support.apple.com/kb/SP725?viewlocale=en_US&locale=en_US. [Accessed: 16-

Feb- 2016]. A Study of Modern Mobile Tablets - 216

[52] "Apple Special Event. September 9, 2015", Apple, 2015. [Online]. Available:

http://www.apple.com/ca/apple-events/september-2015/. [Accessed: 16- Feb- 2016].

[53] iFixit, "iPad Mini Wi-Fi Teardown", 2016. [Online]. Available:

https://www.ifixit.com/Teardown/iPad+Mini+Wi-Fi+Teardown/11423. [Accessed: 16-

Feb- 2016].

[54] iFixit, "iPad Mini 2 Teardown", 2016. [Online]. Available:

https://www.ifixit.com/Teardown/iPad+Mini+2+Teardown/19374. [Accessed: 16- Feb-

2016].

[55] iFixit, "iPad Mini 3 Wi-Fi Teardown", 2016. [Online]. Available:

https://www.ifixit.com/Teardown/iPad+Mini+3+Wi-Fi+Teardown/30628. [Accessed: 16-

Feb- 2016].

[56] iFixit, "iPad Mini 4 Teardown", 2016. [Online]. Available:

https://www.ifixit.com/Teardown/iPad+Mini+4+Teardown/48891. [Accessed: 16- Feb-

2016].

[57] iFixit, "iPad Mini 3 Wi-Fi Battery Replacement", 2016. [Online]. Available:

https://www.ifixit.com/Guide/iPad+Mini+3+Wi-Fi+Battery+Replacement/35627.

[Accessed: 16- Feb- 2016].

[58] I-cdn.phonearena.com. [Online]. Available: http://i-

cdn.phonearena.com/images/articles/208241-image/Apple-iOS-9-iPhone-iPad-

compatibility.png. [Accessed: 13- Apr- 2016]. A Study of Modern Mobile Tablets - 217

[59] Support.apple.com, "Use Touch ID on iPhone and iPad - Apple Support", 2016. [Online].

Available: https://support.apple.com/en-ca/HT201371. [Accessed: 03- Mar- 2016].

[60] Support.apple.com, "About Touch ID security on iPhone and iPad - Apple Support",

2015. [Online]. Available: https://support.apple.com/en-ca/HT204587. [Accessed: 03-

Mar- 2016].

[61] Support.apple.com, "iPad Pro - Technical Specifications", 2016. [Online]. Available:

https://support.apple.com/kb/SP723?viewlocale=en_US&locale=en_US. [Accessed: 16-

Feb- 2016].

[62] "Apple - Press Info - Apple Introduces iPad Pro Featuring Epic 12.9-inch Retina

Display", Apple.com, 2015. [Online]. Available:

http://www.apple.com/pr/library/2015/09/09Apple-Introduces-iPad-Pro-Featuring-Epic-

12-9-inch-Retina-Display.html. [Accessed: 17- Mar- 2016].

[63] R. Smith and J. Ho, "The Apple iPhone 6s and iPhone 6s Plus Review", Anandtech.com,

2016. [Online]. Available: http://www.anandtech.com/show/9686/the-apple-iphone-6s-

and-iphone-6s-plus-review/4. [Accessed: 16- Feb- 2016].

[64] R. Smith, "More on Apple’s A9X SoC: 147mm2@TSMC, 12 GPU Cores, No L3

Cache", Anandtech.com, 2016. [Online]. Available:

http://www.anandtech.com/show/9824/more-on-apples-a9x-soc. [Accessed: 16- Feb-

2016]. A Study of Modern Mobile Tablets - 218

[65] iFixit, "iPad Pro Teardown", 2016. [Online]. Available:

https://www.ifixit.com/Teardown/iPad+Pro+Teardown/52599. [Accessed: 16- Feb-

2016].

[66] G. Mah, “The iPad Pro vs. the Surface Pro 3: we check Apple’s lofty performance

claims,” PC World, pp. 111 – 117, Nov-2015.

[67] Microsoft, "Surface RT", 2016. [Online]. Available:

https://www.microsoft.com/surface/en-us/devices/surface. [Accessed: 18- Feb- 2016].

[68] Microsoft Surface, "Surface 2", 2016. [Online]. Available:

https://www.microsoft.com/surface/en-us/devices/surface-2. [Accessed: 18- Feb- 2016].

[69] Microsoft Surface, "Surface 3", 2016. [Online]. Available:

https://www.microsoft.com/surface/en-ca/devices/surface-3. [Accessed: 18- Feb- 2016].

[70] "Microsoft Announces New Surface Details", news.microsoft.com, 2012. [Online].

Available: http://news.microsoft.com/2012/10/16/microsoft-announces-new-surface-

details/. [Accessed: 20- Mar- 2016].

[71] "Surface 2 and Surface Pro 2 are now available!", Microsoft Devices Blog, 2013.

[Online]. Available: https://blogs.windows.com/devices/2013/10/21/surface-2-and-

surface-pro-2-are- now-available/. [Accessed: 20- Mar- 2016].

[72] "Microsoft introduces Surface 3: The thinnest and lightest Surface yet",

news.microsoft.com, 2015. [Online]. Available:

https://news.microsoft.com/2015/03/31/microsoft-introduces-surface-3-the- thinnest-and-

lightest-surface-yet/. [Accessed: 20- Mar- 2016]. A Study of Modern Mobile Tablets - 219

[73] "Supported Operating Systems for Surface Pro 4, Surface Pro3, Surface Pro 2, Surface

Pro, Surface 3, and Surface Book", Support.microsoft.com. [Online]. Available:

https://support.microsoft.com/en-ca/kb/2858199. [Accessed: 18- Feb- 2016].

[74] B. Howse, "The Surface 3 Review", Anandtech.com, 2016. [Online]. Available:

http://www.anandtech.com/show/9219/the-surface-3-review. [Accessed: 18- Feb- 2016].

[75] A. Shimpi, "The Tegra 4 GPU, NVIDIA Claims Better Performance Than iPad 4",

Anandtech.com, 2016. [Online]. Available: http://www.anandtech.com/show/6666/the-

tegra-4-gpu-nvidia-claims-better-performance-than-ipad-4. [Accessed: 18- Feb- 2016].

[76] Arm.com, "Cortex-A15 Processor - ARM", 2016. [Online]. Available:

http://www.arm.com/products/processors/cortex-a/cortex-a15.php. [Accessed: 18- Feb-

2016].

[77] B. Howse, "The Surface 3 Review", Anandtech.com, 2016. [Online]. Available:

http://www.anandtech.com/show/9219/the-surface-3-review/6. [Accessed: 18- Feb-

2016].

[78] iFixit, "Microsoft Surface Teardown", 2016. [Online]. Available:

https://www.ifixit.com/Teardown/Microsoft+Surface+Teardown/11275. [Accessed: 18-

Feb- 2016].

[79] B. Detwiler, "Surface 2 design changes make it more difficult to crack open and repair -

TechRepublic", TechRepublic, 2013. [Online]. Available:

http://www.techrepublic.com/blog/cracking-open/surface-2-design-changes-make-it-

more-difficult-to-crack-open-and-repair/. [Accessed: 18- Feb- 2016]. A Study of Modern Mobile Tablets - 220

[80] Microsoft.com, "Microsoft Surface RT features", 2016. [Online]. Available:

https://www.microsoft.com/surface/en-ca/support/getting-started/surface-rt-

features?os=windows-8.1-rt-update-3. [Accessed: 18- Feb- 2016].

[81] Microsoft.com, "Microsoft Surface 2 features", 2016. [Online]. Available:

https://www.microsoft.com/surface/en-ca/support/getting-started/surface-2-

features?os=windows-8.1-rt-update-3. [Accessed: 18- Feb- 2016].

[82] Microsoft.com, "Microsoft Surface 3 features | Surface 3 overview", 2016. [Online].

Available: https://www.microsoft.com/surface/en-ca/support/getting-started/surface-3-

features?os=windows-10. [Accessed: 18- Feb- 2016].

[83] iFixit, "Microsoft Surface 3 Battery Replacement", 2016. [Online]. Available:

https://www.ifixit.com/Guide/Microsoft+Surface+3+Battery+Replacement/52684.

[Accessed: 18- Feb- 2016].

[84] Microsoft.com, "Microsoft Typography - What is ClearType?", 2016. [Online].

Available: https://www.microsoft.com/typography/whatiscleartype.mspx. [Accessed: 03-

Mar- 2016].

[85] "Tegra 2 Processors", Nvidia.ca, 2016. [Online]. Available:

http://www.nvidia.ca/object/tegra-superchip.html. [Accessed: 09- Mar- 2016].

[86] "Tegra 3 Multi-Core Processor", Nvidia.ca, 2016. [Online]. Available:

http://www.nvidia.ca/object/tegra-3-processor.html. [Accessed: 09- Mar- 2016].

[87] "Intel® Atom™ x7-Z8700 Processor (2M Cache, up to 2.40 GHz) Specifications", Intel®

ARK (Product Specs), 2015. [Online]. Available: A Study of Modern Mobile Tablets - 221

http://ark.intel.com/products/85475/Intel-Atom-x7-Z8700-Processor-2M-Cache-up-to-

2_40-GHz. [Accessed: 09- Mar- 2016].

[88] Intel Atom Z8000 Processor Series Datasheet (Volume 1 of 2), 2nd ed. Intel, 2016, p. 17.

[89] Microsoft.com, "Microsoft Surface Pro specifications", 2016. [Online]. Available:

https://www.microsoft.com/surface/en-au/support/surface-pro-specs. [Accessed: 18- Feb-

2016].

[90] Microsoft.com, "Microsoft Surface Pro 2 specifications", 2016. [Online]. Available:

https://www.microsoft.com/surface/en-au/support/surface-pro-2-specs. [Accessed: 18-

Feb- 2016].

[91] Microsoft.com, "Microsoft Surface Pro 3 specifications", 2016. [Online]. Available:

https://www.microsoft.com/surface/en-au/support/surface-pro-3-specs. [Accessed: 18-

Feb- 2016].

[92] Microsoft.com, "Microsoft Surface Pro 4", 2016. [Online]. Available:

https://www.microsoft.com/surface/en-ca/devices/surface-pro-4. [Accessed: 18- Feb-

2016].

[93] "Microsoft Grows Surface Family", news.microsoft.com, 2013. [Online]. Available:

http://news.microsoft.com/2013/01/22/microsoft-grows-surface-family/. [Accessed: 20-

Mar- 2016].

[94] "Microsoft introduces Surface Pro 3: the tablet that can replace your laptop",

news.microsoft.com, 2014. [Online]. Available: A Study of Modern Mobile Tablets - 222

http://news.microsoft.com/2014/05/20/microsoft-introduces-surface-pro-3-the-tablet-that-

can-replace-your-laptop/. [Accessed: 20- Mar- 2016].

[95] "Microsoft redefines the laptop with Surface Book, ushers in new era of Windows 10

devices", news.microsoft.com, 2015. [Online]. Available:

http://news.microsoft.com/2015/10/06/microsoft-redefines-the-laptop-with- surface-

book-ushers-in-new-era-of-windows-10-devices/. [Accessed: 20- Mar- 2016].

[96] A. Shimpi, "Microsoft Surface Pro 3 Review", Anandtech.com, 2016. [Online].

Available: http://www.anandtech.com/show/8077/microsoft-surface-pro-3-review.

[Accessed: 18- Feb- 2016].

[97] "Intel® Core™ i5-3317U Processor Specifications", Intel® ARK (Product Specs), 2016.

[Online]. Available: http://ark.intel.com/products/65707/Intel-Core-i5-3317U-Processor-

3M-Cache-up-to-2_60-GHz. [Accessed: 09- Mar- 2016].

[98] "Intel® Core™ i5-4200U Processor Specifications", Intel® ARK (Product Specs), 2016.

[Online]. Available: http://ark.intel.com/products/75459/Intel-Core-i5-4200U-Processor-

3M-Cache-up-to-2_60-GHz. [Accessed: 09- Mar- 2016].

[99] "Intel® Core™ i3-4020Y Processor Specifications", Intel® ARK (Product Specs), 2016.

[Online]. Available: http://ark.intel.com/products/76609/Intel-Core-i3-4020Y-Processor-

3M-Cache-1_50-GHz. [Accessed: 09- Mar- 2016].

[100] B. Howse, "The Microsoft Surface Pro 4 Review: Raising The Bar", Anandtech.com,

2016. [Online]. Available: http://www.anandtech.com/show/9727/the-microsoft-surface-

pro-4-review-raising-the-bar. [Accessed: 18- Feb- 2016]. A Study of Modern Mobile Tablets - 223

[101] "Intel® Core™ m3-6Y30 Processor Specifications", Intel® ARK (Product Specs), 2016.

[Online]. Available: http://ark.intel.com/products/88198/Intel-Core-m3-6Y30-Processor-

4M-Cache-up-to-2_20-GHz. [Accessed: 09- Mar- 2016].

[102] "Intel® Core™ i5-4300U Processor Specifications", Intel® ARK (Product Specs), 2016.

[Online]. Available: http://ark.intel.com/products/76308/Intel-Core-i5-4300U-Processor-

3M-Cache-up-to-2_90-GHz. [Accessed: 09- Mar- 2016].

[103] "Intel® Core™ i5-6300U Processor Specifications", Intel® ARK (Product Specs), 2016.

[Online]. Available: http://ark.intel.com/products/88190/Intel-Core-i5-6300U-Processor-

3M-Cache-up-to-3_00-GHz. [Accessed: 09- Mar- 2016].

[104] "Intel® Core™ i7-4650U Processor Specifications", Intel® ARK (Product Specs), 2016.

[Online]. Available: http://ark.intel.com/products/75114/Intel-Core-i7-4650U-Processor-

4M-Cache-up-to-3_30-GHz. [Accessed: 09- Mar- 2016].

[105] "Intel® Core™ i7-6650U Processor Specifications", Intel® ARK (Product Specs), 2016.

[Online]. Available: http://ark.intel.com/products/91497/Intel-Core-i7-6650U-Processor-

4M-Cache-up-to-3_40-GHz. [Accessed: 09- Mar- 2016].

[106] Intel ARK, "Intel® Core™ i3-4020Y Processor (3M Cache, 1.50 GHz)", 2016. [Online].

Available: http://ark.intel.com/products/76609/Intel-Core-i3-4020Y-Processor-3M-

Cache-1_50-GHz. [Accessed: 18- Feb- 2016].

[107] Intel ARK, "Intel® Core™ i5-4300U Processor (3M Cache, up to 2.90 GHz)", 2016.

[Online]. Available: http://ark.intel.com/products/76308/Intel-Core-i5-4300U-Processor-

3M-Cache-up-to-2_90-GHz. [Accessed: 18- Feb- 2016]. A Study of Modern Mobile Tablets - 224

[108] Intel ARK, "Intel® Core™ i7-4650U Processor (4M Cache, up to 3.30 GHz)", 2016.

[Online]. Available: http://ark.intel.com/products/75114/Intel-Core-i7-4650U-Processor-

4M-Cache-up-to-3_30-GHz. [Accessed: 18- Feb- 2016].

[109] iFixit, "Microsoft Surface Pro Teardown", 2016. [Online]. Available:

https://www.ifixit.com/Teardown/Microsoft+Surface+Pro+Teardown/12842. [Accessed:

18- Feb- 2016].

[110] iFixit, "Microsoft Surface Pro 2 Teardown", 2016. [Online]. Available:

https://www.ifixit.com/Teardown/Microsoft+Surface+Pro+2+Teardown/18604.

[Accessed: 18- Feb- 2016].

[111] iFixit, "Microsoft Surface Pro 3 Teardown", 2016. [Online]. Available:

https://www.ifixit.com/Teardown/Microsoft+Surface+Pro+3+Teardown/26595.

[Accessed: 18- Feb- 2016].

[112] iFixit, "Microsoft Surface Pro 4 Teardown", 2016. [Online]. Available:

https://www.ifixit.com/Teardown/Microsoft+Surface+Pro+4+Teardown/51568.

[Accessed: 18- Feb- 2016].

[113] "Microsoft Surface Pro features", Microsoft.com. [Online]. Available:

https://www.microsoft.com/surface/en-ca/support/getting-started/surface-pro-features.

[Accessed: 12- Apr- 2016].

[114] "Surface Pro 2", Microsoft Surface. [Online]. Available:

https://www.microsoft.com/surface/en-ca/devices/surface-pro-2. [Accessed: 12- Apr-

2016]. A Study of Modern Mobile Tablets - 225

[115] "Surface Pro 3", Microsoft Surface. [Online]. Available:

https://www.microsoft.com/surface/en-ca/devices/surface-pro-3. [Accessed: 12- Apr-

2016].

[116] Microsoft.com, "Surface Book", 2016. [Online]. Available:

https://www.microsoft.com/surface/en-ca/devices/surface-book#techspec-block.

[Accessed: 18- Feb- 2016].

[117] B. Howse, "The Microsoft Surface Book Review", Anandtech.com, 2016. [Online].

Available: http://www.anandtech.com/show/9767/microsoft-surface-book-2015-review.

[Accessed: 18- Feb- 2016].

[118] "Intel® Core™ i7-6600U Processor Specifications", Intel® ARK (Product Specs), 2016.

[Online]. Available: http://ark.intel.com/products/88192/Intel-Core-i7-6600U-Processor-

4M-Cache-up-to-3_40-GHz. [Accessed: 09- Mar- 2016].

[119] iFixit, "Microsoft Surface Book Teardown", 2016. [Online]. Available:

https://www.ifixit.com/Teardown/Microsoft+Surface+Book+Teardown/51972.

[Accessed: 18- Feb- 2016].

[120] Cocoa Fundamentals Guide, 1st ed. Apple Inc., 2013, p. 12 - 65. [Online]. Available:

https://developer.apple.com/legacy/library/documentation/Cocoa/Conceptual/CocoaFund

amentals/CocoaFundamentals.pdf. [Accessed: 29- Mar- 2016].

[121] "Why Objective-C?", Developer.apple.com, 2010. [Online]. Available:

https://developer.apple.com/library/ios/documentation/Cocoa/Conceptual/OOP_ObjC/Art

icles/ooWhy.html. [Accessed: 29- Mar- 2016]. A Study of Modern Mobile Tablets - 226

[122] "Apple stakes its future on Next, OpenStep.", Seybold Report on Internet Publishing, vol.

1, no. 5, p. 2, 1997.

[123] Developer.apple.com, About Objective-C, 2015. [Online]. Available:

https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/Programming

WithObjectiveC/Introduction/Introduction.html. [Accessed: 29- Oct- 2015].

[124] "Transitioning to ARC Release Notes", Developer.apple.com, 2013. [Online]. Available:

https://developer.apple.com/library/ios/releasenotes/ObjectiveC/RN-

TransitioningToARC/Introduction/Introduction.html#//apple_ref/doc/uid/TP40011226-

CH1-SW4. [Accessed: 29- Mar- 2016].

[125] "Values and Collections", Developer.apple.com, 2014. [Online]. Available:

https://developer.apple.com/library/ios/documentation/Cocoa/Conceptual/Programming

WithObjectiveC/FoundationTypesandCollections/FoundationTypesandCollections.html#/

/apple_ref/doc/uid/TP40011210-CH7-SW1. [Accessed: 29- Mar- 2016].

[126] "What's New for Visual C#", Msdn.microsoft.com, 2016. [Online]. Available:

https://msdn.microsoft.com/en-us/library/hh156499.aspx. [Accessed: 29- Mar- 2016].

[127] M. H. Lutz and P. A. Laplante, “C# and the .NET Framework: Ready for Real Time?,”

IEEE Software, vol. 20, no. 1, p. 74, Feb. 2003.

[128] "Garbage Collection", Msdn.microsoft.com. [Online]. Available:

https://msdn.microsoft.com/en-us/library/0xy59wtx(v=vs.110).aspx. [Accessed: 29- Mar-

2016]. A Study of Modern Mobile Tablets - 227

[129] "Fundamentals of Garbage Collection", Msdn.microsoft.com. [Online]. Available:

https://msdn.microsoft.com/en-us/library/ee787088(v=vs.110).aspx. [Accessed: 29- Mar-

2016].

[130] "Xcode - Downloads - Apple Developer", Developer.apple.com, 2016. [Online].

Available: https://developer.apple.com/xcode/download/. [Accessed: 24- Mar- 2016].

[131] "Xcode 7 Release Notes", Developer.apple.com, 2016. [Online]. Available:

https://developer.apple.com/library/ios/releasenotes/DeveloperTools/RN-

Xcode/Chapters/xc7_release_notes.html#//apple_ref/doc/uid/TP40001051-CH5-SW1.

[Accessed: 24- Mar- 2016].

[132] "Xcode 4 Release Notes", Developer.apple.com, 2016. [Online]. Available:

https://developer.apple.com/library/ios/releasenotes/DeveloperTools/RN-

Xcode/Chapters/xc4_release_notes.html#//apple_ref/doc/uid/TP40001051-CH3-SW2.

[Accessed: 24- Mar- 2016].

[133] "Xcode Overview: Workspace Window Overview", Developer.apple.com, 2016.

[Online]. Available:

https://developer.apple.com/library/tvos/documentation/ToolsLanguages/Conceptual/Xco

de_Overview/TheWorkspaceWindow.html#//apple_ref/doc/uid/TP40010215-CH25-

SW1. [Accessed: 24- Mar- 2016].

[134] "Xcode Overview: Connecting Objects to Code", Developer.apple.com. [Online].

Available:

https://developer.apple.com/library/ios/documentation/ToolsLanguages/Conceptual/Xcod

e_Overview/ConnectingObjectstoCode.html#//apple_ref/doc/uid/TP40010215-CH44-

SW1. [Accessed: 24- Mar- 2016]. A Study of Modern Mobile Tablets - 228

[135] "Xcode Overview: Running on a Device", Developer.apple.com, 2016. [Online].

Available:

https://developer.apple.com/library/tvos/documentation/ToolsLanguages/Conceptual/Xco

de_Overview/RunningonaDevice.html#//apple_ref/doc/uid/TP40010215-CH55-SW1.

[Accessed: 26- Mar- 2016].

[136] "Xcode Overview: Working with Targets", Developer.apple.com, 2016. [Online].

Available:

https://developer.apple.com/library/tvos/documentation/ToolsLanguages/Conceptual/Xco

de_Overview/WorkingwithTargets.html#//apple_ref/doc/uid/TP40010215-CH32-SW1.

[Accessed: 26- Mar- 2016].

[137] "Adding Capabilities", Developer.apple.com, 2016. [Online]. Available:

https://developer.apple.com/library/tvos/documentation/IDEs/Conceptual/AppDistributio

nGuide/AddingCapabilities/AddingCapabilities.html#//apple_ref/doc/uid/TP40012582-

CH26. [Accessed: 28- Mar- 2016].

[138] "On-Demand Resources Essentials", Developer.apple.com, 2016. [Online]. Available:

https://developer.apple.com/library/tvos/documentation/FileManagement/Conceptual/On

_Demand_Resources_Guide/index.html#//apple_ref/doc/uid/TP40015083. [Accessed:

28- Mar- 2016].

[139] "Accessing and Downloading On-Demand Resources", Developer.apple.com, 2016.

[Online]. Available:

https://developer.apple.com/library/tvos/documentation/FileManagement/Conceptual/On

_Demand_Resources_Guide/Managing.html#//apple_ref/doc/uid/TP40015083-CH4-

SW1. [Accessed: 28- Mar- 2016]. A Study of Modern Mobile Tablets - 229

[140] "Visual Studio 2015 Compatibility", Visualstudio.com, 2016. [Online]. Available:

https://www.visualstudio.com/en-us/products/visual-studio-2015-compatibility-vs.aspx.

[Accessed: 28- Mar- 2016].

[141] "What's New in Visual Studio 2012", Msdn.microsoft.com, 2016. [Online]. Available:

https://msdn.microsoft.com/en-us/library/bb386063(v=vs.110).aspx. [Accessed: 28- Mar-

2016].

[142] "What is XAML?", Msdn.microsoft.com, 2016. [Online]. Available:

https://msdn.microsoft.com/en-us/library/cc295302.aspx. [Accessed: 28- Mar- 2016].

[143] "Windows 8.1: Side load your apps onto your test device", blogs.msdn.microsoft.com,

2016. [Online]. Available:

https://blogs.msdn.microsoft.com/sbrand/2014/01/07/windows-8-1-side-load-your-apps-

onto-your-test-device/. [Accessed: 28- Mar- 2016].

[144] "Configure a Windows 8.1 app package by using the manifest designer",

Msdn.microsoft.com, 2016. [Online]. Available: https://msdn.microsoft.com/en-

us/library/br230259.aspx. [Accessed: 28- Mar- 2016].

[145] "Capability - Windows app development", Msdn.microsoft.com, 2016. [Online].

Available: https://msdn.microsoft.com/en-ca/library/windows/apps/br211423.aspx.

[Accessed: 28- Mar- 2016].

[146] "App contracts and extensions (Windows Runtime apps) - Windows app development",

Msdn.microsoft.com, 2016. [Online]. Available:

https://msdn.microsoft.com/library/windows/apps/hh464906.aspx. [Accessed: 28- Mar-

2016]. A Study of Modern Mobile Tablets - 230

[147] "Apple ID Frequently Asked Questions", Appleid.apple.com, 2016. [Online]. Available:

https://appleid.apple.com/ca/#!&page=faq. [Accessed: 29- Mar- 2016].

[148] "Apple Developer", Idmsa.apple.com, 2016. [Online]. Available:

https://idmsa.apple.com/IDMSWebAuth/login?&appIdKey=891bd3417a7776362562d21

97f89480a8547b108fd934911bcbea0110d07f757&path=%2F%2Fmembercenter%2Finde

x.action. [Accessed: 29- Mar- 2016].

[149] "Creating an iTunes Connect Record for an App", Developer.apple.com, 2016. [Online].

Available:

https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iT

unesConnect_Guide/Chapters/CreatingiTunesConnectRecord.html#//apple_ref/doc/uid/T

P40011225-CH13-SW1. [Accessed: 29- Mar- 2016].

[150] "Configuring Store Technologies", Developer.apple.com, 2016. [Online]. Available:

https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iT

unesConnect_Guide/Chapters/ConfiguringStoreTechnologies.html#//apple_ref/doc/uid/T

P40011225-CH2-SW6. [Accessed: 29- Mar- 2016].

[151] "Uploading a Build for an App", Developer.apple.com, 2016. [Online]. Available:

https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iT

unesConnect_Guide/Chapters/UploadingBinariesforanApp.html#//apple_ref/doc/uid/TP4

0011225-CH38-SW1. [Accessed: 29- Mar- 2016].

[152] "Submitting the App to App Review", Developer.apple.com, 2016. [Online]. Available:

https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iT

unesConnect_Guide/Chapters/SubmittingTheApp.html#//apple_ref/doc/uid/TP40011225-

CH33-SW1. [Accessed: 29- Mar- 2016]. A Study of Modern Mobile Tablets - 231

[153] "Common App Rejections", Developer.apple.com. [Online]. Available:

https://developer.apple.com/app-store/review/rejections/. [Accessed: 30- Mar- 2016].

[154] "UI Design Do's and Don'ts - Apple Developer", Developer.apple.com. [Online].

Available: https://developer.apple.com/design/tips/. [Accessed: 30- Mar- 2016].

[155] "App Store Review Guidelines - Apple Developer", Developer.apple.com, 2015.

[Online]. Available: https://developer.apple.com/app-

store/review/guidelines/#functionality. [Accessed: 30- Mar- 2016].

[156] "Microsoft Account", Microsoft Account Official Home. [Online]. Available:

https://www.microsoft.com/en-us/account. [Accessed: 30- Mar- 2016].

[157] "Create your app by reserving a name", Msdn.microsoft.com, 2016. [Online]. Available:

https://msdn.microsoft.com/en-us/windows/uwp/publish/create-your-app-by-reserving-a-

name. [Accessed: 30- Mar- 2016].

[158] "The App Certification Process", Msdn.microsoft.com, 2016. [Online]. Available:

https://msdn.microsoft.com/en-us/windows/uwp/publish/the-app-certification-process.

[Accessed: 30- Mar- 2016].

[159] "Purchase and Activation - Support - Apple Developer", Developer.apple.com, 2016.

[Online]. Available: https://developer.apple.com/support/purchase-activation/. [Accessed:

30- Mar- 2016].

[160] "Apple Developer Enterprise Program - Apple Developer", Developer.apple.com, 2016.

[Online]. Available: https://developer.apple.com/programs/enterprise/. [Accessed: 30-

Mar- 2016]. A Study of Modern Mobile Tablets - 232

[161] "Account types, locations, and fees", Msdn.microsoft.com, 2016. [Online]. Available:

https://msdn.microsoft.com/en-us/windows/uwp/publish/account-types-locations-and-

fees. [Accessed: 30- Mar- 2016].

[162] "About the iOS Technologies", Developer.apple.com, 2014. [Online]. Available:

https://developer.apple.com/library/ios/documentation/Miscellaneous/Conceptual/iPhone

OSTechOverview/Introduction/Introduction.html#//apple_ref/doc/uid/TP40007898.

[Accessed: 30- Mar- 2016].

[163] "iOS 5.0", Developer.apple.com, 2016. [Online]. Available:

https://developer.apple.com/library/ios/releasenotes/General/WhatsNewIniOS/Articles/iO

S5.html. [Accessed: 30- Mar- 2016].

[164] "iOS 6.0", Developer.apple.com, 2016. [Online]. Available:

https://developer.apple.com/library/ios/releasenotes/General/WhatsNewIniOS/Articles/iO

S6.html#//apple_ref/doc/uid/TP40011812-SW1. [Accessed: 30- Mar- 2016].

[165] "iOS 7.0", Developer.apple.com, 2016. [Online]. Available:

https://developer.apple.com/library/ios/releasenotes/General/WhatsNewIniOS/Articles/iO

S7.html#//apple_ref/doc/uid/TP40013162-SW1. [Accessed: 30- Mar- 2016].

[166] "iOS 8.0", Developer.apple.com, 2016. [Online]. Available:

https://developer.apple.com/library/ios/releasenotes/General/WhatsNewIniOS/Articles/iO

S8.html#//apple_ref/doc/uid/TP40014205-SW1. [Accessed: 30- Mar- 2016]. A Study of Modern Mobile Tablets - 233

[167] "iOS 9.0", Developer.apple.com, 2016. [Online]. Available:

https://developer.apple.com/library/ios/releasenotes/General/WhatsNewIniOS/Articles/iO

S9.html#//apple_ref/doc/uid/TP40016198-SW1. [Accessed: 30- Mar- 2016].

[168] "Windows RT 8.1: FAQ - Windows Help", windows.microsoft.com. [Online]. Available:

http://windows.microsoft.com/en-CA/windows/windows-rt-faq. [Accessed: 30- Mar-

2016].

[169] "Windows 10 - Microsoft", Microsoft.com, 2016. [Online]. Available:

https://www.microsoft.com/en-ca/windows/features. [Accessed: 30- Mar- 2016].

[170] AcqNotes, "AcqOps", 2016. [Online]. Available:

http://acqnotes.com/acqnote/careerfields/software-development-approaches. [Accessed:

20- Feb- 2016].

[171] AcqNotes, Incremental Waterfall. 2016.

[172] "CMMotionManager Class Reference", Developer.apple.com, 2013. [Online]. Available:

https://developer.apple.com/library/ios/documentation/CoreMotion/Reference/CMMotion

Manager_Class/#//apple_ref/doc/uid/TP40009670-CH1-SW9. [Accessed: 17- Mar-

2016].

[173] "Accelerometer class - Windows app development", Msdn.microsoft.com. [Online].

Available: https://msdn.microsoft.com/en-

us/library/windows.devices.sensors.accelerometer.aspx?cs-save- lang=1&cs-

lang=csharp#code-snippet-1. [Accessed: 23- Mar- 2016]. A Study of Modern Mobile Tablets - 234

[174] "TIOBE Index | Tiobe - The Software Quality Company", Tiobe.com, 2016. [Online].

Available: http://www.tiobe.com/tiobe_index. [Accessed: 23- Mar- 2016].

[175] "The Objective-C Programming Language", Tiobe.com, 2016. [Online]. Available:

http://www.tiobe.com/tiobe_index?page=Objective-C. [Accessed: 23- Mar- 2016].

[176] " The C# Programming Language", Tiobe.com, 2016. [Online]. Available:

http://www.tiobe.com/tiobe_index?page=C%23. [Accessed: 23- Mar- 2016].