Interactive Technologies

Transkript

1 Interactive Technologies Prof. Dr. Matthias Kranz, Priv.-Doz. Dipl.-Ing. Dr. Andreas Riener with contributions from Stefan Diewald, Patrick Lindemann, Andreas Möller, Marion Koelle, Luis Roalter, Tobias Stockinger with material partially from Prof. Dr. Andreas Butz, Dr. Paul Holleis, Prof. Dr. Albrecht Schmidt

2 Introduction & Motivation Motivating examples Basic terms and concepts A brief history of human-computer interaction (HCI) Overview and taxonomy of input and output devices Principles of user-centred design Trends in computing Source: 2

3 Interaction-oriented History of HCI People Tables and Hardware level interfaces Programming as user interface Interactive command line interfaces Graphical user interfaces and direct manipulation Multimodal UIs, Speech, and Gesture 3

4 VisiCalc - Widespread use of an Interactive Application Significant value to non-technical users, earlier: recalculate all data manually! Instantly calculating electronic spreadsheet Early killer app for PCs allowed for what if scenarios - what if we change something here, how is the impact on à freedom à no fear of interaction (undo, without hassle of recalculating) VisiCalc (1979) as ancestor of all spreadsheet calculating software last visited last visited

5 last visited last visited

6 Lessons learned from Interactive Computing Supporting immediate feedback is of great value Going beyond the input! output model is of great value to the user Provide freedom to the user (interactive calculations) Support for what if assessment (exploration of user interface without fear) 8

8 XEROX ALTO - the first PC! (1973) last visited last visited

9 XEROX Star - first commercial PC (1981) last visited

10 Apple Macintosh - first commercially successful PC (1984) last visited

11 Apple Macintosh (1984) TV ad last visited

12 More GUIs Amiga 1985 NeXTstep 1989 Win OS/

13 Graphical UIs - Characteristics Replacement of command-language Direct manipulation of the objects of interest Continuous visibility of objects and actions of interest Graphical metaphors (desktop, trash can) Windows, icons, menus and pointers (WIMP) Rapid, reversible, incremental actions Origins of direct manipulation an graphical user interfaces Ivan Sutherland s Sketchpad, 1963, object manipulation with a light pen (grabbing, moving, resizing) Douglas C. Engelbart, 1968, Mouse, NLS XEROX ALTO (50 units given to universities/researchers in 1978) XEROX Star (1981) Apple Macintosh (1984) 15

15 Multimodal Interaction Multimodality makes use of several input or output modalities Dominant (human) modalities Seeing (output from a system) Hearing (output from a system) Physical manipulation (input to a system) Further modalities Haptic (touch, sense of pressure) Proprioception (body awareness) Taste and Smell Thermoception 17

16 Speech Text to speech (TTS), system à human Speech to text (STT), recognizing spoken text, human à system (also: automatic speech recognition, ASR) form of natural interaction, hands-free Applications Voice dialog systems (telephone annoyances) Phones (Siri, Majel) Cars (upcoming trend) last visited

17 Gestures on devices / with devices in 2D, in 3D with one or multiple fingers/hands on the front of a device / on the back of a device marker-based/marker less form of natural interaction Applications table top interaction on-screen interaction Who has seen Minority Report? last visited last visited

18 Everywhere Displays Project (IBM) The Everywhere Displays project aims to develop systems that allow the transformation of every surface in a space into a projected "touch screen". Basic technology LCD projector pan/tilt mirror Camera The projected image is processed to compensate for the perspective distortion pan/tilt video camera to detect hand/body activity on the projected area people can interact with the projected image by simply touching the surface last visited

19 Possible Future Directions of Human-Computer Interaction 21

