WEBVTT - TechStuff Gets in Touch with Touch Screens

0:00:04.240 --> 0:00:07.240
<v Speaker 1>Welcome to tech Stuff, a production of I Heart Radios,

0:00:07.320 --> 0:00:13.880
<v Speaker 1>How Stuff Works. Hey there, and welcome to tech Stuff.

0:00:14.000 --> 0:00:17.079
<v Speaker 1>I'm your host, Jonathan Strickland. I'm an executive producer with

0:00:17.120 --> 0:00:19.279
<v Speaker 1>How Stuff Works and I Heart Radio and I love

0:00:19.320 --> 0:00:23.520
<v Speaker 1>all things tech and listener Robert Casey pinned me on

0:00:23.560 --> 0:00:26.640
<v Speaker 1>Twitter with a request that I do an episode about

0:00:26.720 --> 0:00:31.639
<v Speaker 1>touch screens and stylus is or STYLI Now. My original

0:00:31.720 --> 0:00:35.600
<v Speaker 1>co host, Chris Palette, and I covered this topic on

0:00:35.720 --> 0:00:39.680
<v Speaker 1>an ancient episode of tech Stuff that published all the

0:00:39.680 --> 0:00:45.360
<v Speaker 1>way back on October nineteen, two thousand nine, Holy Cow,

0:00:45.880 --> 0:00:49.159
<v Speaker 1>ten years ago. But I think it's past time to

0:00:49.320 --> 0:00:53.000
<v Speaker 1>revisit this topic and give it the full modern day

0:00:53.080 --> 0:00:56.560
<v Speaker 1>tech stuff treatment. Now, there are a few interesting things

0:00:56.680 --> 0:00:59.319
<v Speaker 1>about touch screens in general that I'd like to get

0:00:59.360 --> 0:01:03.360
<v Speaker 1>all the way. One is that it's pretty ubiquitous today.

0:01:03.520 --> 0:01:06.400
<v Speaker 1>It's it's it's a user interface that you find everywhere

0:01:06.440 --> 0:01:11.200
<v Speaker 1>for everything from mobile or mobile devices to lots of

0:01:11.240 --> 0:01:15.720
<v Speaker 1>different laptop and desktop displays. Now, granted, I've never owned

0:01:15.959 --> 0:01:19.800
<v Speaker 1>a laptop or desktop display that had touch screen technology

0:01:19.800 --> 0:01:23.080
<v Speaker 1>incorporated in it, largely because I didn't see a lot

0:01:23.160 --> 0:01:25.760
<v Speaker 1>of use in that Based on how I tend to

0:01:25.800 --> 0:01:28.039
<v Speaker 1>interact with computers, Not to say that there's no use

0:01:28.080 --> 0:01:30.360
<v Speaker 1>for it, just that the way I use computers, it

0:01:30.360 --> 0:01:32.920
<v Speaker 1>wouldn't make sense for me. Usually I don't have the

0:01:32.959 --> 0:01:35.720
<v Speaker 1>display so close that reaching out and touching it would

0:01:35.720 --> 0:01:38.720
<v Speaker 1>be terribly easy or comfortable, And most of what I

0:01:38.800 --> 0:01:42.880
<v Speaker 1>use computers for requires lots of typing, which isn't great

0:01:42.959 --> 0:01:46.480
<v Speaker 1>on most touch screen implementations. I guess you could pare

0:01:46.520 --> 0:01:49.320
<v Speaker 1>it with voice recognition and get more use out of it,

0:01:49.800 --> 0:01:52.080
<v Speaker 1>But I am curious if any of you guys use

0:01:52.160 --> 0:01:56.559
<v Speaker 1>computers with touch displays and what do you use them for?

0:01:56.800 --> 0:01:59.400
<v Speaker 1>As I'm sure there are plenty of use cases where

0:01:59.440 --> 0:02:03.400
<v Speaker 1>it is incredibly handy so to speak. Oh and there

0:02:03.400 --> 0:02:07.000
<v Speaker 1>will probably be a lot of unintentional puns in this episode,

0:02:07.440 --> 0:02:11.480
<v Speaker 1>and maybe a couple of intended ones will be but

0:02:11.639 --> 0:02:15.840
<v Speaker 1>a touch away, so to speak. Anyway, touch screens are everywhere,

0:02:16.120 --> 0:02:19.680
<v Speaker 1>but their history is fairly recent. Another thing I find

0:02:19.720 --> 0:02:22.040
<v Speaker 1>really interesting about them is that there are a lot

0:02:22.040 --> 0:02:24.680
<v Speaker 1>of different ways to go about it, and the end

0:02:24.760 --> 0:02:27.960
<v Speaker 1>result aims to be the same, but there are several

0:02:28.000 --> 0:02:32.120
<v Speaker 1>approaches to implementing touch screens, and each implementation has its

0:02:32.160 --> 0:02:36.080
<v Speaker 1>advantages and disadvantages, so we'll cover those in this episode.

0:02:36.520 --> 0:02:39.880
<v Speaker 1>And yet, one more thing I think is interesting is

0:02:39.919 --> 0:02:43.359
<v Speaker 1>really just how innovative touch screen devices have been. If

0:02:43.360 --> 0:02:46.600
<v Speaker 1>you look back at the science fiction films and TV

0:02:46.760 --> 0:02:50.200
<v Speaker 1>series from the nineteen fifties and even into the nineteen sixties,

0:02:50.360 --> 0:02:54.320
<v Speaker 1>when touch screen technology was first being described, you'll rarely

0:02:54.360 --> 0:02:58.000
<v Speaker 1>see examples of that idea. Touch Screens were such a

0:02:58.080 --> 0:03:03.320
<v Speaker 1>leap forward that spec lative fiction writers weren't really imagining

0:03:03.360 --> 0:03:06.880
<v Speaker 1>it as a user interface. That's why in series like

0:03:06.960 --> 0:03:10.960
<v Speaker 1>Star Trek, the original series, you'll see characters interacting with

0:03:11.080 --> 0:03:16.000
<v Speaker 1>physical dials and knobs and levers that are the controls

0:03:16.040 --> 0:03:19.400
<v Speaker 1>of a twenty third century spaceship. You know, you look

0:03:19.400 --> 0:03:22.079
<v Speaker 1>at those controls today and you think, oh, that looks antiquated.

0:03:22.680 --> 0:03:24.959
<v Speaker 1>Unlike a lot of technologies we've seen over the last

0:03:25.000 --> 0:03:29.600
<v Speaker 1>several decades, touch screens weren't heavily predicted in fiction. And

0:03:29.639 --> 0:03:31.640
<v Speaker 1>I think I'll have to do an episode dedicated to

0:03:31.760 --> 0:03:34.840
<v Speaker 1>tech that writers described years before it became a reality.

0:03:34.920 --> 0:03:37.600
<v Speaker 1>That's an interesting subject of its own, Like the types

0:03:37.640 --> 0:03:41.280
<v Speaker 1>of technology that science fiction writers predicted before it happened.

0:03:41.600 --> 0:03:44.720
<v Speaker 1>You know, things like you know, geosynchronous satellites, but that's

0:03:44.720 --> 0:03:49.120
<v Speaker 1>for another episode. Okay, so we're ready for our history lesson,

0:03:49.200 --> 0:03:51.920
<v Speaker 1>which is you longtime listeners know is sort of a

0:03:51.960 --> 0:03:55.320
<v Speaker 1>requirement in every tech stuff episode. Before I dive in,

0:03:55.400 --> 0:03:58.040
<v Speaker 1>I want to give a shout out to Florence Ion's

0:03:58.200 --> 0:04:02.000
<v Speaker 1>article from Touch to Plays to the Surface, A brief

0:04:02.040 --> 0:04:05.840
<v Speaker 1>history of touch screen technology in Ours Technica. It's a

0:04:05.840 --> 0:04:09.400
<v Speaker 1>fantastic summary of the evolution of the technology, and if

0:04:09.440 --> 0:04:12.080
<v Speaker 1>you want to learn more about the history of touch screens,

0:04:12.080 --> 0:04:14.160
<v Speaker 1>I urge you to seek it out. It was not

0:04:14.280 --> 0:04:17.559
<v Speaker 1>the only source I used when getting all the history stuff,

0:04:17.600 --> 0:04:21.680
<v Speaker 1>but it was a great resource. Also. I normally break

0:04:21.760 --> 0:04:24.760
<v Speaker 1>up the history and the description of how technology works

0:04:24.800 --> 0:04:28.479
<v Speaker 1>into different parts of episodes typically, but in this case,

0:04:28.920 --> 0:04:32.080
<v Speaker 1>I think it works better to describe how each version

0:04:32.160 --> 0:04:35.120
<v Speaker 1>of the technology works as we get to them, and

0:04:35.200 --> 0:04:37.400
<v Speaker 1>as a peak behind the curtain. I came to that

0:04:37.480 --> 0:04:39.880
<v Speaker 1>decision after I was about a third of the way

0:04:39.960 --> 0:04:43.400
<v Speaker 1>done typing out all of my notes, so I actually

0:04:43.440 --> 0:04:45.719
<v Speaker 1>went back and revised my notes quite a bit and

0:04:45.800 --> 0:04:48.080
<v Speaker 1>rearranged things because I did not like the way the

0:04:48.120 --> 0:04:52.719
<v Speaker 1>episode flowed in its original form. So all that being said,

0:04:53.000 --> 0:04:55.800
<v Speaker 1>where did the idea for the touch screen interface come

0:04:55.880 --> 0:04:59.599
<v Speaker 1>from well before there were touch screens that could interpret

0:04:59.680 --> 0:05:02.919
<v Speaker 1>the touch of a finger or stylus, there was the

0:05:03.040 --> 0:05:05.520
<v Speaker 1>light pen. The first light pen was part of a

0:05:05.560 --> 0:05:09.279
<v Speaker 1>system that IBM design called Whirlwind, which the company built

0:05:09.279 --> 0:05:12.919
<v Speaker 1>for Norad. But the way touch screens work is different

0:05:13.080 --> 0:05:16.120
<v Speaker 1>from the way light pens work. With touch screens, the

0:05:16.160 --> 0:05:19.800
<v Speaker 1>technology for detecting a point of contact is generally built

0:05:20.000 --> 0:05:24.240
<v Speaker 1>into or behind or sometimes in front of the screen itself.

0:05:24.920 --> 0:05:27.960
<v Speaker 1>With a light pen, the detector is actually in the

