DOCSLIB.ORG

Software Development for Mobile Computing, the Internet of Things and Wearable Devices: Inspecting the Past to Understand the Future

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Software Development for Mobile Computing, the Internet of Things and Wearable Devices: Inspecting the Past to Understand the Future Proceedings of the 52nd Hawaii International Conference on System Sciences | 2019 Software Development for Mobile Computing, the Internet of Things and Wearable Devices: Inspecting the Past to Understand the Future Tor-Morten Grønli Andreas Biørn-Hansen Tim A. Majchrzak Kristiania University College, Kristiania University College, University of Agder, Dep. Technology, Oslo, Norway Dep. Technology, Oslo, Norway Kristiansand, Norway [email protected] [email protected] [email protected] Abstract texting a friend on the phone, and over time as the conversation is flowing s/he is on the move, and begin Currently a convergence in software development to consume the messages on a wearable device such as for mobile computing (including mobile devices and a smartwatch whilst moving. Back at the office s/he special technology such as wearables) and the Internet will move over to use the stationary computer as input of Things (IoT) can be observed. Devices from the device. Extending further, voice recognition can be fields are becoming part of a joint ecosystem and enabled by the IoT device residing on the office desk share the same infrastructure. Moreover, development and complete the multi-dimensional interaction. processes have changed and user requirements have Mobile technology and IoT form a multidisciplinary become very heterogeneous. We have been studying field where sensing devices with communication this development for a while, also by offering the fitting capabilities that can be applied to ordinary objects HICSS minitrack. In this article, we look into the in order to make the object “smart”. They add a past of software development for mobile devices, in the whole new dimension of content to the current Internet context of IoT, and for wearables. We analyse joint paradigm [2]. The topic of wearable computing and characteristics and show differences. Then we invite to smart garments have been researched and developed a discussion that leads to a research outlook. While for several decades [3], but only in recent years has neither for industry nor for academia the journey is become a popular research field. Gartner first introduced over, the convergence of fields should offer many new Wearable User Interfaces into their Hype Cycle for possibilities, prevent problems we faced in the past, but Emerging Technologies in 2013, two years after also introduce novel challenges. introducing Internet of Things [4]. This exemplifies how a field with root back decades has been re-established with a contemporary consumer focus and created a new 1. Introduction arena of possible outlets for software developers. Mobile computing, Internet of Things (IoT) and Because of this extensive heterogeneous wearable devices are joining forces and becoming part environment, it is important that research focuses of the same ecosystem and infrastructure. In modern on established architectures and integration with applications of today the focus is (and should) be on existing business practices, and not only provides solving a specific user’s or group of users’ needs. This prototypes and single-case studies. The landscape for has traditionally been done through the investigation of software development has become highly dynamic requirements, prototyping, design, implementation and and given the diversity of the field, we showcase how testing [1]. Multi-disciplinary teams collaborating in mobile devices, Internet of Things and wearables are all order to create a satisfactory solution. parts coming together in one ecosystem. We explore Today this has changed. We still need to solve this phenomena by looking into the past, and highlight specific needs, but the user environment has become research contributions and challenges. even more heterogeneous, as we continue to investigate Our article makes two contributions. First, we draw throughout this paper. The focus has shifted to not a comprehensive picture of software development for (only) solving needs, but to completing tasks. The user mobile computing – both looking at mobile devices in is agnostic to what kind of device the task is solved on, general and at wearables in particular – and IoT. Second, and would often utilise more than one device before we provide an outlook into the expected research completion. Further to this, interaction is based on activities and development in the field. convenience and availability. For instance, a user starts The remainder is structured as follows. First URI: https://hdl.handle.net/10125/60182 ISBN: 978-0-9981331-2-6 Page 7451 (CC BY-NC-ND 4.0) we present an overview of state-of-the-art in mobile or criteria originating from the industry (e.g. [27]), computing, Internet of Things and wearable computing. although we rarely encounter case studies in which the Following this we venture into the development engineering itself is in focus. This section will introduce ecosystems for these three concepts before discussing research in some frequently encountered topics. the current state of affairs. We then present a synthesis While there exist numerous papers on these and in the form of a research outlook. related topics (e.g. [8, 9, 15, 16, 26]), we frequently find ourselves questioning what to focus on going 2. Background forward. In studies on mobile security, we tend to encounter discussions on attack surfaces (e.g. [28, We will in the following section highlight related 29, 30]), ecosystem vulnerabilities (e.g. [31]), and work, and give an overview of the major research investigations of app-level security measures through streams and contributions in the fields of mobile permissions (e.g. [32, 33]). However, from the computing, Internet of Things and wearable devices. literature, we note that security is not necessarily a topic that practitioners are devoted to, according to interviews 2.1. Basics conducted by Ahmad et al. [34], whom also mention a lack of security-oriented studies in the related research As depicted in 1, the three fields are closely related. community. Mobile computing spawned the dawn of Internet of Things for the masses. It is no longer confined to We find that on the topic of performance research, industry projects. Building closely on this, the wearable studies span from the introduction of modern computing paradigm evolved out of sensors becoming smartphone devices, and continue to regularly emerge common place and its use being proven to a large portion in academic outlets [15, 16, 35]. Nevertheless, due of the general public. to the rapid and constantly evolving nature of both software, hardware, and surrounding ecosystems, the continuation of empirical performance measurements is Mobile Computing Internet of Things Wearable Computing key to keeping up with- and staying relevant to industry and stakeholders. Lastly, studies involving end-users Figure 1. Technological progress are less frequently encountered than the previous topics traversed. This is especially true in research on Today, we take all three paradigms for granted and as cross-platform mobile software development, in which part of our environment at home, at the office or on the case we only identify a mere handful of user-oriented move. To get a better understanding of the way forward studies (e.g. [26, 25, 21]). We are interested in seeing until today, we will start looking into the research stream this corpus of research extended, as the perception and of mobile computing. experience of app usability and quality should be core 2.2. Mobile Computing topics of interest for academics and practitioners alike. From both the research literature and practitioner Since the release of app-enabled smartphones, outlets we note that traditional approaches and counting from the 2007 announcement of iPhone [5], techniques for development of mobile apps are millions of apps have found their way to the various challenged by a wide array of new technologies and app marketplaces [6]. With the app economy generating novel concepts, some of which we will elaborate on billions of USD yearly [7], developing software and discuss throughout this paper. While the field targeting mobile devices can indeed be a profitable of mobile computing goes beyond the development endeavour. We find that numerous studies investigate the of software applications, the pace at which tools and “hows” of software application development targeting frameworks facilitating the development of mobile apps mobile devices. are released, is seemingly more rapid than ever. The Within this literature body, we find topics ranging high turnover of tools could although have serious from business predictability and development processes implications on decision-making, and consequently add (e.g. [8, 9, 10, 11]) to security (e.g. [12, 13, 14]), to quickly to technical debt. empirical performance-oriented studies (e.g. [15, 16, 17, 18, 19]), and studies focused on end-users’ perception 2.3. Internet of Things of the quality of mobile apps (e.g. [20, 21, 22, 23, 24, 25, 26]). Research on software development for mobile The Internet of Things (IoT) are amongst the fastest computing conducted in the intersection of business growing of emerging technologies of today. The IoT and software engineering often relies on requirements technologies and applications are still in their infancy, Page 7452 and so the academic community must thoroughly fitness device. The authors report of an overall increase address the area [36]. Although IoT was initially meant in activity levels across demographics, regardless of to describe a network of RadioFrequency ID-enabled gender, weight, and prior levels of activity. Studies devices, it has since been expanded a wider definition similar in nature, e.g. by Fountaine et al. [45] also report of the term incorporating sensors, actuators and agents. of an increase in activity levels for their participants in According to Perera et al. [2], most of the research done the context of benefits in individual health related to the on IoT during the last two decades has been focused use and adoption of Pokemon´ Go. around prototypes, systems and solutions with a limited However, while there are definite benefits to the number of data sources.
Load more