20 Technologies to look out for? Eye gaze detection (2012: Tobii (Swedish company) bought by Intel, SMI) Speech and gesture recognition (2011: mobile phones, 2013: vehicular contexts) Full body interaction (2011: Kinect) EEG (ElectroEncephaloGraphy), ECG (ElectroCardioGraphy), EMG (ElectroMyoGraphy ) interfaces (e.g. Implanted Interfaces (?) Brain Computer Interfaces (BCI) mass market (?) Already today: medical domain, disabled patients Global market leader: g.tec (Guger Technologies, Schiedlberg, Upper Austria) 22

21 Technologies to look out for? Gesture interface: Google Tango 23

22 Head Tracking, Body Tracking direct interaction / natural interaction context information (directions, ) observing the person/object (visually, depth sensing) instrumenting the person (markers, sensors) Lot of work in the movie/animation domain and in augmented reality Haritaoglu, I.; Harwood, D.; Davis, Larry S.: W4: Who, When, Where, What: A Real Time System for Detecting and Tracking People. In: Proc. Third Conf. Face and Gesture Recognition, 1998, last visited

23 Brain Computer Interfaces - Atari Mindlink (intended for release in 84, never released) last visited

24 Brain Computer Interfaces - Brain Ball last visited

25 Brain Computer Interfaces - Reality Today direct brain-machine interface (outside the head inside the head?) no more wires, no more gel à usable in all situations ideally only little training necessary thoughts and emotions as inputs last visited

26 Brain Computer Interfaces (today) Attaching / implanting electrodes close to the brain Distribution of electrodes to read activation in different areas Reading the EEG signals Classification of the signals Controls and feedback based on the signals last visited

27 Brain Computer Interfaces Applications Locked-in syndrome Cursor control Context-awareness Emotions Some Issues Control of muscle movement show strongly in the brain signals Reading movements of the body from the brain (e.g. Thad Starner suggest reading of sign language) Gel-free attachment of electrodes Very low bandwidth (currently!) Thad Starner The guy behind Google s Glass 29

28 Eye-Gaze Interaction / Eye-Tracking Implicit & explicit input eye-gaze as modality like seeing, hearing, touching, Using an eye tracker as additional input channel For explicit and implicit interaction Currently mainly used Psychology, e.g. Where do people look?, What is the path of their gaze?, How long do they look at an item? Usability testing, e.g. Where do users look first? Users with severe disabilities, e.g. Eye movement as only input Systems are still somewhat expensive now very cheap (Tobii Rex ~ 750 EUR) Hardware and processing required is already available Expectation for future devices (if it is shown that they are useful) Hardware included in the screen similar to speakers today Integration of eye tracking into everyday devices 30

29 Eye-Gaze Interaction / Eye-Tracking Pupil and reflection define the eye movement 31

30 Eye-Gaze Interaction / Eye-Tracking Measuring the direction and distance between glint (reflection) and center of the pupil (w.r.t. the tracker, then one needs to relate this to the I/O device, e.g. screen) 32

31 Eye-Gaze Interaction / Eye-Tracking - Next Generation? In the past: Eye-tracking used as a simple and limited input method, originally: mostly for disabled people The most common input method is dwell-time (how long people look at a specific spot): Actions are invoked by staring at a specific area for a fixed time Today / in the future: New interaction paradigms Eye-tracking used as context information SMI 2.0: 3-camera solution One camera observates/tracks the viewed scene Two cameras (one per eye) tracks eye movements SMI Eye Tracking Glasses 2.0, visited March 14,

32 Eye-Gaze Interaction / Eye-Tracking - Next Generation? Eye tracking today (Google Glass, etc.) Eye Gaze Features Fixation Saccades Functions Mapping of scans to content Online annotation of content Online recommender coupling Reading experience classification Typology of readers Machine learning (SVN) for classification Fixation Saccade 34

33 Eye-Gaze Interaction / in Windows 9 or 10? Or already with the new XBOX (Kinect V.2) Technik html/, last visited

34 Eye Gaze Gestures - Interaction by Eye Movement Gaze gestures are executed to perform actions Biggest advantages: Gestures do not occupy any screen real estate Do not require calibration since they work with relative movements Appropriate for small tasks with simple gestures But: gestures can appear in standard gaze, thus could be involuntarily performed But: what is input and what is NON-input? (compare to: pause mouse) Drewes, H., Schmidt, A. Interacting with the computer using gaze gestures. In: INTERACT

35 Towards Implantable computing Symbiosis (?) between human and computer Direct interfacing of electronics with the body Stelarc Body Ping Design Vision of a phone implanted in a tooth - designed by Jimmy Loizeau and James Auger 37

36 Lessons Learned from History Technology drives new user interface concepts and interaction metaphors New user interfaces create new applications Designs and user interface concepts constantly evolve The first to come out with a new user interface is not necessarily the most successful; e.g. Tablet Computers: first one: DynaBook (1969) PARC: not successful Microsoft: Apple: not successful successful (Newton 1987, ipad 2010!) Palm: successful last visited

37 Interactive Exploration of HCI (former student project) last visited last visited

38 Development from an idea to an infrastructure How does the development look for current interactive technologies? Idea Killer App Infrastructure Electric_Current_Line_in_Kukherd_District.jpg?uselang=de 40

39 Current Situation of Computing and Interaction Computing & interaction paradigms are (still mostly) designed for PCs (desktop + mouse, keyboard & monitor) WIMP interaction (windows, icons, mouse, pointer) (term coined by Merzouga Wilberts (1980) at XEROX PARC) Direct manipulation interface Characteristics: Fixed configurations User interface with mouse and keyboard Output with printer, monitor(s) Dedicated network services Fixed network addresses and locations... l.png

40 Ubiquitous Computing - Computing changes Ubiquitous computing (UbiComp): A completely new paradigm for interaction Heterogeneous set of devices: Visible & Invisible computers Smart Phones, Personal digital assistants (PDAs) Personal devices (e.g. wearables, jewellery,..) Everyday objects w/ embedded computing, furniture,... Environments, buildings Different operating systems with different application areas: Embedded OS Desktop OS Distributed Systems / Clouds Different network devices and services no longer fixed, but ad-hoc Bluetooth, ZigBee, WLAN, 3G, 4G,... Location-based services, video/media services, data synchronization,... 42

41 Ubiquitous Computing - Computing changes Different input and output possibilities 3D I/O, e.g.: Gestures in free space Auto-stereoscopic displays Interaction with walls, windows (real ones!), floors implicit & explicit interaction (Pico and large-scale) projection Display sizes from LED to wall-sized Haptic device I/O Ultrasonic + bone sound

42 Computing Models Change One-to-one model (one person, one computer) is not applicable anymore Many-to-many model (many persons, many computer) Interaction changes from WIMP/GUI/explicit to Implicit Invisible Through sensing natural interactions/modalities: speech, gesture, presence,... à wide range of sensors & sensing systems necessary à in devices & environments Application scenarios (not comprehensive): Rooms (meeting rooms, classrooms,...) Vehicles and cars Environments (schools, hospitals, museums, homes,...) Everyday objects Every time, every where 44

44 Why care about User-centered Design? Usability Aspect A carefully designed system can be used more efficiently (intuitive, easy to understand, features are at the right place,...) Comfort Aspect Users should feel at home Business Aspect Many products of similar functionality, usability is distinction factor Likeability Aspect Role of emotion: attractive things work better Don Norman: Emotion and Design: Attractive things work better. In Interactions Magazine, ix (4),

45 A model for an user-centred design life cycle Deployment Phase Implementation Phase User Analysis Phase Design Phase 48

46 49

47 Software Development Cycles Goals Segmentation of overall activity into smaller portions of work Identification of phases and individual tasks Help for milestone definition Various existing process models Analysis Common phases in all models: Analysis Design Implementation Validation Evolution Design Implementation Test Classic Waterfall Model, according to Royce (1970) Maintenance 50

48 Other process models Spiral Model Prototyping Model Determine Objectives Design Implementation Demonstrate Develop Refine Analysis Test Test Prototypes/ Product Releases Implement 51

49 Analysis Phase Requirement specification Complete and detailed description for the application Important: be specific Here: specified by team project descriptions Derive features from user goals First figure out what users really want to do Then define necessary features Attention: too many features are not good! Choose carefully which to include! Source: It is sometimes not easy to find out what the customers really want! 52

50 Source:

51 Design Phase From the requirements specification to the app Steps Step 1: Define the functionality Step 2: Organize the functionality in screens Step 3: Plan the navigation Step 4: Design the individual screens Let us look at the individual steps in detail now. 54

52 Step 1: Define the functionality Questions to start with: What is the main task of your application? What sub-tasks are required to perform the main task? Which other features should be contained in the app? What types of information the app is dealing with? In what way does the user interact with this information? Create an entity-relationship (ER) diagram Source: developer.android.com 55

53 Step 2: Plan the screens Based on the ER model, which screens does the application need? Begin with a list, then plan the relation between screens Source: developer.android.com 56

54 Consider alternative layouts Modify screen layouts based on the device and orientation Larger screens (tablets) can show more information (e.g. element preview for list items, more or larger images, ) Tablets can use multi-fragment layouts (e.g. a navigation pane and a detail pane) Consider also different layouts for portrait and landscape mode Stretch elements for best layout in each orientation Expand and collapse elements Show or hide elements Use different placements (bar on top/bottom vs. at side) 57

55 Step 3: Plan the navigation between screens Descendant navigation: down in hierarchy from parent to child screen Ancestral navigation: up in hierarchy Back button Action bar (back/home) Explicit home button Lateral navigation: navigate between sibling screens Section siblings: different parts of functionality Tabs Tick marks Labels Collection siblings: individual elements of a collection Swipe Views Buttons Temporal navigation: Activity stack/back button 58

56 Step 4: Design the individual screens Conceive layouts for the individual activities Which UI elements do you need? Think of intuitiveness and consistency Create prototypes of the screen layouts Paper prototypes Wireframe prototypes See tutorial on prototyping Which development patterns can be applied in the UI? (see later) 60

57 Step 5 (and 6): Implement and test the application Use iterative design Start with the implementation of the basic functionality and layout Refine with each iteration In each iteration, test the application Do newly implemented features provide the intended result? In any situation? Do new features break existing features? Is the app fast and responsive? (client/server communication, reading large data, doing long calculations -> AsyncTask) Critical tester: try to make it crash! Exception handling everywhere they could occur? Frequent error sources: data parsing, service availability (internet/ location provider/ ), differences between devices 61

58 Iterative Design Example: Collaborative cookbook application Very simple functionality: Users can contribute recipes with images List view: navigate through recipes, sorted by upload time Detail view: see ingredients and cooking instructions Image material courtesy of Android Design in Action YouTube channel 62

59 Image material courtesy of Android Design in Action YouTube channel 63

60 Use the ActionBar for consistency with Android stock applications and design guidelines Usability: direct access to important functions android:theme = Theme.Holo.Light.DarkActionBar android:targetsdkversion = 17 Image material courtesy of Android Design in Action YouTube channel 64

61 Branding your application increases recognition Manually modify style or use Android Action Bar Style Generator to generate resources automatically actionbarstylegenerator Image material courtesy of Android Design in Action YouTube channel 65

62 Use margins and spacing for better readability. Touchable UI components are generally laid out along 48dp units. grids.html Image material courtesy of Android Design in Action YouTube channel 66

63 Adjust images in list view for less visual clutter android:scaletype = centercrop Image material courtesy of Android Design in Action YouTube channel 67

64 Vary fonts for a unique look and feel Readability is important! android:fontfamily = sans- serif- condensed (or light) android:linespacingmultiplier Image material courtesy of Android Design in Action YouTube channel 68

65 Swipe between details views for faster navigation using ViewPager Can be used beginning from API level 4 with the Support Library Image material courtesy of Android Design in Action YouTube channel 69

68 Use fragments to make better use of the available space Image material courtesy of Android Design in Action YouTube channel 72

69 Optimize metrics for larger screen size res/values/dimensions.xml (Smartphone) res/values- sw600dp/dimensions.xml (7 tablet) res/values- sw720dp/dimensions.xml (10 tablet) Image material courtesy of Android Design in Action YouTube channel 73

70 Iterative design: what did we learn? Step by step Start with implementing the functionality and basic UI, then successively improve it Don t try to be perfect from the beginning Get a look for the details Visual appearance (spacing, fonts, layout) is important for likeability (think of Golden Ratio), visual aesthetics Likeability and usability often go together! There s always something you can improve further Feedback Get feedback as often as possible (team mates, other teams, friends ) Some issues can already be resolved before implementation 74

71 Motivation: What is a user-centered approach? Real users and their goals (not just technology or functionality) should be the driving force behind development of a product. Three principles that lead to a useful and easy to use of computer systems (in the context of interactive systems!) (Gould and Lewis, 1985) Early focus on users and tasks Empirical measurement Iterative design To Do as homework, reading: The Five Most Influential Papers In Usability esp.: Designing for usability: key principles and what designers think. Gould, J. D. and Lewis, C. (1985) Heuristic evaluation of user interfaces. Nielsen, J., and Molich, R. (1990) Comparative Evaluation of Usability Tests. Molich et al. (1998) Interaction Design, Chap. 9, book available online: last visited Gould, J. D., Lewis, C. (1985). Designing for usability: Key principles and what designers think. Comm. of the ACM, 28, 3,

72 Gould s Principle 1: Early focus on users and tasks Users tasks and goals are the driving force behind the development (and not on the data that is inputted/outputted only!) Users behavior and context of use are studied and the system is designed to support them (e.g. workplace analysis, interaction context) Users characteristics are captured and designed for (backgrounds, knowledge, diversity, age, social context, ) Users are consulted throughout development from earliest phases to the latest and their input is seriously taken into account (active involvement, stakeholder participation) All design decisions are taken within the context of the users, their work, and their environment (not w.r.t. costs, ease of implementation, ) Interaction Design, Chap. 9, book available online: last visited

73 Gould, s Principle 2: Empirical measurement Specific usability and user experience goals should be identified, clearly documented, and agreed at the beginning of the project. Goals have to be defined in a way that measuring the goal achievement is possible. The product can be empirically evaluated at regular stages as it is developed, to ensure that the final product is as intended. Interaction Design, Chap. 9, book available online: last visited

74 Gould s Principle 3: Iterative design Iteration allows for the refinement of designs based on feedback During the design process different insights into what is needed, what will help, and what is feasible will emerge. Innovation rarely emerges as a whole and ready to go but in steps and based on feedback and iteration Iteration is inevitable because designers never get the solution right the first time (nor do the developers the functionality) Interaction Design, Chap. 9, book available online: last visited

75 4 basic activities of interaction design Identifying needs and establishing requirements for the user experience Developing alternative designs that meet those requirements Building interactive versions of the designs Evaluating what is being built throughout the process and the user experience it offers basis for a simple interaction design life cycle model 79

76 A simple interaction design lifecycle model Identifiy needs/ establish requirements (Re-) Design Evaluate Build an interactive version Looks simple - but it not trivial to apply/achieve! Final Product 80

77 Design and Development Process Separation between interaction design and technical design For interactive applications, a separation into a two stage process is often advisable 1st Iterative interaction design (incl.: what is physical, what is digital?) Concept Interaction analysis Prototypes Evaluation Stable and tested design 2nd technical realization Technical analysis Technical specification (e.g. architecture, platform) Implementation Evaluation and Quality management 81

78 An Example Development Process Logical User-Centered Interactive Development (LUCID) Methodology A key principle of The LUCID Framework is that products should be designed to offer users the five E s: Effectiveness Efficiency Engagement Error tolerance Ease of learning LUCID is structured as a series of six stages: Example: LUCID as an example methodology for user-centered design (UCD) Logical User Centered Interactive development (LUCID) Methodology lucid/index.html and last visited

79 Logical User Centered Interactive Development (LUCID) Stage 1: Envision Develop UI Roadmap which defines the product concept, rationale, constraints and design objectives. Stage 2: Analyze Analyze the user needs and develop requirements. Stage 3: Design Create a design concept and implement a key screen prototype. Stage 4: Refine Test the prototype for design problems and iteratively refine and expand the design. Stage 5: Implement Support implementation of the product making late stage design changes where required. Develop user support components. Stage 6: Support Provide roll-out support as the product is deployed and gather data for next version. product definition and development product definition and development Logical User Centered Interactive development (LUCID) Methodology and last visited

80 yellow boxes: include usability, not only design! Logical User Centered Interactive development Methodology (LUCID) last visited

81 The LUCID Framework: Product Development Process Logical User Centered Interactive development Methodology (LUCID) last visited

82 The LUCID Framework: Product Development Process yellow boxes: include usability, not only design! Logical User Centered Interactive development Methodology (LUCID) last visited

83 The value of prototyping Creating prototypes is important to get early feedback from the project team (prototypes help to communicate) from potential users Different types of prototypes Low-fidelity prototypes (e.g. paper prototypes, sketches) Hi-fidelity prototypes (e.g. implemented and semi-functional UI, could look like the real product ) Fidelity is referring to detail Tools & Techniques (remember the lecture before & the tutorial) Sketches & Storyboards Paper prototyping Using GUI-builders to prototype Limited functionality simulations Wizard of Oz 87

84 Challenges of User Centered Design Users may be wrong (even if that should be a rare answer ;), they might just see their part of the task but not more ) Users may be resistant to change (in fact, they frequently are afraid of things that are different ) Users may expect disadvantages (e.g. being replaced by software, in fear of higher work load, ) Be aware: You are expected to create an optimal system (in all respects) with regards to the goals specified This is unfortunately NOT necessarily the system users would like to have (e.g. trade-off between employers and employees) 88