0:05:28.040 --> 0:05:31.560
<v Speaker 1>pen side of the interface, not on the screen side,

0:05:31.839 --> 0:05:34.760
<v Speaker 1>so the screen is a nert. It's the pen that's active.

0:05:35.279 --> 0:05:38.840
<v Speaker 1>Light pens have a photoelectric cell built into them, in

0:05:38.839 --> 0:05:43.440
<v Speaker 1>other words, a sensor that detects light, and typically light

0:05:43.480 --> 0:05:46.839
<v Speaker 1>pen is tethered to the computer system it's connected to.

0:05:46.960 --> 0:05:50.400
<v Speaker 1>It's actually physically connected with a cable. Holding a light

0:05:50.440 --> 0:05:53.120
<v Speaker 1>pen up to a screen would allow the light pen

0:05:53.240 --> 0:05:57.880
<v Speaker 1>to register when the monitors electron beams scanned across that point,

0:05:58.440 --> 0:06:01.080
<v Speaker 1>because monitors in those days were based off the old

0:06:01.160 --> 0:06:06.279
<v Speaker 1>cathode ray tube technology, which uses an electron gun that

0:06:06.480 --> 0:06:10.599
<v Speaker 1>shoots a beam of electrons in row after row after row,

0:06:10.839 --> 0:06:14.200
<v Speaker 1>so it goes it scans across the screen and then

0:06:14.320 --> 0:06:17.880
<v Speaker 1>down the screen. So it goes one line across, then

0:06:17.960 --> 0:06:21.279
<v Speaker 1>moves down the line, goes across, moves down the line, etcetera, etcetera.

0:06:21.960 --> 0:06:25.640
<v Speaker 1>And these electrons then hit against phost four points on

0:06:25.680 --> 0:06:28.640
<v Speaker 1>the back side of the screen and it generates light. Now,

0:06:28.680 --> 0:06:31.919
<v Speaker 1>because the light pins were tethered to the computer system,

0:06:31.960 --> 0:06:35.440
<v Speaker 1>the computer would pick up precisely where on the screen

0:06:35.480 --> 0:06:38.360
<v Speaker 1>the light pin was sitting, and it did this by

0:06:38.400 --> 0:06:42.640
<v Speaker 1>cross referencing the time of contact with the position of

0:06:42.680 --> 0:06:46.080
<v Speaker 1>the electron beam at that moment. So the light pin

0:06:46.120 --> 0:06:50.360
<v Speaker 1>would detect this electron beam, and that message would be

0:06:50.400 --> 0:06:52.640
<v Speaker 1>sent to the computer, and the computer knew where the

0:06:52.680 --> 0:06:56.160
<v Speaker 1>electron beam was at that precise instant, and that way

0:06:56.200 --> 0:06:58.760
<v Speaker 1>it knew where the point of contact was. Now, this

0:06:58.839 --> 0:07:01.960
<v Speaker 1>is largely an outlier of the touchscreen topic, but it's

0:07:02.000 --> 0:07:04.720
<v Speaker 1>kind of a predecessor, so I thought it would include it. Now,

0:07:04.839 --> 0:07:07.960
<v Speaker 1>unlike a lot of other technologies, which tend to get

0:07:08.000 --> 0:07:10.920
<v Speaker 1>pretty muddy when you start asking questions like where did

0:07:10.920 --> 0:07:14.480
<v Speaker 1>this idea come from? We can be reasonably certain that

0:07:14.760 --> 0:07:18.760
<v Speaker 1>Eric Arthur Johnson or E. A. Johnson proposed the first

0:07:18.880 --> 0:07:24.080
<v Speaker 1>technological solution to creating a touch screen computer interface. Johnson

0:07:24.120 --> 0:07:26.920
<v Speaker 1>was an engineer at what was at that point the

0:07:27.160 --> 0:07:32.000
<v Speaker 1>Royal Radar Establishment, which was a research facility in Malvern, England,

0:07:32.320 --> 0:07:35.760
<v Speaker 1>and as the name suggests, this facility was chiefly focused

0:07:35.760 --> 0:07:39.560
<v Speaker 1>on developing new radar technologies, and it wasn't It was

0:07:39.600 --> 0:07:43.000
<v Speaker 1>operating as a research organization that worked closely with British

0:07:43.120 --> 0:07:46.880
<v Speaker 1>Armed Forces. It would later become the Defense Evaluation and

0:07:46.960 --> 0:07:51.000
<v Speaker 1>Research Agency after merging with a few other organizations, and

0:07:51.120 --> 0:07:54.880
<v Speaker 1>later still it would become part of a defense contractor

0:07:54.920 --> 0:07:59.880
<v Speaker 1>in England called Kinetic spelled with a que. Johnson was

0:08:00.120 --> 0:08:04.720
<v Speaker 1>working on improving the user interface for air traffic control staff.

0:08:04.760 --> 0:08:08.200
<v Speaker 1>He wrote an article and had the title touch Display

0:08:08.360 --> 0:08:12.480
<v Speaker 1>a novel input output device for computers. It was published

0:08:12.480 --> 0:08:16.760
<v Speaker 1>in the journal Electronics Letters on October uh in nineteen.

0:08:17.680 --> 0:08:20.640
<v Speaker 1>I said on October, I should say in October nine,

0:08:21.360 --> 0:08:24.080
<v Speaker 1>because I don't have the precise date of when in

0:08:24.120 --> 0:08:26.600
<v Speaker 1>October it came out. But in nineteen sixty seven he

0:08:26.640 --> 0:08:30.760
<v Speaker 1>published a follow up piece titled touch Displays a Programmed

0:08:30.840 --> 0:08:34.880
<v Speaker 1>Man Machine Interface that further developed this concept and fleshed

0:08:34.920 --> 0:08:37.560
<v Speaker 1>it out, and he was describing what would become the

0:08:37.600 --> 0:08:42.079
<v Speaker 1>capacitive touch screen interface. And I also find this interesting

0:08:42.400 --> 0:08:45.840
<v Speaker 1>because for many years, it seemed the majority of consumer

0:08:45.880 --> 0:08:50.080
<v Speaker 1>products that had touch screens used an alternative to the

0:08:50.120 --> 0:08:54.480
<v Speaker 1>capacity of approach, known as resistive touch screens, and those

0:08:54.520 --> 0:08:57.679
<v Speaker 1>two technologies make up the majority of the touch screens

0:08:57.760 --> 0:09:01.440
<v Speaker 1>we tend to encounter. I'll explain the differences between them

0:09:01.559 --> 0:09:05.080
<v Speaker 1>when we get to each, but first before I get

0:09:05.120 --> 0:09:08.480
<v Speaker 1>into the differences, what our capacity of touch screens and

0:09:08.520 --> 0:09:12.560
<v Speaker 1>how do they register touch? Well, they only register a

0:09:12.640 --> 0:09:17.839
<v Speaker 1>touch if the substance touching the screen can hold an

0:09:17.840 --> 0:09:21.959
<v Speaker 1>electrical charge, So stuff like our skin. Our skin can

0:09:22.000 --> 0:09:25.360
<v Speaker 1>hold an electrical charge. It's electrically conductive. So if you've

0:09:25.400 --> 0:09:29.400
<v Speaker 1>ever used a touch screen while wearing gloves and nothing happened,

0:09:29.800 --> 0:09:33.560
<v Speaker 1>it's probably because the capacity of touch screen was not

0:09:33.760 --> 0:09:37.640
<v Speaker 1>able to detect any sort of electrical connection. The gloves

0:09:37.640 --> 0:09:42.480
<v Speaker 1>were acting like insulators. They inhibit electrical charge. That's why

0:09:42.520 --> 0:09:44.520
<v Speaker 1>there are companies out there that sell gloves that have

0:09:44.720 --> 0:09:48.679
<v Speaker 1>conductive wire or conductive pads at the fingertips. And it's

0:09:48.720 --> 0:09:51.840
<v Speaker 1>also why you can't use something like an inert plastic

0:09:51.960 --> 0:09:55.560
<v Speaker 1>stylus on a capacity of screen. You can use a

0:09:55.640 --> 0:10:00.720
<v Speaker 1>stylus that has a conductive surface at the hip, that

0:10:00.760 --> 0:10:05.000
<v Speaker 1>would work. But if it's just a plastic stick, for example,

0:10:05.320 --> 0:10:08.439
<v Speaker 1>it wouldn't activate the screen. But you could use something

0:10:08.440 --> 0:10:11.920
<v Speaker 1>else like um, you know, like a hot dog, which

0:10:11.960 --> 0:10:14.120
<v Speaker 1>is I understand it used to be a thing in

0:10:14.160 --> 0:10:17.839
<v Speaker 1>South Korea. People would use hot dogs to activate their

0:10:17.840 --> 0:10:20.120
<v Speaker 1>capacitive touch screens when it was too cold for them

0:10:20.160 --> 0:10:23.360
<v Speaker 1>to not wear gloves, which tells me you could probably

0:10:23.400 --> 0:10:27.200
<v Speaker 1>make a killing in soul by selling screen cleaners dedicated

0:10:27.200 --> 0:10:32.320
<v Speaker 1>to eradicating weener grease from your screens. But how do

0:10:32.559 --> 0:10:36.240
<v Speaker 1>the capacity of screens actually detect touch. There's a couple

0:10:36.280 --> 0:10:39.360
<v Speaker 1>of different approaches, but the general idea is to create

0:10:39.360 --> 0:10:43.240
<v Speaker 1>a surface that holds an electrical charge, and in many

0:10:43.320 --> 0:10:46.640
<v Speaker 1>implementations this is done with a grid of very fine

0:10:46.880 --> 0:10:51.000
<v Speaker 1>conductive wires running in rows and columns on an x

0:10:51.160 --> 0:10:55.360
<v Speaker 1>y grid. In other words, so like a net, sensors

0:10:55.559 --> 0:10:58.640
<v Speaker 1>pick up changes in this electrical charge when they happen.

0:10:58.920 --> 0:11:02.720
<v Speaker 1>So if an object act that conducts electricity makes contact

0:11:02.720 --> 0:11:06.360
<v Speaker 1>with the screen, so for example, your finger, there's a

0:11:06.480 --> 0:11:09.680
<v Speaker 1>change in that electrical charge. Technically the change is a

0:11:09.800 --> 0:11:13.800
<v Speaker 1>drop in voltage. So by detecting where that change happens

0:11:13.840 --> 0:11:17.880
<v Speaker 1>along those x y coordinates, A microprocessor can interpret the