Recommended publications
  • Differential Fuzzing the Webassembly
    Master’s Programme in Security and Cloud Computing Differential Fuzzing the WebAssembly Master’s Thesis Gilang Mentari Hamidy MASTER’S THESIS Aalto University - EURECOM MASTER’STHESIS 2020 Differential Fuzzing the WebAssembly Fuzzing Différentiel le WebAssembly Gilang Mentari Hamidy This thesis is a public document and does not contain any confidential information. Cette thèse est un document public et ne contient aucun information confidentielle. Thesis submitted in partial fulfillment of the requirements for the degree of Master of Science in Technology. Antibes, 27 July 2020 Supervisor: Prof. Davide Balzarotti, EURECOM Co-Supervisor: Prof. Jan-Erik Ekberg, Aalto University Copyright © 2020 Gilang Mentari Hamidy Aalto University - School of Science EURECOM Master’s Programme in Security and Cloud Computing Abstract Author Gilang Mentari Hamidy Title Differential Fuzzing the WebAssembly School School of Science Degree programme Master of Science Major Security and Cloud Computing (SECCLO) Code SCI3084 Supervisor Prof. Davide Balzarotti, EURECOM Prof. Jan-Erik Ekberg, Aalto University Level Master’s thesis Date 27 July 2020 Pages 133 Language English Abstract WebAssembly, colloquially known as Wasm, is a specification for an intermediate representation that is suitable for the web environment, particularly in the client-side. It provides a machine abstraction and hardware-agnostic instruction sets, where a high-level programming language can target the compilation to the Wasm instead of specific hardware architecture. The JavaScript engine implements the Wasm specification and recompiles the Wasm instruction to the target machine instruction where the program is executed. Technically, Wasm is similar to a popular virtual machine bytecode, such as Java Virtual Machine (JVM) or Microsoft Intermediate Language (MSIL).
    [Show full text]
  • Seamless Offloading of Web App Computations from Mobile Device to Edge Clouds Via HTML5 Web Worker Migration
    Seamless Offloading of Web App Computations From Mobile Device to Edge Clouds via HTML5 Web Worker Migration Hyuk Jin Jeong Seoul National University SoCC 2019 Virtual Machine & Optimization Laboratory Department of Electrical and Computer Engineering Seoul National University Computation Offloading Mobile clients have limited hardware resources Require computation offloading to servers E.g., cloud gaming or cloud ML services for mobile Traditional cloud servers are located far from clients Suffer from high latency 60~70 ms (RTT from our lab to the closest Google Cloud DC) Latency<50 ms is preferred for time-critical games Cloud data center End device [Kjetil Raaen, NIK 2014] 2 Virtual Machine & Optimization Laboratory Edge Cloud Edge servers are located at the edge of the network Provide ultra low (~a few ms) latency Central Clouds Mobile WiFi APs Small cells Edge Device Cloud Clouds What if a user moves? 3 Virtual Machine & Optimization Laboratory A Major Issue: User Mobility How to seamlessly provide a service when a user moves to a different server? Resume the service at the new server What if execution state (e.g., game data) remains on the previous server? This is a challenging problem Edge computing community has struggled to solve it • VM Handoff [Ha et al. SEC’ 17], Container Migration [Lele Ma et al. SEC’ 17], Serverless Edge Computing [Claudio Cicconetti et al. PerCom’ 19] We propose a new approach for web apps based on app migration techniques 4 Virtual Machine & Optimization Laboratory Outline Motivation Proposed system WebAssembly
    [Show full text]
  • Webassembly a New World of Native Exploits on the Web Agenda
    WebAssembly A New World Of Native Exploits On The Web Agenda • Introduction • The WebAssembly Platform • Emscripten • Possible Exploit Scenarios • Conclusion Wasm: What is it good for? ● Archive.org web emulators ● Image/processing ● Video Games ● 3D Modeling ● Cryptography Libraries ● Desktop Application Ports Wasm: Crazy Incoming ● Browsix, jslinux ● Runtime.js (Node), Nebulet ● Cervus ● eWASM Java Applet Joke Slide ● Sandboxed ● Virtual Machine, runs its own instruction set ● Runs in your browser ● Write once, run anywhere ● In the future, will be embedded in other targets What Is WebAssembly? ● A relatively small set of low-level instructions ○ Instructions are executed by browsers ● Native code can be compiled into WebAssembly ○ Allows web developers to take their native C/C++ code to the browser ■ Or Rust, or Go, or anything else that can compile to Wasm ○ Improved Performance Over JavaScript ● Already widely supported in the latest versions of all major browsers ○ Not limited to running in browsers, Wasm could be anywhere Wasm: A Stack Machine Text Format Example Linear Memory Model Subtitle Function Pointers Wasm in the Browser ● Wasm doesn’t have access to memory, DOM, etc. ● Wasm functions can be exported to be callable from JS ● JS functions can be imported into Wasm ● Wasm’s linear memory is a JS resizable ArrayBuffer ● Memory can be shared across instances of Wasm ● Tables are accessible via JS, or can be shared to other instances of Wasm Demo: Wasm in a nutshell Emscripten ● Emscripten is an SDK that compiles C/C++ into .wasm binaries ● LLVM/Clang derivative ● Includes built-in C libraries, etc. ● Also produces JS and HTML code to allow easy integration into a site.
    [Show full text]
  • Superoptimization of Webassembly Bytecode
    Superoptimization of WebAssembly Bytecode Javier Cabrera Arteaga Shrinish Donde Jian Gu Orestis Floros [email protected] [email protected] [email protected] [email protected] Lucas Satabin Benoit Baudry Martin Monperrus [email protected] [email protected] [email protected] ABSTRACT 2 BACKGROUND Motivated by the fast adoption of WebAssembly, we propose the 2.1 WebAssembly first functional pipeline to support the superoptimization of Web- WebAssembly is a binary instruction format for a stack-based vir- Assembly bytecode. Our pipeline works over LLVM and Souper. tual machine [17]. As described in the WebAssembly Core Specifica- We evaluate our superoptimization pipeline with 12 programs from tion [7], WebAssembly is a portable, low-level code format designed the Rosetta code project. Our pipeline improves the code section for efficient execution and compact representation. WebAssembly size of 8 out of 12 programs. We discuss the challenges faced in has been first announced publicly in 2015. Since 2017, it has been superoptimization of WebAssembly with two case studies. implemented by four major web browsers (Chrome, Edge, Firefox, and Safari). A paper by Haas et al. [11] formalizes the language and 1 INTRODUCTION its type system, and explains the design rationale. The main goal of WebAssembly is to enable high performance After HTML, CSS, and JavaScript, WebAssembly (WASM) has be- applications on the web. WebAssembly can run as a standalone VM come the fourth standard language for web development [7]. This or in other environments such as Arduino [10]. It is independent new language has been designed to be fast, platform-independent, of any specific hardware or languages and can be compiled for and experiments have shown that WebAssembly can have an over- modern architectures or devices, from a wide variety of high-level head as low as 10% compared to native code [11].
    [Show full text]
  • Swivel: Hardening Webassembly Against Spectre
    Swivel: Hardening WebAssembly against Spectre Shravan Narayan† Craig Disselkoen† Daniel Moghimi¶† Sunjay Cauligi† Evan Johnson† Zhao Gang† Anjo Vahldiek-Oberwagner? Ravi Sahita∗ Hovav Shacham‡ Dean Tullsen† Deian Stefan† †UC San Diego ¶Worcester Polytechnic Institute ?Intel Labs ∗Intel ‡UT Austin Abstract in recent microarchitectures [41] (see Section 6.2). In con- We describe Swivel, a new compiler framework for hardening trast, Spectre can allow attackers to bypass Wasm’s isolation WebAssembly (Wasm) against Spectre attacks. Outside the boundary on almost all superscalar CPUs [3, 4, 35]—and, browser, Wasm has become a popular lightweight, in-process unfortunately, current mitigations for Spectre cannot be im- sandbox and is, for example, used in production to isolate plemented entirely in hardware [5, 13, 43, 51, 59, 76, 81, 93]. different clients on edge clouds and function-as-a-service On multi-tenant serverless, edge-cloud, and function as a platforms. Unfortunately, Spectre attacks can bypass Wasm’s service (FaaS) platforms, where Wasm is used as the way to isolation guarantees. Swivel hardens Wasm against this class isolate mutually distursting tenants, this is particulary con- 1 of attacks by ensuring that potentially malicious code can nei- cerning: A malicious tenant can use Spectre to break out of ther use Spectre attacks to break out of the Wasm sandbox nor the sandbox and read another tenant’s secrets in two steps coerce victim code—another Wasm client or the embedding (§5.4). First, they mistrain different components of the under- process—to leak secret data. lying control flow prediction—the conditional branch predic- We describe two Swivel designs, a software-only approach tor (CBP), branch target buffer (BTB), or return stack buffer that can be used on existing CPUs, and a hardware-assisted (RSB)—to speculatively execute code that accesses data out- approach that uses extension available in Intel® 11th genera- side the sandbox boundary.
    [Show full text]
  • Webassembly Backgrounder
    Copyright (c) Clipcode Limited 2021 - All rights reserved Clipcode is a trademark of Clipcode Limited - All rights reserved WebAssembly Backgrounder [DRAFT] Written By Eamon O’Tuathail Last updated: January 8, 2021 Table of Contents 1: Introduction.................................................................................................3 2: Tooling & Getting Started.............................................................................13 3: Values.......................................................................................................18 4: Flow Control...............................................................................................27 5: Functions...................................................................................................33 6: (Linear) Memory.........................................................................................42 7: Tables........................................................................................................50 1: Introduction Overview The WebAssembly specification is a definition of an instruction set architecture (ISA) for a virtual CPU that runs inside a host embedder. Initially, the most widely used embedder is the modern standard web browser (no plug-ins required). Other types of embedders can run on the server (e.g. inside standard Node.js v8 – no add-ons required) or in future there could be more specialist host embedders such as a cross- platform macro-engine inside desktop, mobile or IoT applications. Google, Mozilla, Microsoft and
    [Show full text]
  • Formally Verifying Webassembly with Kwasm
    Formally Verifying WebAssembly with KWasm Towards an Automated Prover for Wasm Smart Contracts Master’s thesis in Computer Science and Engineering RIKARD HJORT Department of Computer Science and Engineering CHALMERS UNIVERSITY OF TECHNOLOGY UNIVERSITY OF GOTHENBURG Gothenburg, Sweden 2020 Master’s thesis 2020 Formally Verifying WebAssembly with KWasm Towards an Automated Prover for Wasm Smart Contracts RIKARD HJORT Department of Computer Science and Engineering Chalmers University of Technology University of Gothenburg Gothenburg, Sweden 2020 Formally Verifying WebAssembly with KWasm Towards an Automated Prover for Wasm Smart Contracts RIKARD HJORT © RIKARD HJORT, 2020. Supervisor: Thomas Sewell, Department of Computer Science and Engineering Examiner: Wolfgang Ahrendt, Department of Computer Science and Engineering Master’s Thesis 2020 Department of Computer Science and Engineering Chalmers University of Technology and University of Gothenburg SE-412 96 Gothenburg Telephone +46 31 772 1000 Cover: Conceptual rendering of the KWasm system, as the logos for K ans Web- Assembly merged together, with a symbolic execution proof tree protruding. The cover image is made by Bogdan Stanciu, with permission. The WebAssembly logo made by Carlos Baraza and is licensed under Creative Commons License CC0. The K logo is property of Runtime Verification, Inc., with permission. Typeset in LATEX Gothenburg, Sweden 2020 iv Formally Verifying WebAssembly with KWasm Towards an Automated Prover for Wasm Smart Contracts Rikard Hjort Department of Computer Science and Engineering Chalmers University of Technology and University of Gothenburg Abstract A smart contract is immutable, public bytecode which handles valuable assets. This makes it a prime target for formal methods. WebAssembly (Wasm) is emerging as bytecode format for smart contracts.
    [Show full text]
  • Microsoft Band SDK
    Microsoft Band SDK SDK Documentation By using this Microsoft Band SDK, you agree to be bound by the Terms of Use. Further, if accepting on behalf of a company, you represent that you’re authorized to act on your company’s behalf. 1 Introduction and Features ............................................................................................................ 4 1.1 Multi-Platform Support ..................................................................................................................... 4 1.2 Getting Sensor Data ........................................................................................................................... 4 1.3 Creating Tiles and Sending Notifications ............................................................................................. 6 1.3.1 App Tiles ................................................................................................................................................................... 6 1.3.2 App Notifications ...................................................................................................................................................... 7 1.3.3 Haptic Notifications .................................................................................................................................................. 7 1.3.4 Band Personalization ................................................................................................................................................ 8 1.3.4.1 Me Tile ............................................................................................................................................................
    [Show full text]
  • Why You Should Consider Web Assembly in Your Next Frontend Project
    Why you should consider Web Assembly in your next frontend project Håkan Silfvernagel Who Am I? • Background in software development for process automation and robotics • Worked on the .NET platform since its release 2001-2002 • Consultant since 2010 • 19 years’ experience of software development in various positions such as developer, tester, architect, project manager, scrum master, practice manager and team lead. • MIT Artificial Intelligence: Implications for business strategy • MIT Internet of Things: Business implications and opportunities What is Web Assembly? Web Assembly • Group formed in 2015 (all major browsers) • 2017, Nov, Web Assembly Released • 2018, Feb, W3C public draft published Source: https://webassembly.org/ Web platform as virtual machine Virtual Machine • JavaScript • High level language • Flexible and expressive • Dynamically typed JS WASM • No compilation • Huge ecosystem • WebAssembly (WASM) • Low level assembly like language • Compact binary format • Near native performance • C, C++, Rust, Go… Wasm • A new browser standard • Based on asm.js • Intermediate language • Java (bytecode), C# (msil) • Strongly typed • i32, i64, f32, f64 Hello WASM WASM example (1) add.wat (module (func $addTwo (param i32 i32) (result i32) get_local 0 get_local 1 i32.add) (export "addTwo" (func $addTwo))) 0000000: 0061 736d ; WASM_BINARY_MAGIC 0000004: 0100 0000 ; WASM_BINARY_VERSION ; section "Type" (1) 0000008: 01 ; section code 0000009: 00 ; section size (guess) 000000a: 01 ; num types WASM example (2) ; type 0 000000b: 60 ; func
    [Show full text]
  • Comparison Chart Microsoft Band – Kevin Martin Sony Smartwatch 3
    What Wearable Device Do I Buy and Why? PC Retreat 2015 What Do You Want in a Smartwatch? • Fitness Tracking • Phone notifications • Tell time • Long battery life • Style What Wearable Device • Affordability Do I Buy and Why? • More? Kevin Martin, Jonathan Lewis, Parag Joshi Comparison Chart Microsoft Band –Kevin Martin Motorola Apple Pebble Fitbit Sony Microsoft • Windows 8.1, iOS 7.1+, Android 4.3+ Moto 360 Watch Classic Charge HR SmartWatch 3 Band • Battery Life: 2 days Operating Windows Vista+, Windows 8.1+, Android 2.3+ Mac OS X 10.6+, System Android 4.3+ iOS 8+ Android 4.1+ Android 4.1+ iOS • Screen Size: 11mm x 33mm iOS 5+ iOS 6+, Android Syncs With 7.1 4.1+ • Wireless Connectivity: Bluetooth Battery Life 1.5 days 1 day 7 days 5 days 2 days 2 days Screen Size 1.56 inches 1.32 inches 1.26 inches .83 inches 1.6 inches 11mm x 33mm • Splash proof Wireless Bluetooth and Bluetooth Bluetooth and Bluetooth, NFC Bluetooth Bluetooth Connectivity WiFi and WiFi USB cable and WiFi • Built‐in fitness tracking, heart rate monitor and GPS Waterproof? Up to 30m No Up to 50m No Up to 1.5m No • Virtual keyboard Fitness Built‐in + HR + Built‐in + HR + UV + Built‐in + HR Built‐in With app Built‐in Tracking? Sleep Tracking GPS • Notifications: Alarm, Calendar Reminder, E‐mail, Facebook, Incoming Notifications? Yes Yes Yes Yes Yes Yes Call, Missed Call, Text Message, Timer, Twitter, and Weather Starting Price $300 $350 $100 $150 $180 $160 • Starting at $160 with $40 rebate Sony SmartWatch 3 – Jonathan Lewis Apple Watch – Parag Joshi • iOS 8+ • Android
    [Show full text]
  • Notice of Dispute—Kinect for Windows
    Notice of Dispute—Microsoft Software, Devices, and Services with Arbitration Agreements Microsoft is committed to resolving disputes fairly and efficiently. If you are unsatisfied with the resolution a customer service representative offers for your problem, you may notify us of your dispute by mailing this form to Microsoft. Please print legibly and complete this form. Send the completed form by U.S. mail to: Microsoft Corporation CELA Arbitration One Microsoft Way Redmond, WA 98052-6399 Keep a copy for your records. A Microsoft representative will respond within 60 days of receiving this form. If the dispute is not resolved to your satisfaction, you may begin arbitration after 60 days by submitting a Demand for Arbitration to the American Arbitration Association. You can find a Demand for Arbitration form at go.microsoft.com/fwlink/?linkid=245497. Your name Your phone number Additional number during business hours Your e-mail address Your fax number Your address: Your gamertag (if your dispute is about Xbox) Your Microsoft account (if you have one) (formerly called Windows Live ID) Your serial number (for devices) My dispute is about (check Microsoft software, device, or service): Bing Ads Program Cortana Microsoft Health, HealthVault, or Device Health App Kinect Bundled with Xbox 360 E Microsoft OneNote (Windows Store) or Onenote.com Kinect for Xbox One Kinect for Windows Microsoft Answer Desk Support Services (continued on page two) Microsoft Band Microsoft Office 2013 or 2016 Microsoft Business Applications Services Microsoft
    [Show full text]
  • Microsoft Band 2 Experience Design Guidelines
    1 Microsoft Band 2 Experience Design Guidelines Published for Third Party Version 2.0 Microsoft Band 2 2 Welcome Microsoft Band 2 Experience Design Guidelines These guidelines provide an overview of the Band, and define guidelines for the user experience for developers of third party apps. Microsoft Band 2 3 Table of Contents Introduction Glossary Interaction Patterns Typography Color Iconography Template Library Microsoft Band 2 Introduction 4 Microsoft Band 2 Direct, yet discrete. Forgiving. Experience Principals Notifications are timely, not disruptive and quick to Interactions are hyper-mobile. A nondestructive dismiss. Information passes from you to the cloud and interface tailored for the range of human motion. The experience principles should be back again in a direct, yet personal way. Positive reactions to your actions. Compensates taken into consideration when for error. creating app tiles for the Microsoft Band. Hyper-glanceable. In and out in eight. Buzz, ping, glance, swipe... Indoors or out, dark or Never break the stride of life... Glance, peek, and bright, the information most important to you is decide all in less than eight seconds — the right always at arm’s length. type and amount of information at the right time. Not a mini-phone. About you. Free your hands from the fear of missing out. Provide Knows your patterns and what you’ve done. enough information in the moment so you know if Anticipates your needs through smart and when you need to dig into your phone. It’s all recommendations and tracking. about the right amount of information, so you’ll never miss the moments that are most important to you.
    [Show full text]