85 The ISO human-centered design lifecycle model The ISO is an international standard providing guidance on human centered-design activities throughout the lifecycle of an interactive product. Addresses planning and management, does not cover specific design approaches 4 principles: Active involvement of users (rapid prototyping, focus groups, evaluation, ) Appropriate allocation of function between users and technology not just dump input tasks! remember: joint performance of humans and computers! Iteration of design solutions Multi-disciplinary design (different roles in the team) 89

86 The ISO human-centered design lifecycle model Identify need for human-centered design Understand and specify the context of use specifies 4 human-centered design activities as being central to a system development process Evaluate designs against requirements System satisfies specified user and organizational requirements Specify the user and organizational requirements Product design solutions 90

87 Other Frameworks/Approaches that include Usability V-Model XT (accounts explicitly for usability) User-Centred Software Design (USCD) methodology Agile Development methods PACT framework (people, activities, contexts, tasks) Examples of norms: ISO/AWI 23973: Software ergonomics for World Wide Web user interfaces DIN EN ISO 13407: Human-centred design processes for interactive systems DIN EN ISO 14915: Software ergonomics for multimedia user interfaces 91

89 Trends in Computing Selected trends that influence under what conditions people interact and are willing to interact show the impact of changing contexts (e.g. availability of hardware) set the scene for us as basis should not be ignored when developing useable interactive products 93