0:11:17.920 --> 0:11:22.760
<v Speaker 1>touch and associate it with whatever command you wanted to execute. So,

0:11:22.920 --> 0:11:26.040
<v Speaker 1>in the example of activating an icon on a screen,

0:11:26.520 --> 0:11:31.120
<v Speaker 1>the icon represents the execution of a particular app or program.

0:11:31.160 --> 0:11:35.440
<v Speaker 1>When the microprocessor or touch sensor detects a contact at

0:11:35.480 --> 0:11:38.720
<v Speaker 1>the location of such an icon, it interprets that touch

0:11:38.920 --> 0:11:43.439
<v Speaker 1>to mean execute the program associated with the image at

0:11:43.520 --> 0:11:47.200
<v Speaker 1>these coordinates on the display, and then it will launch

0:11:47.240 --> 0:11:50.880
<v Speaker 1>the app. A similar thing happens with gesture controls like

0:11:50.960 --> 0:11:55.280
<v Speaker 1>swiping or pinching. Engineers and programmers have to build in

0:11:55.320 --> 0:11:58.680
<v Speaker 1>this capability so that the system can interpret the meaning

0:11:58.800 --> 0:12:02.760
<v Speaker 1>behind the gestures and thus produced the appropriate result, But

0:12:02.800 --> 0:12:06.280
<v Speaker 1>the actual detection of a touch all comes down to

0:12:06.400 --> 0:12:10.640
<v Speaker 1>that change and voltage. Early capacity of screens could really

0:12:10.679 --> 0:12:14.360
<v Speaker 1>only detect one point of contact, so if you tried

0:12:14.440 --> 0:12:17.680
<v Speaker 1>touching the screen with more than one finger, typically the

0:12:17.720 --> 0:12:21.800
<v Speaker 1>screen would only register that first touch. This is because

0:12:21.840 --> 0:12:26.160
<v Speaker 1>the sensing technology was limited. Early sensors would estimate the

0:12:26.280 --> 0:12:31.079
<v Speaker 1>point of contact. It wasn't incredibly precise. It was precise

0:12:31.200 --> 0:12:35.080
<v Speaker 1>enough for general use, but you couldn't really get fine

0:12:35.160 --> 0:12:39.480
<v Speaker 1>tuning with it. Later implementations would incorporate better sensors, and

0:12:39.480 --> 0:12:42.800
<v Speaker 1>eventually you'd find capacity of screens in which each row

0:12:43.120 --> 0:12:47.000
<v Speaker 1>or column of wires had its own associated sensors, which

0:12:47.040 --> 0:12:49.960
<v Speaker 1>increased their accuracy, and it opened up the possibility of

0:12:49.960 --> 0:12:54.160
<v Speaker 1>a capacity of screen with multi touch capability. Johnson would

0:12:54.200 --> 0:12:57.520
<v Speaker 1>receive a U S patent for his invention in nineteen

0:12:57.679 --> 0:13:02.040
<v Speaker 1>sixty nine. So if you'd like an engineer's explanation of

0:13:02.080 --> 0:13:05.200
<v Speaker 1>the basic technology behind these capacity of touch screens, you

0:13:05.360 --> 0:13:08.840
<v Speaker 1>two can search for u S Patent three million, four

0:13:08.920 --> 0:13:13.320
<v Speaker 1>hundred eighty two thousand, two hundred forty one. The patent

0:13:13.440 --> 0:13:17.200
<v Speaker 1>includes circuit diagrams and a flow chart that are helpful

0:13:17.200 --> 0:13:20.240
<v Speaker 1>to understand how it works as well. The capacity of

0:13:20.280 --> 0:13:24.040
<v Speaker 1>screen was a great innovation, but it saw little adoption

0:13:24.320 --> 0:13:28.160
<v Speaker 1>over the following few years. An alternative approach would get

0:13:28.160 --> 0:13:31.199
<v Speaker 1>a bit more traction. In the short term. You could

0:13:31.240 --> 0:13:35.240
<v Speaker 1>say the tech world couldn't resist it. I'll explain more

0:13:35.640 --> 0:13:47.440
<v Speaker 1>after this break in nineteen seventy, Dr George Samuel Hurst

0:13:47.600 --> 0:13:51.320
<v Speaker 1>invented the first resistive touch screen. In the late nineteen

0:13:51.320 --> 0:13:53.880
<v Speaker 1>forties through the nineteen fifties, he had worked at the

0:13:53.920 --> 0:13:57.520
<v Speaker 1>oak Ridge National Laboratory and R and D facility that

0:13:57.640 --> 0:14:00.559
<v Speaker 1>is funded by the U. S Department of Energy. Herst

0:14:00.600 --> 0:14:03.720
<v Speaker 1>has been working in the field of atomic physics, developing

0:14:03.760 --> 0:14:08.600
<v Speaker 1>stuff like radiation detectors at nuclear testing sites. In nineteen

0:14:08.720 --> 0:14:12.440
<v Speaker 1>sixty six, he accepted a job as professor of physics

0:14:12.480 --> 0:14:15.760
<v Speaker 1>at the University of Kentucky. While in that role, he

0:14:15.800 --> 0:14:19.720
<v Speaker 1>continued doing research into atomic physics, but his team was

0:14:19.800 --> 0:14:23.120
<v Speaker 1>running into some obstacles, particularly in the use of a

0:14:23.200 --> 0:14:27.640
<v Speaker 1>vander graphic accelerator, which is an electro static generator that

0:14:27.760 --> 0:14:31.640
<v Speaker 1>can be used as a particle accelerator. To quote the Minerals,

0:14:31.680 --> 0:14:36.600
<v Speaker 1>Metals and Materials Society, which has a PDF about these devices, quote,

0:14:37.120 --> 0:14:40.520
<v Speaker 1>a high potential difference is built up and maintained on

0:14:40.560 --> 0:14:44.920
<v Speaker 1>a smooth conducting surface by the continuous transfer of positive

0:14:44.920 --> 0:14:48.840
<v Speaker 1>static charges from a moving belt to the surface. When

0:14:48.960 --> 0:14:52.720
<v Speaker 1>used as a particle accelerator, and ion source is located

0:14:52.800 --> 0:14:56.960
<v Speaker 1>inside the high voltage terminal. Ions are accelerated from the

0:14:57.000 --> 0:15:00.440
<v Speaker 1>source to the target by the electric voltage between the

0:15:00.520 --> 0:15:06.040
<v Speaker 1>high voltage supply and ground. Now that sounds complicated, but

0:15:06.320 --> 0:15:10.840
<v Speaker 1>it's essentially a vandergraph generator and you've probably seen one

0:15:10.880 --> 0:15:13.440
<v Speaker 1>of these, maybe non in person, but probably at least

0:15:13.480 --> 0:15:16.880
<v Speaker 1>in a picture or video. They typically look like silver

0:15:17.160 --> 0:15:21.360
<v Speaker 1>orbs that can give off a spectacular spark when they operate.

0:15:21.400 --> 0:15:25.000
<v Speaker 1>There's typically a large silver orb on a pedestal, and

0:15:25.040 --> 0:15:28.440
<v Speaker 1>then there's a smaller silver orb that's located a certain

0:15:28.480 --> 0:15:31.480
<v Speaker 1>distance away from the large one, and when you turn

0:15:31.520 --> 0:15:36.440
<v Speaker 1>it on, inside that pedestal, there is a belt that's

0:15:36.520 --> 0:15:39.200
<v Speaker 1>running in a loop, and the belt is essentially building

0:15:39.280 --> 0:15:44.640
<v Speaker 1>up a positive charge inside that large silver orb, and

0:15:44.680 --> 0:15:48.120
<v Speaker 1>when the the voltage difference is enough between the large

0:15:48.120 --> 0:15:51.720
<v Speaker 1>silver orb and the small silver orb, it will create

0:15:51.760 --> 0:15:55.560
<v Speaker 1>a spark between the two. It can be really really spectacular.

0:15:55.720 --> 0:15:57.480
<v Speaker 1>Now I'll have to do a full episode on those

0:15:57.520 --> 0:15:59.840
<v Speaker 1>in the future. Let's get back to touch screens. So

0:16:00.000 --> 0:16:02.280
<v Speaker 1>Hearst was working with others on his team to come

0:16:02.360 --> 0:16:06.200
<v Speaker 1>up with what they called an electrically conductive paper in

0:16:06.320 --> 0:16:09.440
<v Speaker 1>order to work with these vander Graph accelerators and to

0:16:10.000 --> 0:16:14.360
<v Speaker 1>make their notes more um efficient. The paper would be

0:16:14.360 --> 0:16:17.720
<v Speaker 1>able to pinpoint contact, and when mapped to an x

0:16:17.840 --> 0:16:21.200
<v Speaker 1>Y coordinate system, could be used to specify a particular

0:16:21.240 --> 0:16:26.400
<v Speaker 1>location of contact. So Herst thought, wait a minute, this

0:16:26.440 --> 0:16:29.080
<v Speaker 1>could be used as an interface for computers, not just

0:16:29.120 --> 0:16:32.400
<v Speaker 1>for registering a specific point in space for the purposes

0:16:32.440 --> 0:16:35.400
<v Speaker 1>of research. So Heirst returned to work for the oak

0:16:35.480 --> 0:16:39.520
<v Speaker 1>Ridge National Laboratory in ninety and he refined his idea.

0:16:39.720 --> 0:16:42.720
<v Speaker 1>He worked with nine other Eggheads to create the first

0:16:42.800 --> 0:16:48.680
<v Speaker 1>resistive touch screen. Okay, so, a resistive touch screen has

0:16:48.760 --> 0:16:52.320
<v Speaker 1>a couple of layers, one of which is conductive and

0:16:52.360 --> 0:16:55.560
<v Speaker 1>the other of which is resistive, meaning it resists the

0:16:55.600 --> 0:16:58.920
<v Speaker 1>flow of electrons through the material, and separating those two

0:16:59.040 --> 0:17:03.720
<v Speaker 1>layers are small spacers. Spacers are essentially little blocks of

0:17:03.880 --> 0:17:07.000
<v Speaker 1>non conductive material. They act as as support structure. They

0:17:07.080 --> 0:17:10.040
<v Speaker 1>keep the two layers from being in contact with one another,

0:17:10.560 --> 0:17:13.480
<v Speaker 1>and there's also usually a scratch resistant layer on top

0:17:13.600 --> 0:17:17.320
<v Speaker 1>of the surface that faces the user. Because using a

0:17:17.359 --> 0:17:20.960
<v Speaker 1>resistive screen touch screen means that you're actually having to

0:17:21.000 --> 0:17:23.800
<v Speaker 1>apply pressure on the touch screen. You're not just touching it,

0:17:23.800 --> 0:17:28.200
<v Speaker 1>you're actually pressing it. So when you press a resistive screen,

0:17:28.440 --> 0:17:31.919
<v Speaker 1>you apply that little bit of pressure. The conductive and

0:17:31.960 --> 0:17:36.760
<v Speaker 1>resistive layers move closer together, they're flexible, and eventually they

0:17:36.800 --> 0:17:40.320
<v Speaker 1>touch each other. Now both layers have an electrical current

0:17:40.400 --> 0:17:44.080
<v Speaker 1>running through them, and when they make contact, the electrical

0:17:44.119 --> 0:17:49.080
<v Speaker 1>field changes, and sensors and a microprocessor detect and analyze

0:17:49.119 --> 0:17:51.879
<v Speaker 1>that point of contact and register it so that the

0:17:51.920 --> 0:17:54.880
<v Speaker 1>device does whatever it is you wanted to do, from

0:17:54.880 --> 0:17:59.080
<v Speaker 1>allowing you to make a digital signature to executing a command. Now,

0:17:59.160 --> 0:18:03.080
<v Speaker 1>unlike a capac poet of screen, resistive screens don't require

0:18:03.119 --> 0:18:06.800
<v Speaker 1>the point of contact to come from an electrically conductive material.

0:18:07.200 --> 0:18:10.679
<v Speaker 1>A resistive screen doesn't care if the thing touching the

0:18:10.720 --> 0:18:13.679
<v Speaker 1>screen is your finger, or it's a hot dog wiener,

0:18:14.280 --> 0:18:18.399
<v Speaker 1>or a plastic stylus or a rock or whatever it

0:18:18.560 --> 0:18:22.399
<v Speaker 1>is that's applying the pressure. All the electrical activity is

0:18:22.440 --> 0:18:26.320
<v Speaker 1>contained within those layers that make up the outer part

0:18:26.359 --> 0:18:29.159
<v Speaker 1>of the screen. So you can operate a device with

0:18:29.200 --> 0:18:33.200
<v Speaker 1>a resistive touch screen even if you're wearing non conductive gloves.

0:18:33.520 --> 0:18:36.200
<v Speaker 1>And if the screen were to get a little wet,

0:18:36.560 --> 0:18:38.680
<v Speaker 1>you never want your electronics to really get wet. But

0:18:38.720 --> 0:18:40.800
<v Speaker 1>let's say a little water gets on it, it wouldn't

0:18:40.800 --> 0:18:44.359
<v Speaker 1>affect the performance. That's different from a capacitive screen. If

0:18:44.400 --> 0:18:46.919
<v Speaker 1>you've ever had a smartphone get a little bit of

0:18:46.920 --> 0:18:48.920
<v Speaker 1>water on it. Let's say it's a very light rain

0:18:49.119 --> 0:18:50.919
<v Speaker 1>and you're trying to use your smartphone, you might have

0:18:50.960 --> 0:18:54.280
<v Speaker 1>encountered some problems with it. Well. Capacitive touch screens don't

0:18:54.280 --> 0:18:56.400
<v Speaker 1>work so well when they get a little water on them.

0:18:56.800 --> 0:19:01.639
<v Speaker 1>It messes with this ability to detect the actual point

0:19:01.680 --> 0:19:07.240
<v Speaker 1>of contact with a conductive surface. So resistive screens don't

0:19:07.280 --> 0:19:09.760
<v Speaker 1>have that issue, although you still shouldn't really operate them

0:19:09.760 --> 0:19:13.040
<v Speaker 1>in the rain. Now that being said, resistive touch screens

0:19:13.240 --> 0:19:16.400
<v Speaker 1>tend to be harder to read and to see what's

0:19:16.440 --> 0:19:19.240
<v Speaker 1>on the screen. They require more layers than a capacity

0:19:19.240 --> 0:19:21.880
<v Speaker 1>of screen does, and they tend to reflect a lot

0:19:21.880 --> 0:19:25.800
<v Speaker 1>more ambient light than capacitive screens. Plus, while they are

0:19:25.960 --> 0:19:30.359
<v Speaker 1>pretty hardy, they do rely on detecting pressure, and depending

0:19:30.400 --> 0:19:32.480
<v Speaker 1>on how hard people are pushing while they're trying to

0:19:32.560 --> 0:19:36.080
<v Speaker 1>use these things, it can cause some wear and tear

0:19:36.240 --> 0:19:39.560
<v Speaker 1>on the device. If the spacers that separate those two

0:19:39.680 --> 0:19:42.600
<v Speaker 1>screens get damaged, then the screen can end up having

0:19:42.760 --> 0:19:46.440
<v Speaker 1>points of contact before you've even touched it, which sends

0:19:46.560 --> 0:19:49.479
<v Speaker 1>erroneous signals to the microprocess or it doesn't actually know

0:19:49.560 --> 0:19:53.720
<v Speaker 1>where you're trying to touch it because it's getting conflicting information. Also,

0:19:54.160 --> 0:19:57.400
<v Speaker 1>they were limited to detecting a single point of contact

0:19:57.600 --> 0:20:01.119
<v Speaker 1>which eliminated the possibility for a multi touch Still, because

0:20:01.119 --> 0:20:03.600
<v Speaker 1>they could stand up to a lot of punishment and

0:20:03.640 --> 0:20:06.240
<v Speaker 1>they could work in different environments, they found a lot

0:20:06.240 --> 0:20:11.400
<v Speaker 1>of applications in different technologies, particularly in stuff like military tech. Now,

0:20:11.440 --> 0:20:15.240
<v Speaker 1>just one year after Hurst's resistive touch screen approach made

0:20:15.280 --> 0:20:20.560
<v Speaker 1>the news, the University of Illinois introduced the PLATO for system.

0:20:20.560 --> 0:20:26.840
<v Speaker 1>PLATO stands for Programmed Logic for Automatic Teaching Operations. One

0:20:26.840 --> 0:20:30.040
<v Speaker 1>of the components of this system was an orange plasma

0:20:30.119 --> 0:20:36.040
<v Speaker 1>display with touch screen capability, But unlike the previous inventions,

0:20:36.440 --> 0:20:41.240
<v Speaker 1>this approach relied upon an infrared touch panel. All right, well, then,

0:20:41.280 --> 0:20:45.080
<v Speaker 1>how does an infrared touch panel work. Well, imagine that

0:20:45.160 --> 0:20:47.399
<v Speaker 1>you have an array of l e ED s that

0:20:47.480 --> 0:20:51.160
<v Speaker 1>emit light in the infrared spectrum, so they're like tiny

0:20:51.280 --> 0:20:56.080
<v Speaker 1>little infrared flashlights. Infrared is outside the visible spectrum of light.

0:20:56.160 --> 0:20:58.280
<v Speaker 1>So to us it would seem as if an LED

0:20:58.440 --> 0:21:01.000
<v Speaker 1>light was off because we can't see that light. But

0:21:01.080 --> 0:21:04.280
<v Speaker 1>in fact, it would be beaming this infrared light across

0:21:04.440 --> 0:21:07.760
<v Speaker 1>the surface of a screen, and on the other side

0:21:07.840 --> 0:21:10.480
<v Speaker 1>of the beam would be a photo cell. So, in

0:21:10.520 --> 0:21:12.919
<v Speaker 1>other words, a light sensor, and it's a sensor at

0:21:13.000 --> 0:21:17.240
<v Speaker 1>tuned specifically to detecting that frequency of infrared light that

0:21:17.359 --> 0:21:21.359
<v Speaker 1>it was paired with. So if you could see these lights,

0:21:21.600 --> 0:21:24.680
<v Speaker 1>it would look like a laser grid, kind of like

0:21:24.720 --> 0:21:28.719
<v Speaker 1>admission impossible or Tom Cruise is coming down from the ceiling.

0:21:29.000 --> 0:21:33.320
<v Speaker 1>It's pretty awesome scene. But that's what infrared touch screen

0:21:33.359 --> 0:21:36.159
<v Speaker 1>would look like if you could see those infrared beams. Now,

0:21:36.200 --> 0:21:39.160
<v Speaker 1>if the beam remains unbroken, then it's clear there's no

0:21:39.200 --> 0:21:42.359
<v Speaker 1>contact with the screen. If the sensors keep on picking

0:21:42.440 --> 0:21:45.359
<v Speaker 1>up the light, they just say, all right, nothing's touching.

0:21:45.880 --> 0:21:50.120
<v Speaker 1>But if something that blocks the light that's between the

0:21:50.240 --> 0:21:52.520
<v Speaker 1>l e ED that's emitting the light and the photo cell,

0:21:52.960 --> 0:21:56.359
<v Speaker 1>that interruption would indicate that something has touched the screen.

0:21:56.960 --> 0:21:59.119
<v Speaker 1>And by arranging the l e d s and the

0:21:59.160 --> 0:22:02.800
<v Speaker 1>photo cells and having them paired up in columns and

0:22:02.880 --> 0:22:06.480
<v Speaker 1>in rows as a grid system, then you have a

0:22:06.520 --> 0:22:09.320
<v Speaker 1>whole net of those invisible beams. Touching a point on

0:22:09.359 --> 0:22:13.200
<v Speaker 1>the screen would interrupt both horizontal and vertical beams along

0:22:13.240 --> 0:22:18.080
<v Speaker 1>the surface, So a microprocessor could detect which photo cells

0:22:18.080 --> 0:22:21.840
<v Speaker 1>had registered the interruption and then plot the point where

0:22:21.880 --> 0:22:25.480
<v Speaker 1>that happened. So it's very similar to plotting a point

0:22:25.560 --> 0:22:29.200
<v Speaker 1>on a grid in math class. Like the resist of screens,

0:22:29.680 --> 0:22:33.040
<v Speaker 1>this approach had the benefit of working with any light

0:22:33.080 --> 0:22:36.040
<v Speaker 1>blocking material. It did not have to be electrically conductive,

0:22:36.680 --> 0:22:39.359
<v Speaker 1>so a plastic stylus works just as well as a

0:22:39.400 --> 0:22:42.879
<v Speaker 1>finger if the technology is implemented properly. Also, there's no

0:22:42.960 --> 0:22:46.680
<v Speaker 1>need to work in thin metallic wires in the screen itself,