90 Trends (1) - mobile communication is ubiquitous Terminals for mobile communication have advanced significantly over recent years Infrastructure (power, communication, ) is ubiquitously deployed Interesting developments happen beyond the classical handsets (when thinking of electricity: it is not the advances in light bulbs that changed the world) How many handsets will a user have in 5 years? à a guess: 2-6 (some mobile phones, car phone, ) How many communicating appliances and devices will users have in 10 years? à a guess: 20+ (security system, TV, front door, dog collar, wrist watch, camera, headset, coffee machine, alarm clock, ) 94

91 Trends (2) - Computer-Controlled (Electro-)Mechanical UIs Mechanical and electro-mechanical systems become computer controlled. User interfaces for mechanical and electro-mechanical systems (and more novel ones) have a tradition of being tangible. Many design restrictions due to mechanics are gone novel interfaces (for the better or the worse) are possible and emerge. Sensing of actions and reactions from users becomes an interface option. Examples: automotive, industrial machinery, tools, buildings, music instruments (e.g. automated mixer), 95

92 Question... Do you read manuals (always when you buy a new product)? Did you read a manual for your computer?... your mobile phone?... your digital camera? your tablet pc?... your VCR?... your television? What does that imply on the design & development process of interactive technologies? 96

93 Trends (3) - Declining willingness for training An average person acts today as driver, telephonist, photographer, film-maker, and type setter without much training (many tasks with just one device the phone). In a fast paced job market, training to operate a system is a significant obstacle (and cost factor) for the introduction of new systems. Dangerous actions should be prohibited in the first place by the controls available in the user interface not by a warning in the manual. User interfaces should be intuitive and natural interaction with minimal learning should be supported. 97