0:22:46.720 --> 0:22:50.200
<v Speaker 1>because the screen is not what's detecting the touch. It's

0:22:50.280 --> 0:22:54.000
<v Speaker 1>this laser grid essentially not really lasers, but this led

0:22:54.160 --> 0:22:58.480
<v Speaker 1>grid with the photo cells, so the screen wouldn't have

0:22:58.520 --> 0:23:01.600
<v Speaker 1>any wires in it. It would be brighter and provide

0:23:01.600 --> 0:23:05.399
<v Speaker 1>more clarity than early capacity and resist of versions could.

0:23:05.920 --> 0:23:09.400
<v Speaker 1>That was a big advantage. The infrared approach would see

0:23:09.520 --> 0:23:13.000
<v Speaker 1>use in the nineteen eighties in the HP one fifty.

0:23:13.240 --> 0:23:16.040
<v Speaker 1>That was a computer system from well then Hewlett Packard

0:23:16.400 --> 0:23:21.000
<v Speaker 1>before they became just HP and it costs the princely

0:23:21.240 --> 0:23:25.760
<v Speaker 1>sum of two thousand, seven hundred ninety five dollars in

0:23:25.880 --> 0:23:29.320
<v Speaker 1>ninety three, but if we have adjust that for inflation,

0:23:30.000 --> 0:23:33.120
<v Speaker 1>that means in today's money it would cost about seven thousand,

0:23:33.160 --> 0:23:37.040
<v Speaker 1>two hundred dollars. Yikes. The HP one fifty version, or

0:23:37.119 --> 0:23:39.880
<v Speaker 1>portly had some issues that that made it less practical.

0:23:39.960 --> 0:23:43.560
<v Speaker 1>So I imagine that, uh, the fact that it wasn't

0:23:43.600 --> 0:23:46.359
<v Speaker 1>working perfectly and that the price tag was so high

0:23:46.560 --> 0:23:48.560
<v Speaker 1>meant it didn't get a whole lot of traction in

0:23:48.560 --> 0:23:52.080
<v Speaker 1>the market. Later on, devices like the Sony E reader

0:23:52.240 --> 0:23:56.040
<v Speaker 1>would actually adopt this technology. Now around the same time

0:23:56.080 --> 0:23:58.920
<v Speaker 1>that the infrared system debuted in the mid nineteen seventies,

0:23:59.320 --> 0:24:03.879
<v Speaker 1>g why Zapp Finel and Chris Herold of the Architecture

0:24:03.960 --> 0:24:05.879
<v Speaker 1>Machine Group at M I T. And I know I

0:24:05.960 --> 0:24:09.480
<v Speaker 1>butchered their names. I apologize anyway, they created a touch

0:24:09.520 --> 0:24:13.680
<v Speaker 1>screen interface that could detect not just touch but also pressure.

0:24:14.119 --> 0:24:16.920
<v Speaker 1>I mean it wasn't like a resistive screen in that sense.

0:24:17.160 --> 0:24:20.160
<v Speaker 1>It could actually detect how much pressure you were applying

0:24:20.320 --> 0:24:23.119
<v Speaker 1>to the screen. In fact, the system could detect up

0:24:23.119 --> 0:24:27.560
<v Speaker 1>to eight different signals from a single touch point, including torque,

0:24:28.040 --> 0:24:30.080
<v Speaker 1>which meant you could push your finger on the screen

0:24:30.640 --> 0:24:33.320
<v Speaker 1>and you add some pressure to it and then twist

0:24:33.520 --> 0:24:36.760
<v Speaker 1>your finger, and the interface could detect that you were

0:24:36.760 --> 0:24:41.800
<v Speaker 1>making this twisting motion, and you could have that imagined

0:24:41.840 --> 0:24:45.720
<v Speaker 1>as some sort of effect in a program. What kind

0:24:45.760 --> 0:24:49.240
<v Speaker 1>of effect would depend entirely on the programming, so there's

0:24:49.240 --> 0:24:52.320
<v Speaker 1>no specific application, but it could be used for all

0:24:52.359 --> 0:24:54.720
<v Speaker 1>sorts of different stuff. So they published their work in

0:24:54.800 --> 0:24:59.119
<v Speaker 1>nine with the title one point Touch Input of Vector

0:24:59.280 --> 0:25:03.399
<v Speaker 1>Information from Computer Displays, and it was published in the

0:25:03.440 --> 0:25:06.560
<v Speaker 1>Computer Graphics Periodical, So if you want to read up

0:25:06.600 --> 0:25:10.600
<v Speaker 1>on that, you can. There's also illustrations of how it worked.

0:25:10.760 --> 0:25:13.479
<v Speaker 1>There's also a YouTube video of a demonstration as a

0:25:13.600 --> 0:25:17.680
<v Speaker 1>very early demonstration of this nineteen seventies era technology. But

0:25:17.720 --> 0:25:21.160
<v Speaker 1>it's pretty fascinating to see at work. And we're not

0:25:21.280 --> 0:25:24.240
<v Speaker 1>done with the different ways to achieve touch screen functionality.

0:25:24.280 --> 0:25:27.959
<v Speaker 1>There's still some more to chat about. Engineer Nimish Meta

0:25:28.560 --> 0:25:31.960
<v Speaker 1>developed a solution for the first multi touch system in

0:25:32.080 --> 0:25:37.040
<v Speaker 1>nineteen two decades before the iPhone. Now it's important to

0:25:37.080 --> 0:25:40.399
<v Speaker 1>note that this was not so much a touch screen

0:25:40.920 --> 0:25:44.880
<v Speaker 1>as it was a control interface like a touch pad,

0:25:45.240 --> 0:25:47.440
<v Speaker 1>not a touch screen, so think like a keyboard and

0:25:47.560 --> 0:25:50.639
<v Speaker 1>mouse or something along those lines. And it consisted of

0:25:50.680 --> 0:25:54.400
<v Speaker 1>a pane of glass with a translucent layer of plastic

0:25:54.600 --> 0:25:57.879
<v Speaker 1>on that glass, giving it sort of a frosted appearance.

0:25:58.240 --> 0:26:01.639
<v Speaker 1>There was a camera mounted below or behind the glass pane,

0:26:02.119 --> 0:26:05.359
<v Speaker 1>and that would detect points of contact. Essentially, it was

0:26:05.440 --> 0:26:08.840
<v Speaker 1>looking for dark spots to appear on that surface. That

0:26:08.840 --> 0:26:12.240
<v Speaker 1>would indicate that a finger was there blocking the light.

0:26:12.760 --> 0:26:15.399
<v Speaker 1>This isn't that different from what Microsoft would use on

0:26:15.440 --> 0:26:17.920
<v Speaker 1>the surface tables a couple of decades later. I'll chat

0:26:17.960 --> 0:26:21.040
<v Speaker 1>about that in a second. So in this case, the

0:26:21.240 --> 0:26:25.480
<v Speaker 1>camera would detect these dark spots and through software, the

0:26:25.520 --> 0:26:28.399
<v Speaker 1>system would be able to interpret where those points of

0:26:28.440 --> 0:26:31.439
<v Speaker 1>contact were in relation to what was being displayed on

0:26:31.480 --> 0:26:34.879
<v Speaker 1>a screen. One benefit of this approach was that you

0:26:34.920 --> 0:26:38.280
<v Speaker 1>weren't actually making contact with the same surface you were

0:26:38.320 --> 0:26:41.960
<v Speaker 1>looking at, so you weren't smearing your grubby hands all

0:26:41.960 --> 0:26:44.280
<v Speaker 1>over the same surface you were trying to read. But

0:26:44.320 --> 0:26:47.320
<v Speaker 1>then again, you could argue the whole purpose of creating

0:26:47.320 --> 0:26:51.200
<v Speaker 1>a touch screen interface is to remove the barrier between

0:26:51.400 --> 0:26:53.920
<v Speaker 1>humans and the machines they're working on and make the

0:26:53.960 --> 0:26:57.640
<v Speaker 1>experience more intuitive. We have to learn how to use

0:26:57.680 --> 0:27:00.880
<v Speaker 1>things like a computer mouse or a keyboard. It's not

0:27:01.080 --> 0:27:04.679
<v Speaker 1>hard to learn, but it does mean manipulating something along

0:27:04.720 --> 0:27:08.000
<v Speaker 1>one surface while looking at another. So, for example, with

0:27:08.080 --> 0:27:11.080
<v Speaker 1>a traditional computer, you would use a keyboard and a

0:27:11.119 --> 0:27:14.280
<v Speaker 1>mouse on a plane that's at a ninety degree angle

0:27:14.520 --> 0:27:16.840
<v Speaker 1>with the display you're looking at right. So if you

0:27:16.840 --> 0:27:20.640
<v Speaker 1>think of horizontal and vertical. Your hands are manipulating objects

0:27:20.680 --> 0:27:24.560
<v Speaker 1>on a horizontal plane while you're looking at the reactions

0:27:24.600 --> 0:27:27.640
<v Speaker 1>on a vertical plane. So manipulating the mouse to move

0:27:27.640 --> 0:27:30.520
<v Speaker 1>a cursor requires your brain to translate the motion along

0:27:30.600 --> 0:27:34.280
<v Speaker 1>one axis of movement to a display that's on a

0:27:34.320 --> 0:27:37.080
<v Speaker 1>different axis. Now, once we learn how to do this,

0:27:37.240 --> 0:27:40.320
<v Speaker 1>and admittedly it does not take very long, it becomes

0:27:40.320 --> 0:27:43.000
<v Speaker 1>second nature, so it's not a big deal. But a

0:27:43.000 --> 0:27:46.520
<v Speaker 1>touch screen removes that necessity entirely because the thing you're

0:27:46.560 --> 0:27:50.160
<v Speaker 1>looking at and the thing you're manipulating is the same surface.

0:27:51.000 --> 0:27:57.000
<v Speaker 1>Ine Myron Krueger introduced another input method that wasn't strictly

0:27:57.119 --> 0:28:00.440
<v Speaker 1>a touch screen, but is similar enough to merit in collusion.

0:28:00.520 --> 0:28:04.600
<v Speaker 1>In this episode, Krueger's system could track a user's hands.

0:28:05.200 --> 0:28:08.320
<v Speaker 1>It was a vision based system, meaning it employed cameras

0:28:08.359 --> 0:28:11.440
<v Speaker 1>to detect and track hand motion and poses, so I

0:28:11.480 --> 0:28:14.960
<v Speaker 1>could detect multiple hands so impaired with the proper software,

0:28:15.119 --> 0:28:18.080
<v Speaker 1>it could translate the actions of those multiple hands into

0:28:18.119 --> 0:28:21.040
<v Speaker 1>commands for a program. But in this case, the system

0:28:21.080 --> 0:28:24.840
<v Speaker 1>would respond to what is called dwell time. Hand gestures

0:28:24.960 --> 0:28:28.880
<v Speaker 1>or poses would correspond to specific commands, and a user

0:28:28.920 --> 0:28:31.879
<v Speaker 1>would have to hold his or her hands within view

0:28:32.000 --> 0:28:34.600
<v Speaker 1>of this system long enough for it to register that

0:28:34.680 --> 0:28:38.520
<v Speaker 1>it was in fact a signal to do something. Well,

0:28:38.560 --> 0:28:41.840
<v Speaker 1>this wasn't directly related to touch screen technology, it is

0:28:41.880 --> 0:28:47.360
<v Speaker 1>important in the history of gestural interaction, which does intertwined

0:28:47.400 --> 0:28:50.040
<v Speaker 1>with touch screen technology quite a bit. A lot of

0:28:50.040 --> 0:28:53.640
<v Speaker 1>our interactions with touch screens depend upon not just points

0:28:53.680 --> 0:28:58.560
<v Speaker 1>of contact, but specific gestures swiping, pinching, that kind of thing,

0:28:59.160 --> 0:29:02.440
<v Speaker 1>and I figured should at least touch on Krueger's work.

0:29:02.840 --> 0:29:06.360
<v Speaker 1>Krueger wrote several books on technology that are pretty fascinating.

0:29:06.360 --> 0:29:08.480
<v Speaker 1>I feel I should probably dedicate a full episode to

0:29:08.520 --> 0:29:11.600
<v Speaker 1>him at some point, and we're not finished yet, so

0:29:11.680 --> 0:29:14.720
<v Speaker 1>when we come back, I'll talk more about multi touch

0:29:14.880 --> 0:29:18.360
<v Speaker 1>systems that actually did rely on making contact with a screen.

0:29:18.400 --> 0:29:28.800
<v Speaker 1>But first let's take another quick break. So the first

0:29:28.880 --> 0:29:32.600
<v Speaker 1>screen to feature multi touch isn't the surface. It's not

0:29:32.720 --> 0:29:36.160
<v Speaker 1>the iPhone, though you wouldn't necessarily know that based upon

0:29:36.240 --> 0:29:40.720
<v Speaker 1>the marketing around those devices. A Bell Labs researcher named

0:29:40.800 --> 0:29:48.720
<v Speaker 1>Bob Boy created the first multi touch capacitive screen in Actually,

0:29:48.920 --> 0:29:51.440
<v Speaker 1>to be fair, it really was an array of capacitive

0:29:51.520 --> 0:29:55.480
<v Speaker 1>touch sensors that were mounted on a transparent film that

0:29:55.520 --> 0:29:58.280
<v Speaker 1>could be added as an overlay on top of a

0:29:58.320 --> 0:30:01.680
<v Speaker 1>CRT monitor, So monitor itself wouldn't have the touch screen

0:30:01.720 --> 0:30:03.840
<v Speaker 1>built into it. It would actually be a peripheral you

0:30:03.840 --> 0:30:07.440
<v Speaker 1>could add to the monitor. This prototype never emerged out

0:30:07.440 --> 0:30:11.080
<v Speaker 1>of the lab for broader application, but it was able

0:30:11.120 --> 0:30:15.080
<v Speaker 1>to register the touch of multiple points of contact, and

0:30:15.120 --> 0:30:19.160
<v Speaker 1>thus you could create applications that would allow for that

0:30:19.280 --> 0:30:22.480
<v Speaker 1>and to you know, create new commands for how this

0:30:22.560 --> 0:30:25.640
<v Speaker 1>could work. And there are a couple of other approaches

0:30:25.680 --> 0:30:28.959
<v Speaker 1>to multi touch. One demonstrated by Jeff Hahn in two

0:30:29.000 --> 0:30:32.440
<v Speaker 1>thousand and six, used a rear projection system, a sheet

0:30:32.480 --> 0:30:37.440
<v Speaker 1>of acrylic and an LED that created frustrated total internal

0:30:37.520 --> 0:30:41.240
<v Speaker 1>reflection or f t i R, which sounds to me

0:30:41.400 --> 0:30:44.480
<v Speaker 1>like meditating a self discovery only to find out you're

0:30:44.480 --> 0:30:47.560
<v Speaker 1>actually a total jerk. But that's not what it actually means.

0:30:47.800 --> 0:30:52.080
<v Speaker 1>So to get into the nitty gritty of the technology

0:30:52.440 --> 0:30:55.560
<v Speaker 1>is more than a little bit complicated, but I'll give

0:30:55.600 --> 0:30:59.280
<v Speaker 1>it a shot from a very high level. So imagine

0:30:59.280 --> 0:31:04.400
<v Speaker 1>you have a sheet of really clear material like acrylic. Okay,

0:31:04.400 --> 0:31:06.720
<v Speaker 1>so you've got a sheet of acrylic. Now imagine that

0:31:06.760 --> 0:31:09.880
<v Speaker 1>we're looking at this sheet of acrylic from a side

0:31:10.080 --> 0:31:14.480
<v Speaker 1>edge right, so the top surface is uh is and

0:31:14.560 --> 0:31:17.560
<v Speaker 1>the bottom surface are facing you know, up and down.

0:31:17.640 --> 0:31:20.240
<v Speaker 1>From our perspective, we're just looking at it from the side,

0:31:21.080 --> 0:31:24.200
<v Speaker 1>and you've got a bunch of infrared LEDs mounted on

0:31:24.360 --> 0:31:28.680
<v Speaker 1>either end of this acrylic sheet. Below the acrylic sheet

0:31:29.120 --> 0:31:35.280
<v Speaker 1>and facing upwards is an infrared camera. So the control

0:31:35.360 --> 0:31:38.120
<v Speaker 1>surface in this case would be above the sheet from

0:31:38.120 --> 0:31:41.760
<v Speaker 1>your perspective. The camera is below the sheet from your perspective.

0:31:42.040 --> 0:31:46.000
<v Speaker 1>So total internal reflection gives you a hint at what's

0:31:46.040 --> 0:31:48.800
<v Speaker 1>actually at play here. Those L E D s are

0:31:48.840 --> 0:31:53.320
<v Speaker 1>beaming light, infrared light into the edge of the acrylic

0:31:53.440 --> 0:31:57.200
<v Speaker 1>at a specific angle it's called the critical angle, which

0:31:57.200 --> 0:32:01.560
<v Speaker 1>results in the beam reflecting perfectly within the acrylics. So

0:32:02.240 --> 0:32:05.800
<v Speaker 1>imagine that on one side you have the beam UH

0:32:06.520 --> 0:32:09.440
<v Speaker 1>position in such a way that it's angled downward from

0:32:09.440 --> 0:32:13.720
<v Speaker 1>your perspective. The beam goes down, hits the inner bottom

0:32:13.880 --> 0:32:17.480
<v Speaker 1>edge of the acrylic, bounces up with no refraction. It's

0:32:17.560 --> 0:32:21.640
<v Speaker 1>it's a perfect reflection, and then encounters the upper edge

0:32:21.640 --> 0:32:26.160
<v Speaker 1>from your perspective, bounces off that again perfectly reflected, and

0:32:26.200 --> 0:32:31.600
<v Speaker 1>does so all through the entire length of this acrylic sheet. Now,

0:32:31.600 --> 0:32:33.280
<v Speaker 1>if you could see the beams of infrared light, you

0:32:33.320 --> 0:32:35.880
<v Speaker 1>would see how they were criss crossing around inside this

0:32:35.920 --> 0:32:38.920
<v Speaker 1>acrylic bouncing off those inner surfaces of either face of

0:32:39.000 --> 0:32:43.360
<v Speaker 1>the sheet. And it happens because physics. I mean, it

0:32:43.400 --> 0:32:45.600
<v Speaker 1>gets more complicated than that. But if I were to

0:32:45.680 --> 0:32:47.840
<v Speaker 1>jump into it, I would have to talk about Snell's

0:32:48.000 --> 0:32:52.600
<v Speaker 1>law and the refractive index, and honestly, it would get

0:32:52.760 --> 0:32:55.640
<v Speaker 1>super complex and it would be hard to describe without

0:32:55.720 --> 0:32:57.520
<v Speaker 1>the use of visual aids. So I'm just gonna take

0:32:57.520 --> 0:32:59.440
<v Speaker 1>a shortcut in this case and just say it works

0:32:59.480 --> 0:33:02.880
<v Speaker 1>because of physics. Anyway. The result is you have these

0:33:02.920 --> 0:33:07.000
<v Speaker 1>perfectly reflective beams of infrared light bouncing around inside this

0:33:07.040 --> 0:33:10.719
<v Speaker 1>acrylic sheet. But if you were to touch the surface

0:33:10.760 --> 0:33:14.080
<v Speaker 1>of the sheet on the active side, the top side,

0:33:14.600 --> 0:33:20.040
<v Speaker 1>you frustrate this total internal reflection. Some of that light

0:33:20.520 --> 0:33:23.720
<v Speaker 1>that was being reflected inside the acrylic sheet at the

0:33:23.760 --> 0:33:27.560
<v Speaker 1>point of contact can pass from the surface to your finger,

0:33:27.960 --> 0:33:31.320
<v Speaker 1>so reflection is no longer total. And the infrared count

0:33:31.600 --> 0:33:35.400
<v Speaker 1>camera that's mounted beneath the sheets, pointed up at it

0:33:35.440 --> 0:33:39.600
<v Speaker 1>will detect that change in the reflectivity at the point

0:33:39.600 --> 0:33:43.200
<v Speaker 1>of contact, registering it as a touch, and this system

0:33:43.240 --> 0:33:46.120
<v Speaker 1>can detect multiple points of contact on the same surface,

0:33:46.160 --> 0:33:50.040
<v Speaker 1>so it is a multi touch approach. In two thousand seven,

0:33:50.400 --> 0:33:54.240
<v Speaker 1>Microsoft showed off a table sized computer system that it

0:33:54.320 --> 0:33:57.960
<v Speaker 1>called the Surface. Since then, Microsoft has used the name

0:33:58.040 --> 0:34:01.240
<v Speaker 1>Surface for some of its other product us, largely the