94 Trends (4) - User s abilities don t change much Abilities of un-augmented users in general do not change a lot over time, e.g. ability to cope with cognitive load willingness to cope with stress time one can concentrate on a particular problem abilities Abilities between individual users vary a lot long term, e.g. physical and intellectual abilities short term, e.g. effect of stress or fatigue Abilities of one individual user change over time (e.g. getting old) time Human in the loop Interactive systems for augmenting the human intellect as alternative to automation. 98

95 Trends (5) - Technology becomes widely available Technologies that may be today specialist devices become common in a few years Technologies that are shared now (because they are so expensive) may become personal technologies Technologies that are expensive at one point are not even considered as additional cost in the future, e.g. Video camera connected to a computer Biometric authentication Book printing on demand Eye gaze tracking 3D scanning and printing Integrated production systems 99

96 Trends (6) - Moore s Law "The number of transistors per chip that yields the minimum cost per transistor has increased at a rate of roughly a factor of two per year. Almost every measure of the capabilities of digital electronic devices is linked to Moore's Law: Computing performance Hard disk / RAM storage cost Network capacity Does not apply to power provision, e.g. batteries Not all aspects of computing technology develop in capacities and speed according to Moore's Law (e.g. 45% increase in processor transistors have translated to roughly only 10-20% increase in processing power or speed) 100