0:34:01.280 --> 0:34:05.840
<v Speaker 1>tablet style computers. But the early version of the Surface

0:34:06.000 --> 0:34:10.520
<v Speaker 1>was much much larger, and it was a collaborative workspace

0:34:10.800 --> 0:34:15.319
<v Speaker 1>where multiple people could stand around this interactive table, the

0:34:15.400 --> 0:34:18.399
<v Speaker 1>top of which was a computer display, and it could

0:34:18.400 --> 0:34:21.960
<v Speaker 1>detect multiple points of contact on that computer display. You

0:34:22.000 --> 0:34:25.680
<v Speaker 1>could manipulate virtual objects, you could play games, you could

0:34:25.719 --> 0:34:28.600
<v Speaker 1>do a lot of different stuff. The Surface worked using

0:34:28.680 --> 0:34:32.000
<v Speaker 1>some of the methods I've already mentioned in this episode.

0:34:32.080 --> 0:34:35.600
<v Speaker 1>Inside the table was a projector, and the projector was

0:34:35.640 --> 0:34:39.520
<v Speaker 1>projecting the images that you would see on the actual surface,

0:34:39.920 --> 0:34:42.960
<v Speaker 1>So what you were looking at was really a projection

0:34:43.120 --> 0:34:46.359
<v Speaker 1>being shot against the backside of the screen you were

0:34:46.400 --> 0:34:49.239
<v Speaker 1>looking at. So, in other words, the Surfaces screen was

0:34:49.320 --> 0:34:52.600
<v Speaker 1>what we would call a rear projection screen, very much

0:34:52.640 --> 0:34:57.160
<v Speaker 1>like rear projection televisions. Also inside the Surface were cameras

0:34:57.160 --> 0:34:59.839
<v Speaker 1>that could detect the points of contact on the opp

0:35:00.080 --> 0:35:02.480
<v Speaker 1>outside of the screen on your side. In other words,

0:35:02.880 --> 0:35:06.279
<v Speaker 1>Microsoft also designed a program that could recognize patterns that

0:35:06.320 --> 0:35:09.680
<v Speaker 1>were printed on special stickers. Then they could put those

0:35:09.680 --> 0:35:13.360
<v Speaker 1>stickers onto solid objects. So if you place one of

0:35:13.360 --> 0:35:18.120
<v Speaker 1>those small objects on the surface, the camera underneath would

0:35:18.160 --> 0:35:21.160
<v Speaker 1>be able to recognize the pattern on that sticker and

0:35:21.200 --> 0:35:25.520
<v Speaker 1>then execute an associated command, which could be anything. But

0:35:25.680 --> 0:35:28.960
<v Speaker 1>one version of this one version I saw was that

0:35:29.000 --> 0:35:32.440
<v Speaker 1>you could have sort of a synthesizer application, one that

0:35:32.480 --> 0:35:37.560
<v Speaker 1>could play pre rendered styles of music, and each sticker

0:35:37.640 --> 0:35:41.360
<v Speaker 1>would represent maybe a specific tone or a sound pattern

0:35:41.520 --> 0:35:45.880
<v Speaker 1>or a sound effect, and by arranging a series of

0:35:45.920 --> 0:35:49.560
<v Speaker 1>these objects on the surface, you could build a sound

0:35:50.040 --> 0:35:53.719
<v Speaker 1>So you could create a series of sounds, like in

0:35:53.760 --> 0:35:57.799
<v Speaker 1>a particular rhythm. By manipulating these objects and changing the

0:35:57.840 --> 0:36:00.920
<v Speaker 1>location on the surface might do things like change the

0:36:00.920 --> 0:36:04.400
<v Speaker 1>pitch or the volume of each sound. So you would

0:36:04.400 --> 0:36:07.920
<v Speaker 1>have this interactive kind of music surface to work with.

0:36:08.200 --> 0:36:10.759
<v Speaker 1>And that's just one example of what you could do

0:36:10.920 --> 0:36:14.800
<v Speaker 1>with this type of technology. There were lots of potential applications.

0:36:15.760 --> 0:36:19.040
<v Speaker 1>Microsoft would actually bring that version of the Surface to

0:36:19.200 --> 0:36:21.880
<v Speaker 1>c E. S. Two thousand eight, but the company was

0:36:21.880 --> 0:36:26.960
<v Speaker 1>also quick to say that the technology wasn't actually consumer tech. Rather,

0:36:27.200 --> 0:36:30.040
<v Speaker 1>this was technology that businesses would be able to purchase

0:36:30.320 --> 0:36:33.120
<v Speaker 1>for their own purposes. So you might have it in

0:36:33.160 --> 0:36:37.399
<v Speaker 1>a retail establishment, you might have it in an entertainment establishment.

0:36:38.000 --> 0:36:41.160
<v Speaker 1>One of the versions I heard about was being used

0:36:41.200 --> 0:36:44.520
<v Speaker 1>in a Las Vegas bar where you could play games

0:36:44.680 --> 0:36:47.160
<v Speaker 1>on the table, or you could use your table to

0:36:47.239 --> 0:36:51.520
<v Speaker 1>send messages to other people around the bar on their tables,

0:36:51.920 --> 0:36:53.960
<v Speaker 1>which kind of skeeths me out a little bit. But

0:36:53.960 --> 0:36:56.319
<v Speaker 1>then again, I'm not a bar person, so maybe I'm

0:36:56.360 --> 0:36:58.759
<v Speaker 1>just the wrong kind of guy to look into that

0:36:58.800 --> 0:37:01.279
<v Speaker 1>sort of thing. It just seems like another way to

0:37:01.320 --> 0:37:04.440
<v Speaker 1>kind of harass people without them, you know, wanting it.

0:37:05.200 --> 0:37:07.920
<v Speaker 1>Who am I to say? The same year that Microsoft

0:37:08.000 --> 0:37:12.480
<v Speaker 1>first demonstrated the surface, Apple introduced the iPhone, and again,

0:37:12.480 --> 0:37:16.080
<v Speaker 1>while Apple didn't invent capacitive touch or even capacity of

0:37:16.120 --> 0:37:20.520
<v Speaker 1>multi touch, heck, even the gestures associated with gestural interaction

0:37:20.560 --> 0:37:23.880
<v Speaker 1>on the iPhone were already described by other people in

0:37:23.920 --> 0:37:27.279
<v Speaker 1>other systems, but the packaging of all of those features

0:37:27.320 --> 0:37:32.160
<v Speaker 1>in a sleek smartphone form factor wowed the crowds. The

0:37:32.200 --> 0:37:36.480
<v Speaker 1>iPhone brought touchscreen technology into the spotlight for lots of people,

0:37:37.000 --> 0:37:39.680
<v Speaker 1>when earlier it had been a type of user interface

0:37:40.040 --> 0:37:45.000
<v Speaker 1>that really only applied to electronics in niche applications and implementations.

0:37:45.480 --> 0:37:48.200
<v Speaker 1>The iPhone was not the first consumer gadget to rely

0:37:48.280 --> 0:37:50.880
<v Speaker 1>on touch screen interactions, but I think it's safe to

0:37:50.920 --> 0:37:54.560
<v Speaker 1>say that Apple got it so right that it changed

0:37:54.719 --> 0:37:57.799
<v Speaker 1>the game for everyone, and it became the go to

0:37:58.320 --> 0:38:03.839
<v Speaker 1>interface for mobile handheld electronics. Other than the methods I've

0:38:03.840 --> 0:38:07.160
<v Speaker 1>already covered, there are a couple of more rare forms

0:38:07.200 --> 0:38:11.080
<v Speaker 1>of touch screens out there. One is the surface acoustic

0:38:11.200 --> 0:38:15.480
<v Speaker 1>wave touch screen. Now, as that name implies, this version

0:38:15.480 --> 0:38:19.319
<v Speaker 1>of a touch screen relies on sound, specifically sounds that

0:38:19.360 --> 0:38:22.680
<v Speaker 1>are in the ultrasonic frequencies. Those are at such a

0:38:22.719 --> 0:38:25.759
<v Speaker 1>high frequency range that they are imperceptible to us, we

0:38:25.840 --> 0:38:30.040
<v Speaker 1>cannot hear them. Ultrasonic speakers would be along the edge

0:38:30.160 --> 0:38:33.360
<v Speaker 1>of the screen that would emit these high pitched sound waves,

0:38:33.600 --> 0:38:36.440
<v Speaker 1>and those sound waves reflect back and forth across the surface,

0:38:36.640 --> 0:38:40.160
<v Speaker 1>kind of like waves go across the water, and when

0:38:40.200 --> 0:38:43.000
<v Speaker 1>something would come into contact with the screen, it would

0:38:43.040 --> 0:38:46.120
<v Speaker 1>disrupt the path of those waves. And again it would

0:38:46.160 --> 0:38:50.040
<v Speaker 1>be a lot like if something large were to get

0:38:50.080 --> 0:38:54.600
<v Speaker 1>into a a wavy pool of water. Now, with water,

0:38:55.000 --> 0:38:59.520
<v Speaker 1>the waves are are really big, particularly compared to ultrasonic frequencies,

0:39:00.040 --> 0:39:01.759
<v Speaker 1>and that kind of makes it a little hard to

0:39:01.800 --> 0:39:06.520
<v Speaker 1>see what the effects are in this interrupted path system.

0:39:06.520 --> 0:39:09.239
<v Speaker 1>But it's much easier to see the change with ultrasonic

0:39:09.239 --> 0:39:12.200
<v Speaker 1>waves because they are so tiny, and sensors detect the

0:39:12.239 --> 0:39:15.840
<v Speaker 1>point of interruption to determine where you touched the screen. So,

0:39:15.880 --> 0:39:19.440
<v Speaker 1>in other words, they detect where are the waves no

0:39:19.600 --> 0:39:23.480
<v Speaker 1>longer able to travel unimpeded, and that is clearly the

0:39:23.480 --> 0:39:27.960
<v Speaker 1>point of contact. They're also touch screens called near field

0:39:28.080 --> 0:39:31.719
<v Speaker 1>imaging touch screens. These screens have technology that monitors the

0:39:31.719 --> 0:39:35.880
<v Speaker 1>electromagnetic field on the glass screen, and when something comes

0:39:35.920 --> 0:39:40.040
<v Speaker 1>close to the screens surface, it interferes with that electromagnetic field,

0:39:40.320 --> 0:39:43.080
<v Speaker 1>and the system detects that and interprets it as a touch.