97 Trends (7) - Computing, Storage and Communication are not the limit (anymore) For personal computing (not supercomputing), there are only few technical limitations left Processing power is available desktop machines run with minimal processing power Massive amounts of storage are available Phones with 16GB disk Record everything you ever said on a HD Have all movies ever produced in a single device Bandwidth (wireless and wired) is available While you tie your shoe laces you can cache all the latest news papers While you wait for the bus you can transfer a complete movie 103

98 Trends (8) - functionality is non-discriminative Feature set and functionality is similar between products (non-discriminative) Quality of the functional aspects vary little (e.g. same decoder chip, same display-panel) Design, experience, user interface became important factors to have a different product? (remember: Who knows why the VCR is an evil nemesis to any HCI engineer?) 104

99 Trends (9) - The process/task is the key advancing technology is not sufficient innovation happens when entire processes are considered (not just parts of them) 105

100 Trends (10) - education changes values in education change ( I have always been bad at maths can now be said with some pride, but could not have been 10 years ago) experiences people have are changing (soon: no non-computer users anymore) learning and training is not a constant, they change over time (that is, while we age) 106

101 Trends (11) - Perception of Privacy changes our personal information will likely become a commodity that we trade 107

102 Trends (12) Big data and the quantified self ZDF log in (March 11, 2014) Health insurance coverage: Rates are person dependent, e.g., based on behavior of food intake, sports/exercises Weight loss: study with 1500 overweight individuals (half were left individual, half were connected via a social network) The connected individuals were 3 times more sucessful (faster loss of weight, sustainable) Public available health profile (insurance, employer, social network, etc.) Social sustainability? Lifestyle disease (alcohol, diabetis II) vs. diseases through no own fault (e.g., cancer, diabetis I) 108

103 Trends (12) Big data and the quantified self ZDF log in (March 11, 2014) 109

104 The interaction is the key! Anytime and everywhere Design restrictions are gone Sensing and actuators are part of the UI Must be obvious to use (affordances) Processing, storage and communication without limits Current cost of technology is not an issue The overall process is crucial Acquired knowledge is the basis The interface between the user and the machine or the information is most critical to create pleasant, effective and efficient systems. 110