0:39:43.400 --> 0:39:46.359
<v Speaker 1>These sorts of screens can also be pretty rugged, and

0:39:46.440 --> 0:39:49.279
<v Speaker 1>so they are frequently used for stuff like industrial or

0:39:49.280 --> 0:39:53.440
<v Speaker 1>military applications. And there we are. That's the history and

0:39:53.520 --> 0:39:57.920
<v Speaker 1>operation of touch screens. Uh. It's pretty complicated because, like

0:39:58.200 --> 0:40:00.960
<v Speaker 1>many other technologies, there were a lot of people taking

0:40:01.000 --> 0:40:05.360
<v Speaker 1>many different approaches, all in an effort to achieve similar goals,

0:40:05.440 --> 0:40:08.000
<v Speaker 1>and some of what I've described has also been used

0:40:08.000 --> 0:40:11.160
<v Speaker 1>in other types of interfaces that don't involve a touch

0:40:11.200 --> 0:40:14.080
<v Speaker 1>screen at all, such as the gesture controls used in

0:40:14.120 --> 0:40:18.279
<v Speaker 1>systems like the Microsoft Connect peripheral for Xbox systems. Now,

0:40:18.320 --> 0:40:20.680
<v Speaker 1>I think it's safe to say that the Connect was

0:40:20.800 --> 0:40:24.120
<v Speaker 1>largely a failed experiment. But I don't think it was

0:40:24.160 --> 0:40:27.040
<v Speaker 1>because it didn't work, because for the most part it

0:40:27.080 --> 0:40:30.279
<v Speaker 1>did work. Now, there were some rather egregious exceptions to

0:40:30.320 --> 0:40:33.520
<v Speaker 1>that rule, but for the most part it worked. Rather,

0:40:33.600 --> 0:40:36.720
<v Speaker 1>I think it failed because the system never evolved beyond

0:40:36.880 --> 0:40:41.200
<v Speaker 1>a gimmick or oddity in the eyes of most owners. Uh.

0:40:41.400 --> 0:40:43.480
<v Speaker 1>You could argue a large reason for that was just

0:40:43.600 --> 0:40:48.120
<v Speaker 1>a lack of very compelling content in the library of

0:40:48.640 --> 0:40:52.960
<v Speaker 1>games and applications that supported Connect interactivity. Still, the Connect

0:40:53.000 --> 0:40:55.879
<v Speaker 1>relied on a lot of work that was being done

0:40:55.920 --> 0:40:58.840
<v Speaker 1>in the field of touch screen user interfaces and just

0:40:59.040 --> 0:41:02.640
<v Speaker 1>your controls, So while it's not a direct application of

0:41:02.680 --> 0:41:07.440
<v Speaker 1>the technology, it is definitely related to it. Likewise, there

0:41:07.480 --> 0:41:10.840
<v Speaker 1>have been several systems for everything from virtual environments to

0:41:11.239 --> 0:41:16.200
<v Speaker 1>art installations that have used similar technologies to some touchscreen implementations.

0:41:16.600 --> 0:41:19.400
<v Speaker 1>Most of these have been visually or optically based, so

0:41:19.440 --> 0:41:23.279
<v Speaker 1>in other words, they use cameras to track the gestures, motions,

0:41:23.360 --> 0:41:26.680
<v Speaker 1>and poses of people within a physical space in order

0:41:26.719 --> 0:41:29.239
<v Speaker 1>to create some sort of effect. You may have been

0:41:29.400 --> 0:41:33.960
<v Speaker 1>one of these installations or or applications where your movements

0:41:34.000 --> 0:41:37.120
<v Speaker 1>through the space are reflected in some way. Maybe it's

0:41:37.160 --> 0:41:40.520
<v Speaker 1>a video effect, maybe it's sound. But a lot of

0:41:40.560 --> 0:41:45.319
<v Speaker 1>that also has related technologies to the ones that went

0:41:45.360 --> 0:41:49.880
<v Speaker 1>into developing touch screens. Now, considering the ubiquity of mobile devices,

0:41:50.120 --> 0:41:52.880
<v Speaker 1>I expect will continue to see advancements in touch screen

0:41:52.880 --> 0:41:56.319
<v Speaker 1>technology over the years. It may involve new approaches to

0:41:56.360 --> 0:42:00.319
<v Speaker 1>achieving the results, or it may involve refined implementation of

0:42:00.360 --> 0:42:04.560
<v Speaker 1>existing approaches to improve the overall experience. And I'm not

0:42:04.600 --> 0:42:08.759
<v Speaker 1>sure if it will translate to all our electronics. I

0:42:08.800 --> 0:42:11.480
<v Speaker 1>think there are some implementations where touch screens make a

0:42:11.480 --> 0:42:14.320
<v Speaker 1>lot of sense, and in others maybe not so much.

0:42:14.840 --> 0:42:17.360
<v Speaker 1>Like I'm still curious if people with desktop or laptop

0:42:17.400 --> 0:42:21.759
<v Speaker 1>displays that include touch sensitivity really use that feature all

0:42:21.800 --> 0:42:25.520
<v Speaker 1>that often. I mean, maybe they do. I'm only basing

0:42:25.560 --> 0:42:29.040
<v Speaker 1>this off my own anecdotal evidence, which obviously is limited

0:42:29.080 --> 0:42:32.279
<v Speaker 1>and therefore largely worthless. But it's hard for me to

0:42:32.320 --> 0:42:37.560
<v Speaker 1>imagine using a touch screen laptop or our desktop display regularly.

0:42:38.360 --> 0:42:41.560
<v Speaker 1>In fact, when i use my Microsoft Surface tablet as

0:42:41.600 --> 0:42:44.840
<v Speaker 1>a laptop, because I've got all the connected keyboard I

0:42:44.840 --> 0:42:47.080
<v Speaker 1>can use with it. When I'm using it, like in

0:42:47.120 --> 0:42:50.000
<v Speaker 1>that form factor, I totally forget that the screen actually

0:42:50.000 --> 0:42:52.760
<v Speaker 1>has touch capability, that I could reach out and touch

0:42:52.840 --> 0:42:56.560
<v Speaker 1>things on the screen instead of using the mouse pad. Uh.

0:42:56.960 --> 0:43:00.879
<v Speaker 1>But also I have to admit, as Tori will tell

0:43:00.960 --> 0:43:05.759
<v Speaker 1>you without a moment's hesitation, I'm old, and so it's

0:43:05.920 --> 0:43:08.880
<v Speaker 1>entirely possible that I'm the odd man out here. I

0:43:08.920 --> 0:43:11.800
<v Speaker 1>do think it's true that even when an interface works,

0:43:11.840 --> 0:43:15.840
<v Speaker 1>and it works well, it's not necessarily the best interface

0:43:15.920 --> 0:43:19.080
<v Speaker 1>for everything. So if I'm not the odd one out

0:43:19.360 --> 0:43:23.120
<v Speaker 1>and most people find touch screens unnecessary for laptops or desktops,

0:43:23.600 --> 0:43:26.600
<v Speaker 1>maybe we won't seem as many of those types of

0:43:26.640 --> 0:43:30.120
<v Speaker 1>devices with that feature included in the future. Kind of

0:43:30.160 --> 0:43:35.200
<v Speaker 1>like how televisions for a while all had three D capability,

0:43:35.320 --> 0:43:37.719
<v Speaker 1>and then people said, I don't want three D. I

0:43:37.760 --> 0:43:42.200
<v Speaker 1>don't care for it. It's too irritating. And now if

0:43:42.239 --> 0:43:44.680
<v Speaker 1>it is a feature, it's rarely one of the main

0:43:44.800 --> 0:43:48.560
<v Speaker 1>ones mentioned on the box. For those televisions we might

0:43:48.600 --> 0:43:50.640
<v Speaker 1>see the same thing with the touch screen text for

0:43:50.960 --> 0:43:54.040
<v Speaker 1>certain types of electronics, but for things like mobile devices,

0:43:54.239 --> 0:43:57.160
<v Speaker 1>it totally makes sense, and I expect we will continue

0:43:57.160 --> 0:44:01.520
<v Speaker 1>to see uh it used there and improve in that implementation.

0:44:02.160 --> 0:44:04.960
<v Speaker 1>And that wraps up this discussion about touch screens. Obviously

0:44:05.000 --> 0:44:07.320
<v Speaker 1>I could have gone into a lot more detail about

0:44:07.360 --> 0:44:09.600
<v Speaker 1>each of those, but that would have required a whole

0:44:09.600 --> 0:44:13.040
<v Speaker 1>mini series on it, and honestly, I'm not sure that

0:44:13.480 --> 0:44:16.760
<v Speaker 1>that I could do all of that without losing my mind.

0:44:17.400 --> 0:44:20.120
<v Speaker 1>So we're gonna wrap up this episode. If you guys

0:44:20.160 --> 0:44:23.560
<v Speaker 1>have suggestions for future episodes, you can write me the

0:44:23.640 --> 0:44:26.759
<v Speaker 1>email addresses tech Stuff at how stuff works dot com.

0:44:26.840 --> 0:44:30.319
<v Speaker 1>You can drop by the website that's tech stuff podcast

0:44:30.480 --> 0:44:33.200
<v Speaker 1>dot com. There you're gonna find an archive of all

0:44:33.239 --> 0:44:36.600
<v Speaker 1>of our shows, including the two thousand nine episode where

0:44:36.640 --> 0:44:38.839
<v Speaker 1>I first talked about touch screens with my co host

0:44:38.960 --> 0:44:41.960
<v Speaker 1>Chris Palette, as well every other episode of tech Stuff.

0:44:42.000 --> 0:44:44.839
<v Speaker 1>You'll also find links to our social media presence and

0:44:44.960 --> 0:44:47.480
<v Speaker 1>a link to our online store, where every purchase you

0:44:47.560 --> 0:44:50.440
<v Speaker 1>make goes to help the show, and we greatly appreciate it,

0:44:50.800 --> 0:44:59.319
<v Speaker 1>and I will talk to you again really soon. Text

0:44:59.320 --> 0:45:01.959
<v Speaker 1>Stuff is a action of i heart Radio's How Stuff Works.

0:45:02.200 --> 0:45:05.000
<v Speaker 1>For more podcasts from I heart Radio, visit the i

0:45:05.120 --> 0:45:08.359
<v Speaker 1>heart Radio app, Apple Podcasts, or wherever you listen to

0:45:08.400 --> 0:45:09.320
<v Speaker 1>your favorite shows.