WEBVTT - An Autopsy of Apple's Vision Pro

0:00:02.240 --> 0:00:03.320
<v Speaker 1>All Zone Media.

0:00:05.440 --> 0:00:08.520
<v Speaker 2>Welcome to Better Offline. I'm ed Zetron. This is a

0:00:08.520 --> 0:00:11.080
<v Speaker 2>weekly tech podcast where I break down the ways in

0:00:11.119 --> 0:00:14.480
<v Speaker 2>which the tech industry, and in particular big tech, is

0:00:14.520 --> 0:00:17.080
<v Speaker 2>trying to change the future for better or for worse.

0:00:17.360 --> 0:00:19.560
<v Speaker 2>And in the case of Apple, a company worth nearly

0:00:19.600 --> 0:00:22.760
<v Speaker 2>three trillion dollars, it's a little bit of both.

0:00:34.000 --> 0:00:34.360
<v Speaker 1>You see.

0:00:34.360 --> 0:00:37.400
<v Speaker 2>It took me fifteen minutes and two restarts to try

0:00:37.400 --> 0:00:40.320
<v Speaker 2>and rename the title of the script. I'm currently reading

0:00:40.360 --> 0:00:44.000
<v Speaker 2>you the Vision Pro, Apple's latest device and their first

0:00:44.040 --> 0:00:47.559
<v Speaker 2>real new computer since the iPad, released in early February

0:00:47.600 --> 0:00:50.839
<v Speaker 2>of this year, and it's a three five hundred special

0:00:50.880 --> 0:00:55.440
<v Speaker 2>computer which, to quote Apple's marketing literature, you navigate simply

0:00:55.520 --> 0:01:00.160
<v Speaker 2>with your eyes, hands and voice. This device refused. It's

0:01:00.240 --> 0:01:02.400
<v Speaker 2>time and time again to let me select the part

0:01:02.440 --> 0:01:04.920
<v Speaker 2>of the document in Google Dogs that I wanted to

0:01:04.959 --> 0:01:09.160
<v Speaker 2>look and point and grab. Theoretically, I was meant to

0:01:09.160 --> 0:01:11.360
<v Speaker 2>look at it with my eyes and then it would

0:01:11.400 --> 0:01:13.080
<v Speaker 2>go to the place I wanted it to go, and

0:01:13.120 --> 0:01:15.360
<v Speaker 2>then I'd tap my fingers and then I'd select it

0:01:15.760 --> 0:01:19.200
<v Speaker 2>and then type things in. That's not what happens. You

0:01:19.240 --> 0:01:23.039
<v Speaker 2>can probably guess. I assumed at first that this was

0:01:23.040 --> 0:01:25.560
<v Speaker 2>potentially due to a poor fit. So I pulled the

0:01:25.680 --> 0:01:29.240
<v Speaker 2>vision Pro off my head, I adjusted the strap, I

0:01:29.319 --> 0:01:33.000
<v Speaker 2>put it back on, and I saw nothing, only the

0:01:33.080 --> 0:01:36.120
<v Speaker 2>vision Pro showing me the world around me. No menus,

0:01:36.800 --> 0:01:39.440
<v Speaker 2>nothing was projected on the one thing this device was

0:01:39.480 --> 0:01:42.520
<v Speaker 2>meant to do it was not doing. This is a

0:01:42.520 --> 0:01:45.360
<v Speaker 2>bug that's happened to me at least five different times,

0:01:46.080 --> 0:01:49.160
<v Speaker 2>and this entire experience is indicative of what the vision

0:01:49.200 --> 0:01:53.680
<v Speaker 2>Pro is simultaneously the single most interesting and annoying piece

0:01:53.680 --> 0:01:58.000
<v Speaker 2>of technology ever made. Practically speaking, the vision Pro is

0:01:58.040 --> 0:02:00.800
<v Speaker 2>a head worn computer that attaches eye with a single

0:02:01.120 --> 0:02:03.960
<v Speaker 2>band rap called the solo band, which adjusts with a

0:02:03.960 --> 0:02:05.880
<v Speaker 2>little wheel. It kind of goes around the back of

0:02:05.920 --> 0:02:08.320
<v Speaker 2>your head and you turn it to tighten it, or

0:02:08.360 --> 0:02:11.560
<v Speaker 2>the dual loop band, which adjusts with two extremely basic

0:02:11.639 --> 0:02:16.560
<v Speaker 2>velcro straps. It feels very unapple, but it works. The

0:02:16.560 --> 0:02:19.440
<v Speaker 2>headset itself features a big sheet of glass and metal

0:02:19.520 --> 0:02:21.920
<v Speaker 2>with a series of cameras and sensors for measuring the

0:02:21.960 --> 0:02:25.280
<v Speaker 2>space around you, letting you see the world through pass

0:02:25.320 --> 0:02:28.040
<v Speaker 2>through technology. This is a fancy way of saying that

0:02:28.080 --> 0:02:30.680
<v Speaker 2>there are cameras that show your surroundings and it's pretty

0:02:30.720 --> 0:02:34.680
<v Speaker 2>good perspective wise. It feels realistic. You can grab a drink,

0:02:35.040 --> 0:02:38.359
<v Speaker 2>you can pet a cat, as I have many times.

0:02:38.360 --> 0:02:41.400
<v Speaker 2>Inside there's even more cameras and there's two four k

0:02:41.840 --> 0:02:46.560
<v Speaker 2>O lead screens that's organic LED kind of see it

0:02:46.560 --> 0:02:50.799
<v Speaker 2>in fancy high end TVs, particularly ones by LG. And

0:02:51.440 --> 0:02:54.240
<v Speaker 2>these OLED screens are how you see the vision pros

0:02:54.320 --> 0:02:58.120
<v Speaker 2>operating system, which is projected onto the world in front

0:02:58.160 --> 0:03:01.400
<v Speaker 2>of you, and the thing that actually blocks out the

0:03:01.480 --> 0:03:04.080
<v Speaker 2>light around you, that actually puts the vision Pro against

0:03:04.080 --> 0:03:06.799
<v Speaker 2>your face close enough so it works. It's called a

0:03:06.880 --> 0:03:08.840
<v Speaker 2>light seal and it clips on with a bit of

0:03:08.919 --> 0:03:14.480
<v Speaker 2>magnets and it's strange. It's really weird and it kind

0:03:14.520 --> 0:03:17.920
<v Speaker 2>of works, but not regularly enough for me to recommend.

0:03:18.400 --> 0:03:20.480
<v Speaker 2>One would think you could just buy this thing, and

0:03:20.520 --> 0:03:24.919
<v Speaker 2>you'd be incorrect. You can't just order a vision Pro no, no,

0:03:24.919 --> 0:03:27.520
<v Speaker 2>no no. You have to have an iPhone or an

0:03:27.520 --> 0:03:30.639
<v Speaker 2>iPad with face ID, which is the scanner that allows

0:03:30.639 --> 0:03:33.200
<v Speaker 2>you to unlock your phone or your iPad and you

0:03:33.240 --> 0:03:36.320
<v Speaker 2>scan your face before you can order it so that

0:03:36.360 --> 0:03:39.080
<v Speaker 2>they can tell you the right size light seal face rest,

0:03:39.120 --> 0:03:41.200
<v Speaker 2>which is the little cushion that goes inside the light

0:03:41.240 --> 0:03:45.760
<v Speaker 2>seal and headstrap. Now you're probably hearing this and thinking, man,

0:03:45.800 --> 0:03:47.920
<v Speaker 2>I hope they don't get that wrong, and you're completely

0:03:48.000 --> 0:03:50.840
<v Speaker 2>right to worry about that. My first scan gave me

0:03:50.880 --> 0:03:53.640
<v Speaker 2>a light seal that didn't really seem right, so I

0:03:53.680 --> 0:03:55.640
<v Speaker 2>scanned it again a day later and got a larger

0:03:55.720 --> 0:04:01.480
<v Speaker 2>light seal, which costs three hundred dollars. This sucks, and

0:04:01.520 --> 0:04:05.120
<v Speaker 2>it's the least Apple experience I've ever seen. It's the

0:04:05.120 --> 0:04:08.720
<v Speaker 2>hallmark of a product rushed out without any real planning

0:04:08.840 --> 0:04:13.240
<v Speaker 2>or thought. I had to scrape through Reddit to find

0:04:13.240 --> 0:04:15.320
<v Speaker 2>out what to do with this thing, and apparently there

0:04:15.360 --> 0:04:18.480
<v Speaker 2>is a way of swapping this. I cannot find anything

0:04:18.520 --> 0:04:23.760
<v Speaker 2>from Apple themselves about doing so. Nevertheless, you scan, you

0:04:23.880 --> 0:04:25.880
<v Speaker 2>tell it if you have any vision issues, You tell

0:04:25.920 --> 0:04:28.559
<v Speaker 2>it if you need optical inserts, and then you provide

0:04:28.600 --> 0:04:30.880
<v Speaker 2>them with your prescription if you do, and then you

0:04:31.000 --> 0:04:33.960
<v Speaker 2>order the bloody thing three and a half thousand dollars.

0:04:34.440 --> 0:04:37.120
<v Speaker 2>And that's just for starters, two hundred and fifty six

0:04:37.160 --> 0:04:39.640
<v Speaker 2>gigabytes of memory in there, going all the way up

0:04:39.680 --> 0:04:44.240
<v Speaker 2>to one terror byte, approaching four thousand dollars. When you

0:04:44.279 --> 0:04:47.640
<v Speaker 2>get the device. It isn't small, but it definitely isn't

0:04:47.680 --> 0:04:52.120
<v Speaker 2>as bulky or awkward as say Innoculus Quest or an

0:04:52.279 --> 0:04:56.720
<v Speaker 2>HDC vive or a steam Index, which are all virtual

0:04:56.760 --> 0:05:01.040
<v Speaker 2>reality headsets. It took about half an hour of messing

0:05:01.040 --> 0:05:03.440
<v Speaker 2>with it for me to find something comfortable. This thing

0:05:03.520 --> 0:05:05.919
<v Speaker 2>is not light, though, and you put it on and

0:05:05.960 --> 0:05:08.480
<v Speaker 2>you can definitely feel it on there. The solo strap,

0:05:08.480 --> 0:05:11.960
<v Speaker 2>in my opinion, is useless. It's uncomfortable, it does not

0:05:12.040 --> 0:05:14.480
<v Speaker 2>hold it on right, but the dual strap is actually

0:05:14.480 --> 0:05:17.440
<v Speaker 2>pretty good. Nevertheless, it took me about half an hour

0:05:17.520 --> 0:05:20.160
<v Speaker 2>of messing around with it to make it comfortable and

0:05:20.279 --> 0:05:23.920
<v Speaker 2>make it actually feel right. But when you get there,

0:05:25.200 --> 0:05:29.360
<v Speaker 2>it kind of just works. It's different from every other

0:05:29.520 --> 0:05:34.080
<v Speaker 2>VR virtual reality in AR augmented reality experience that I've

0:05:34.080 --> 0:05:37.719
<v Speaker 2>ever had. You put it on, you turn it on,

0:05:38.560 --> 0:05:42.760
<v Speaker 2>and it powers on sort of. The initial setup of

0:05:42.760 --> 0:05:44.960
<v Speaker 2>the Vision Pro requires you to look at your hands,

0:05:45.040 --> 0:05:47.360
<v Speaker 2>then look at several colored spots hanging in the ether

0:05:47.720 --> 0:05:50.479
<v Speaker 2>all around your vision, and you tap with your fingers,

0:05:50.480 --> 0:05:52.480
<v Speaker 2>which you can see with the cameras on the outside

0:05:52.480 --> 0:05:55.960
<v Speaker 2>of the device. Once that's done, you're presented with a

0:05:56.000 --> 0:06:00.640
<v Speaker 2>slate of pretty familiar apps, messages, notes, email, and so

0:06:00.760 --> 0:06:02.919
<v Speaker 2>on and so forth, all things that you would have

0:06:02.920 --> 0:06:05.400
<v Speaker 2>seen on your iPhone or your Mac or your iPad.

0:06:06.880 --> 0:06:09.920
<v Speaker 2>When I say you're presented or you see these apps,

0:06:10.560 --> 0:06:13.360
<v Speaker 2>what I actually mean is the Vision Pro projects these

0:06:13.440 --> 0:06:16.160
<v Speaker 2>onto the world around you. They are it's almost as

0:06:16.160 --> 0:06:19.159
<v Speaker 2>if they're physically there, but they're not really. It's all

0:06:19.200 --> 0:06:22.920
<v Speaker 2>computer magic. The screen is sharp, the text is smooth,

0:06:22.920 --> 0:06:24.919
<v Speaker 2>the icons are rich with color, and they all have

0:06:24.960 --> 0:06:27.240
<v Speaker 2>a satisfying pop when you look at them, because that's

0:06:27.240 --> 0:06:29.960
<v Speaker 2>how you really navigate this device. So you look at

0:06:29.960 --> 0:06:32.800
<v Speaker 2>an icon, you tap your fingers and then that opens

0:06:32.839 --> 0:06:35.360
<v Speaker 2>it up. You navigate through pages, say, if you're looking

0:06:35.360 --> 0:06:37.160
<v Speaker 2>at I don't know, a Google doc like the one

0:06:37.160 --> 0:06:39.159
<v Speaker 2>I'm looking at right now, and you pinch and you

0:06:39.240 --> 0:06:41.360
<v Speaker 2>hold your fingers and then you move them up and down.

0:06:41.880 --> 0:06:44.440
<v Speaker 2>It feels kind of cool. And this is all done

0:06:44.440 --> 0:06:46.920
<v Speaker 2>because the vision Broken see your hands by your side,

0:06:47.600 --> 0:06:49.520
<v Speaker 2>and they can see where you're looking at. They actually

0:06:49.520 --> 0:06:53.120
<v Speaker 2>look at your eyes using cameras inside the device. Theoretically speaking,

0:06:53.680 --> 0:06:57.679
<v Speaker 2>you can just use this device with your hands and eyes. Essentially,

0:06:57.720 --> 0:07:01.640
<v Speaker 2>the world's your desktop. You open Safari, messages, whatever else.

0:07:02.000 --> 0:07:05.600
<v Speaker 2>You move those windows around by pinching them, and say

0:07:05.680 --> 0:07:08.760
<v Speaker 2>you underneath everything you're looking at, say a web browser,

0:07:08.920 --> 0:07:11.040
<v Speaker 2>there's a little dot and there's a little line. The

0:07:11.040 --> 0:07:13.760
<v Speaker 2>little dot lets you close it by pinching, and the

0:07:13.800 --> 0:07:16.600
<v Speaker 2>little line lets you grab it and move it around space.

0:07:16.680 --> 0:07:20.360
<v Speaker 2>You can have a theoretically infinite desktop space. You can

0:07:20.400 --> 0:07:22.840
<v Speaker 2>also resize things by looking at the corner of a

0:07:22.880 --> 0:07:25.400
<v Speaker 2>window and kind of moving your hands up and down.

0:07:26.240 --> 0:07:28.880
<v Speaker 2>This all sounds quite weird when you're in the experience,

0:07:28.920 --> 0:07:34.040
<v Speaker 2>it's quite accurate. When it works. It's genuinely magical. It's

0:07:34.080 --> 0:07:37.480
<v Speaker 2>a functional workspace that turns basically anywhere you are into

0:07:37.520 --> 0:07:42.040
<v Speaker 2>a huge desktop, resizing windows by grabbing the corners, throwing

0:07:42.080 --> 0:07:46.480
<v Speaker 2>things around. It feels satisfying, it feels futuristic. Apple has

0:07:46.720 --> 0:07:51.400
<v Speaker 2>on some level delivered a consumer friendly augmented reality experience

0:07:51.440 --> 0:07:56.880
<v Speaker 2>that anyone can use. It's really exciting when it works. Sadly,

0:07:57.480 --> 0:08:01.400
<v Speaker 2>that's a load bearing when now you may be hearing

0:08:01.440 --> 0:08:04.240
<v Speaker 2>all this and saying, wow, that sounds amazing. Moving things

0:08:04.280 --> 0:08:08.240
<v Speaker 2>around with my hands and my eyes. How innovative. But

0:08:08.280 --> 0:08:11.320
<v Speaker 2>what if I need to write an email. The first

0:08:11.360 --> 0:08:13.360
<v Speaker 2>thing to realize about the vision pro is that has

0:08:13.400 --> 0:08:16.640
<v Speaker 2>the single worst keyboard I have used on a modern

0:08:16.680 --> 0:08:20.960
<v Speaker 2>consumer device. And remember, Apple once made a keyboard so

0:08:21.360 --> 0:08:23.520
<v Speaker 2>bad it ended up on the receiving end of a

0:08:23.520 --> 0:08:27.640
<v Speaker 2>class action lawsuit, of course, talking about the Butterfly keyboard

0:08:27.680 --> 0:08:30.480
<v Speaker 2>of the twenty fifteen to twenty twenty era MacBooks that

0:08:30.840 --> 0:08:35.800
<v Speaker 2>really sucked and cost Apple millions to settle. And that keyboard, well,

0:08:35.840 --> 0:08:38.520
<v Speaker 2>I mean compared to the Vision Pro, that thing's a

0:08:38.559 --> 0:08:43.400
<v Speaker 2>bloody masterpiece. The Vision Pro's keyboard is so poorly devised,

0:08:43.679 --> 0:08:48.640
<v Speaker 2>so horribly executed, and so offensively unfit for the task

0:08:48.880 --> 0:08:52.199
<v Speaker 2>that I cannot understand how this device was allowed to

0:08:52.280 --> 0:08:55.840
<v Speaker 2>launch with it. Typing involves either selecting the keys and

0:08:55.880 --> 0:08:58.320
<v Speaker 2>the keyboard by looking at them and then pitching or

0:08:58.880 --> 0:09:03.000
<v Speaker 2>physically poking at the air like a confused ape, something

0:09:03.000 --> 0:09:06.160
<v Speaker 2>that Steve Jobs himself once said he did not like.

0:09:06.400 --> 0:09:11.160
<v Speaker 2>And that's why MacBooks don't have touch screens. It's ill

0:09:11.240 --> 0:09:13.839
<v Speaker 2>suited for tasks where you need to precisely select something

0:09:13.880 --> 0:09:18.480
<v Speaker 2>from a densely packed group of things. It's awkward, it's ugly,

0:09:18.760 --> 0:09:24.520
<v Speaker 2>it does not work, and it's astonishing that this device

0:09:25.200 --> 0:09:28.880
<v Speaker 2>launched with this. This is enough of a problem that

0:09:28.920 --> 0:09:31.120
<v Speaker 2>they should not have put the vision Pro out into

0:09:31.120 --> 0:09:35.320
<v Speaker 2>the world without a Bluetooth keyboard, which the vision Pro

0:09:35.440 --> 0:09:39.079
<v Speaker 2>does support. This thing is effectively useless for any kind

0:09:39.120 --> 0:09:45.080
<v Speaker 2>of written communication, relying entirely on this horrifying airborne poking

0:09:45.280 --> 0:09:49.400
<v Speaker 2>thing or Siri, a voice based assistant, which, as you

0:09:49.480 --> 0:09:53.080
<v Speaker 2>know from using literally any voice assistant, is a C

0:09:53.240 --> 0:09:56.520
<v Speaker 2>plus replacement for the written word. Anyone with a strong

0:09:56.559 --> 0:09:59.480
<v Speaker 2>accent and mind by comparison, isn't that strong compared to

0:09:59.480 --> 0:10:03.360
<v Speaker 2>say from Scotland. They're probably going to drop a few letters,

0:10:03.440 --> 0:10:06.559
<v Speaker 2>few words and just find themselves deeply frustrated by the

0:10:06.600 --> 0:10:10.480
<v Speaker 2>whole experience. One might think, of course, now that I

0:10:10.640 --> 0:10:15.080
<v Speaker 2>mentioned bluetooth keyboards like Apple's Magic Keyboard, that this would

0:10:15.120 --> 0:10:17.440
<v Speaker 2>solve all the problems. You'd plug this thing in and

0:10:18.240 --> 0:10:20.480
<v Speaker 2>are where you go, you type away, and you'd be

0:10:20.640 --> 0:10:24.679
<v Speaker 2>like fifty to seventy five percent correct. Look, if I

0:10:24.800 --> 0:10:26.880
<v Speaker 2>was making this product, if I was Tim Cook and

0:10:26.920 --> 0:10:28.960
<v Speaker 2>I was putting this bad boy into the world, I

0:10:29.160 --> 0:10:32.600
<v Speaker 2>probably would have thought, well, my keyboard sucks, so I'm

0:10:32.600 --> 0:10:36.040
<v Speaker 2>going to make the best Bluetooth experience anyone's ever seen.

0:10:36.520 --> 0:10:39.840
<v Speaker 2>That's not what Tim Cook did. Look for reasons I

0:10:39.960 --> 0:10:44.120
<v Speaker 2>cannot ascertain the vision pro treats Bluetooth keyboards unlike any

0:10:44.200 --> 0:10:49.880
<v Speaker 2>other device, acting with abject surprise in its existence. You'll

0:10:49.880 --> 0:10:53.079
<v Speaker 2>turn this thing on, connect it, and suddenly blue lines

0:10:53.080 --> 0:10:56.720
<v Speaker 2>will appear on random things on the bar, on safari,

0:10:57.480 --> 0:11:00.679
<v Speaker 2>on a textbox in messages, and it isn't obvious what

0:11:00.720 --> 0:11:02.480
<v Speaker 2>you're meant to do there. You might hit enter and

0:11:02.480 --> 0:11:03.959
<v Speaker 2>you'd think, Okay, this is going to put me in

0:11:04.000 --> 0:11:07.240
<v Speaker 2>the textbox. It doesn't. It isn't obvious what it wants

0:11:07.240 --> 0:11:11.120
<v Speaker 2>to do, and at times it completely freaks out. You'll

0:11:11.120 --> 0:11:14.120
<v Speaker 2>be typing and then the screen will start freaking out

0:11:14.120 --> 0:11:17.240
<v Speaker 2>and selecting different parts or unselecting the place where you

0:11:17.320 --> 0:11:21.079
<v Speaker 2>are currently typing. My theory is that the vision pro

0:11:21.200 --> 0:11:23.520
<v Speaker 2>is still tracking your hands as I mentioned it does

0:11:23.640 --> 0:11:26.960
<v Speaker 2>as you are typing. This suggests the hilarious possibility that

0:11:26.960 --> 0:11:29.640
<v Speaker 2>Apple's engineers did not consider the fact that people use

0:11:29.640 --> 0:11:33.880
<v Speaker 2>their hands to type on keyboards. Writing in a Google

0:11:33.960 --> 0:11:37.120
<v Speaker 2>document as I am reading off of now, as billions

0:11:37.120 --> 0:11:39.720
<v Speaker 2>of people do every day. One of the Web's most

0:11:39.720 --> 0:11:44.640
<v Speaker 2>common tasks is an exercise in frustration. Sometimes the vision

0:11:44.679 --> 0:11:46.880
<v Speaker 2>pro will arbitrarily decide that I need to move the

0:11:47.040 --> 0:11:49.360
<v Speaker 2>entire window, or that I can type, but I cannot

0:11:49.440 --> 0:11:52.040
<v Speaker 2>navigate through the words with the arrow keys, as one

0:11:52.120 --> 0:11:55.280
<v Speaker 2>might do on literally any device from the last twenty years.

0:11:55.640 --> 0:11:58.160
<v Speaker 2>Sometimes it will open the software keyboard while I'm typing

0:11:58.160 --> 0:12:01.760
<v Speaker 2>on the hardware keyboard, getting in the way, physically blocking

0:12:01.760 --> 0:12:04.600
<v Speaker 2>my vision with a keyboard that I don't want to

0:12:04.720 --> 0:12:07.560
<v Speaker 2>use because I'm using a physical one, and then I

0:12:07.640 --> 0:12:09.959
<v Speaker 2>have to close that or move it because sometimes it

0:12:10.000 --> 0:12:13.840
<v Speaker 2>will pop back up. Similarly, when you use I message

0:12:14.080 --> 0:12:17.120
<v Speaker 2>so you're texting features, you have a lot more problems.

0:12:17.240 --> 0:12:19.160
<v Speaker 2>One might think that this would be a simple case

0:12:19.160 --> 0:12:22.160
<v Speaker 2>of looking and then maybe tapping and then typing. What

0:12:22.320 --> 0:12:25.200
<v Speaker 2>actually happens is the vision pro has a minor history

0:12:25.280 --> 0:12:28.320
<v Speaker 2>onic situation, unable to tell whether you'd want to use

0:12:28.320 --> 0:12:31.360
<v Speaker 2>the bluetooth keyboard or the on screen keyboard, or even

0:12:31.400 --> 0:12:35.120
<v Speaker 2>if you want to text. I really cannot make it clearer.

0:12:35.280 --> 0:12:38.440
<v Speaker 2>It is very difficult to just look at a place

0:12:39.320 --> 0:12:41.920
<v Speaker 2>and then start typing and then send a message with

0:12:41.960 --> 0:12:44.760
<v Speaker 2>a Bluetooth keyboard. This is a three and a half

0:12:44.840 --> 0:12:48.880
<v Speaker 2>thousand dollars item. It should be easy. This is the

0:12:49.000 --> 0:12:56.040
<v Speaker 2>easy stuff. Look, look, look. While this may seem petty.

0:12:56.200 --> 0:12:59.280
<v Speaker 2>I just want to be crystal clear. The Apple Vision Pro,

0:12:59.360 --> 0:13:01.840
<v Speaker 2>Apple's first this new kind of computer in some time,

0:13:02.200 --> 0:13:04.920
<v Speaker 2>is incapable of simply letting me type words into a

0:13:04.960 --> 0:13:10.880
<v Speaker 2>document without experiencing some kind of mental breakdown. The user

0:13:10.960 --> 0:13:15.120
<v Speaker 2>interface issues on this thing are remarkably bad. They suggest

0:13:15.160 --> 0:13:18.480
<v Speaker 2>this company simply did not test it in real world cases.

0:13:18.960 --> 0:13:23.040
<v Speaker 2>It feels as if they rushed this out. Apple, a

0:13:23.120 --> 0:13:26.600
<v Speaker 2>company that redefined the computer several times over and likely

0:13:26.640 --> 0:13:29.480
<v Speaker 2>will several times more, has managed to launch a three

0:13:29.480 --> 0:13:33.120
<v Speaker 2>and a half thousand dollars device that its basic level

0:13:33.360 --> 0:13:36.679
<v Speaker 2>cannot let me type words on a fucking page. And

0:13:36.720 --> 0:13:40.280
<v Speaker 2>it's astonishing that this company would launch a product so

0:13:40.440 --> 0:13:44.640
<v Speaker 2>utterly ramshackle in its execution. It isn't clear why, for example,

0:13:44.840 --> 0:13:47.640
<v Speaker 2>I cannot simply type in this document, check my text,

0:13:47.800 --> 0:13:50.599
<v Speaker 2>and then immediately return to the same document without the

0:13:50.679 --> 0:13:53.199
<v Speaker 2>Vision Pro either failing to let me start typing or

0:13:53.280 --> 0:13:56.040
<v Speaker 2>dropping my cursor into the middle of the page. Look,

0:13:56.360 --> 0:14:01.559
<v Speaker 2>these are bugs, obvious, ridiculous bugs. An Apple has shown

0:14:01.800 --> 0:14:05.439
<v Speaker 2>an utter loathing and disrespect for their customers by shipping

0:14:05.440 --> 0:14:09.120
<v Speaker 2>this device with such obvious flaws, And there are plenty

0:14:09.200 --> 0:14:11.920
<v Speaker 2>more too. On taking the device off and putting it

0:14:12.000 --> 0:14:14.560
<v Speaker 2>on again. As I mentioned on the intro, about half

0:14:14.600 --> 0:14:18.280
<v Speaker 2>the time, it'll simply not load the user interface, forcing

0:14:18.280 --> 0:14:20.600
<v Speaker 2>me to do a hard restart of the entire device.

0:14:21.560 --> 0:14:24.600
<v Speaker 2>I've had multiple times where the eye tracking simply didn't work,

0:14:24.640 --> 0:14:28.560
<v Speaker 2>selecting stuff I was clearly not looking at. Apple has

0:14:28.600 --> 0:14:32.800
<v Speaker 2>also rushed ahead without a full app ecosystem, relying on

0:14:32.840 --> 0:14:36.520
<v Speaker 2>compatibility with and I quote millions of iPhone and iPad

0:14:36.560 --> 0:14:38.960
<v Speaker 2>apps that really aren't that compatible with it at all,

0:14:39.400 --> 0:14:42.160
<v Speaker 2>including chatap signal, which requires you to take a picture

0:14:42.160 --> 0:14:45.560
<v Speaker 2>of a QR code to connect to your account. Note

0:14:45.560 --> 0:14:47.520
<v Speaker 2>that there is no way to take a picture of

0:14:47.560 --> 0:14:50.760
<v Speaker 2>a QR code that's inside a device that you're looking

0:14:50.760 --> 0:14:55.520
<v Speaker 2>at with your eyes. It's just sad. It's really sad.

0:14:56.440 --> 0:15:00.240
<v Speaker 2>You can't launch something with a facsimile of Slack, a

0:15:00.280 --> 0:15:03.840
<v Speaker 2>workplace piece of software used by millions. But don't worry,

0:15:03.880 --> 0:15:08.360
<v Speaker 2>Microsoft team fans, You're supported. The basic building blocks of

0:15:08.400 --> 0:15:11.520
<v Speaker 2>an app ecosystem are not in place here. There's no

0:15:11.640 --> 0:15:14.680
<v Speaker 2>YouTube app, though YouTubers mentioned that they might build one.

0:15:15.200 --> 0:15:19.200
<v Speaker 2>Netflix no app. It feels as if Apple just thought

0:15:19.480 --> 0:15:22.800
<v Speaker 2>we'll just get this shit out there. Who cares and

0:15:22.840 --> 0:15:27.200
<v Speaker 2>as I've mentioned, well, there's technically Bluetooth keyboard support, Apple

0:15:27.200 --> 0:15:30.440
<v Speaker 2>has done such a lazy, half fast, than thoughtless job

0:15:30.480 --> 0:15:33.760
<v Speaker 2>with it that it's barely an improvement over there regular

0:15:33.760 --> 0:15:38.040
<v Speaker 2>software keyboard unless you can make it work, and that

0:15:38.200 --> 0:15:42.320
<v Speaker 2>is that's in unless. As I've mentioned, there's technically Bluetooth

0:15:42.360 --> 0:15:46.120
<v Speaker 2>keyboard support, but Apple has done such an awful, lazy,

0:15:46.240 --> 0:15:49.080
<v Speaker 2>half fast, and thoughtless job with it that it's only

0:15:49.160 --> 0:15:52.240
<v Speaker 2>somewhat of an improvement over the software keyboard. This is

0:15:52.280 --> 0:16:02.680
<v Speaker 2>the easy stuff, as I've mentioned, So while writing this draft,

0:16:02.800 --> 0:16:05.800
<v Speaker 2>While putting this together, I had quite a few problems

0:16:05.800 --> 0:16:08.240
<v Speaker 2>with Focus. I would pick the thing up, put it on,

0:16:08.480 --> 0:16:10.920
<v Speaker 2>it wouldn't look right. I'd readjust and I could kind

0:16:10.920 --> 0:16:12.960
<v Speaker 2>of get it right, but it just didn't feel consistent.

0:16:13.680 --> 0:16:17.440
<v Speaker 2>Sometimes I'd look and it wouldn't look at the right place,

0:16:17.520 --> 0:16:19.640
<v Speaker 2>For example, when you open the device and you have

0:16:19.680 --> 0:16:23.720
<v Speaker 2>to enter your passcode. Sometimes it just wouldn't accept where

0:16:23.720 --> 0:16:25.800
<v Speaker 2>my eye was looking. I'd look at the top right corner,

0:16:25.960 --> 0:16:29.080
<v Speaker 2>it would look in the middle. I called Apple Support,

0:16:29.880 --> 0:16:32.440
<v Speaker 2>couldn't get through to anyone. I'd book a core, dogged

0:16:32.520 --> 0:16:36.240
<v Speaker 2>someone for five minutes. They're gone. Hung up on me.

0:16:37.480 --> 0:16:39.600
<v Speaker 2>This was within a week of the launch of a

0:16:39.600 --> 0:16:44.000
<v Speaker 2>device that made Apple half a billion dollars. Nevertheless, many

0:16:44.040 --> 0:16:46.160
<v Speaker 2>of the problems I ran into were a result of

0:16:46.240 --> 0:16:49.720
<v Speaker 2>poor fit. I want to be clear how inexcusable it

0:16:49.760 --> 0:16:51.920
<v Speaker 2>is that a major tech product, one that made a

0:16:51.960 --> 0:16:55.440
<v Speaker 2>company hundreds of millions of dollars in a single day,

0:16:55.680 --> 0:16:58.480
<v Speaker 2>could be shipped as poorly as Apple has shipped the

0:16:58.560 --> 0:17:02.400
<v Speaker 2>Vision Pro to try a different sized light seal. An

0:17:02.440 --> 0:17:05.720
<v Speaker 2>essential part of this device is three hundred dollars, and

0:17:05.760 --> 0:17:08.239
<v Speaker 2>the cushions that go inside the light seals cost an

0:17:08.240 --> 0:17:12.480
<v Speaker 2>additional thirty dollars each. I got really lucky. I found

0:17:12.520 --> 0:17:15.399
<v Speaker 2>someone with exactly the same issue as I had on Reddit,

0:17:15.520 --> 0:17:18.800
<v Speaker 2>someone with exactly the same sizes. I scanned my face

0:17:18.840 --> 0:17:20.720
<v Speaker 2>on the day and I got fitted for what Apple

0:17:20.760 --> 0:17:24.520
<v Speaker 2>caused twenty one W. The person on Reddit also had

0:17:24.520 --> 0:17:27.240
<v Speaker 2>this problem. They tried to twenty three W. It was better,

0:17:27.680 --> 0:17:30.520
<v Speaker 2>but a trip to the Apple Store ended up with

0:17:30.560 --> 0:17:34.080
<v Speaker 2>a twenty three N When I tried it, this was

0:17:34.119 --> 0:17:37.800
<v Speaker 2>exactly what I needed. The Vision Pro was now very consistent.

0:17:37.880 --> 0:17:39.640
<v Speaker 2>Every time I put it on it was pretty good.

0:17:40.080 --> 0:17:44.439
<v Speaker 2>Things mostly worked because that's the Vision Pro experience. Now,

0:17:45.440 --> 0:17:47.959
<v Speaker 2>these numbers are of course all nonsense and based on

0:17:48.000 --> 0:17:51.480
<v Speaker 2>some kind of internal calculus that would have made Steve

0:17:51.560 --> 0:17:55.000
<v Speaker 2>Jobs take a hostage. Had I not spent hours trying

0:17:55.040 --> 0:17:57.560
<v Speaker 2>to work out these issues and spending ninety bucks on

0:17:57.600 --> 0:18:00.480
<v Speaker 2>different eye cushions, I would have assumed that the Vision

0:18:00.480 --> 0:18:02.439
<v Speaker 2>Pro was just kind of awkward if you didn't put

0:18:02.480 --> 0:18:05.160
<v Speaker 2>it on right. It turns out it's meant to feel

0:18:05.200 --> 0:18:08.760
<v Speaker 2>a certain way every time, and in many cases I

0:18:08.800 --> 0:18:11.880
<v Speaker 2>think people would simply return it them correct the homework

0:18:11.960 --> 0:18:14.560
<v Speaker 2>of a company with two hundred and fifty billion dollars

0:18:14.600 --> 0:18:17.680
<v Speaker 2>in cash in the bank. I of course was doing

0:18:17.720 --> 0:18:20.800
<v Speaker 2>this review, so I had to get it right. It's

0:18:20.840 --> 0:18:24.080
<v Speaker 2>also ridiculous that I had to, and it's ridiculous that

0:18:24.119 --> 0:18:27.320
<v Speaker 2>Apple does not have a way of checking whether the

0:18:27.359 --> 0:18:29.880
<v Speaker 2>fit is correct. The way the vision Pro is meant

0:18:29.920 --> 0:18:32.240
<v Speaker 2>to work is it's meant to go on and feel

0:18:32.280 --> 0:18:35.080
<v Speaker 2>good immediately. You're not meant to shift the bugger around.

0:18:35.880 --> 0:18:39.320
<v Speaker 2>That's what I found out only through my own experimentation.

0:18:40.119 --> 0:18:43.560
<v Speaker 2>Apple has made very little effort to make sure you

0:18:43.600 --> 0:18:46.560
<v Speaker 2>are using their device properly. This is not aid to

0:18:46.640 --> 0:18:50.199
<v Speaker 2>quote Steve Jobs, You're holding it wrong. Issue. This is

0:18:50.240 --> 0:18:53.399
<v Speaker 2>a you have deployed your launch wrong, mister Cook issue.

0:18:54.440 --> 0:18:58.080
<v Speaker 2>It's a complete disgrace that a company as large as

0:18:58.119 --> 0:19:01.560
<v Speaker 2>Apple could ship a product I add that costs several

0:19:01.560 --> 0:19:05.280
<v Speaker 2>times more than most people pay for rent, requiring such

0:19:05.280 --> 0:19:08.679
<v Speaker 2>a precise fit, and then trusts these measures to a

0:19:08.720 --> 0:19:13.439
<v Speaker 2>phone's face scanner. The difference between a correct fit on

0:19:13.480 --> 0:19:16.159
<v Speaker 2>a vision pro is the difference between the clarity of

0:19:16.200 --> 0:19:18.439
<v Speaker 2>a seven to twenty piece screen, so the kind that

0:19:18.440 --> 0:19:21.040
<v Speaker 2>you would have seen from televisions fifteen or twenty years ago,

0:19:21.240 --> 0:19:23.320
<v Speaker 2>and a four CR screen like you'd see on most

0:19:23.359 --> 0:19:26.479
<v Speaker 2>televisions today. And there's very little out there to tell

0:19:26.520 --> 0:19:30.920
<v Speaker 2>you what right feels like. If Apple was a responsible company,

0:19:31.200 --> 0:19:33.520
<v Speaker 2>they'd demand customers come in to pick up their vision

0:19:33.560 --> 0:19:36.960
<v Speaker 2>pros and get fitted by an Apple genius when they

0:19:36.960 --> 0:19:41.840
<v Speaker 2>did so. Instead of doing the expensive, important hard work

0:19:41.880 --> 0:19:46.399
<v Speaker 2>of building, say satellite fitting appointments, or perhaps a thorough

0:19:46.400 --> 0:19:50.240
<v Speaker 2>remote fitting appointment, Apple would rather burden an indeterminate amount

0:19:50.240 --> 0:19:54.160
<v Speaker 2>of customers with an inferior experience. Imagine if you got

0:19:54.160 --> 0:19:57.359
<v Speaker 2>your laptop and you opened it up and sometimes the

0:19:57.359 --> 0:20:00.800
<v Speaker 2>resolution was wrong, or maybe your eye phone came and

0:20:01.359 --> 0:20:03.840
<v Speaker 2>just the quarter of the screen didn't work, and these

0:20:03.840 --> 0:20:06.320
<v Speaker 2>were all basic settings that had never been put in.

0:20:07.040 --> 0:20:09.359
<v Speaker 2>This is the level of fuck up that Apple has

0:20:09.400 --> 0:20:12.080
<v Speaker 2>made with the Vision Pro, and I think it's important

0:20:12.119 --> 0:20:15.760
<v Speaker 2>that consumers are aware of this look. I don't have

0:20:15.840 --> 0:20:18.240
<v Speaker 2>any data on this subject, but based on even in

0:20:18.280 --> 0:20:21.399
<v Speaker 2>a cursory glance of social media, there are so many

0:20:21.440 --> 0:20:24.520
<v Speaker 2>people who do not know if they're getting the intended

0:20:24.560 --> 0:20:28.720
<v Speaker 2>experience with Apple's Vision Pro. I spent days with this device,

0:20:28.760 --> 0:20:31.640
<v Speaker 2>feeling uncomfortable and trying to make it work in a predictable,

0:20:31.960 --> 0:20:36.439
<v Speaker 2>reliable manner, without success. I did try and schedule a

0:20:36.480 --> 0:20:38.879
<v Speaker 2>call with Apple support, but when I did so, I

0:20:38.960 --> 0:20:41.520
<v Speaker 2>spent five minutes giving them the most basic information about

0:20:41.520 --> 0:20:44.240
<v Speaker 2>my device, like my serial number and all sorts and

0:20:44.320 --> 0:20:48.240
<v Speaker 2>things I'd already tried. At that point, the specialist drop

0:20:48.280 --> 0:20:51.399
<v Speaker 2>my call, dump me back on hold with a chirpy

0:20:51.480 --> 0:20:53.600
<v Speaker 2>voice telling me that a specialist would be right with

0:20:53.640 --> 0:20:56.320
<v Speaker 2>me in a few minutes. After ten minutes, I hung up.

0:20:57.119 --> 0:21:00.320
<v Speaker 2>To be abundantly clear, this was a call I sched

0:21:00.320 --> 0:21:05.480
<v Speaker 2>with Apple several hours beforehand. It's also important to add

0:21:05.480 --> 0:21:08.080
<v Speaker 2>that Apple does allegedly have pop ups that are meant

0:21:08.080 --> 0:21:09.960
<v Speaker 2>to warn you of a poor fit of the vision

0:21:09.960 --> 0:21:13.200
<v Speaker 2>Pro or issues with eye tracking. They never appeared once,

0:21:13.480 --> 0:21:16.320
<v Speaker 2>and I simply assumed that Apple had really not quite

0:21:16.320 --> 0:21:20.359
<v Speaker 2>worked out how to make augmented reality work yet. And

0:21:20.400 --> 0:21:24.280
<v Speaker 2>what's really frustrating about this whole thing is that Apple

0:21:24.400 --> 0:21:30.960
<v Speaker 2>was really really close to doing something quite marvelous. I

0:21:31.000 --> 0:21:33.080
<v Speaker 2>wanted to give you listeners a little more perspective on

0:21:33.119 --> 0:21:34.760
<v Speaker 2>the vision Pro, so I reached out to one of

0:21:34.800 --> 0:21:37.560
<v Speaker 2>the leading tech reviewers in the country. Joanna Stern is

0:21:37.600 --> 0:21:40.080
<v Speaker 2>the Emmy Award winning personal tech columnist at The Wall

0:21:40.119 --> 0:21:42.240
<v Speaker 2>Street Journal and was one of the founding reporters at

0:21:42.280 --> 0:21:46.480
<v Speaker 2>The Verge, another major consumer electronics website. She reviewed the

0:21:46.560 --> 0:21:48.520
<v Speaker 2>vision Pro for the Journal, and I thought it'd be

0:21:48.520 --> 0:21:50.720
<v Speaker 2>great to get her views. Joanna, thank you for joining me.

0:21:51.720 --> 0:21:53.159
<v Speaker 3>Anytime where else would I be?

0:21:53.960 --> 0:21:57.240
<v Speaker 2>Well, maybe that's a good question. Do you plan to

0:21:57.359 --> 0:22:00.480
<v Speaker 2>use your vision Pro past the review period?

0:22:01.680 --> 0:22:02.040
<v Speaker 3>I do?

0:22:02.800 --> 0:22:05.760
<v Speaker 1>I think, I you know, I think I've had it

0:22:05.800 --> 0:22:10.160
<v Speaker 1>now what okay, two weeks with days today, I'm.

0:22:10.119 --> 0:22:12.240
<v Speaker 2>Very prepared for your podcast Wednesday the seventh.

0:22:13.000 --> 0:22:16.320
<v Speaker 1>Okay, so I've actually had it for two weeks. Today

0:22:16.440 --> 0:22:20.359
<v Speaker 1>at five o'clock PM, in one hour from now, I

0:22:20.400 --> 0:22:22.920
<v Speaker 1>will celebrate my two week anniversary with my vision Pro

0:22:23.040 --> 0:22:29.080
<v Speaker 1>review you and we will be together and well, well,

0:22:29.119 --> 0:22:31.600
<v Speaker 1>I won't go there in the augmented world, in the

0:22:31.600 --> 0:22:34.359
<v Speaker 1>augmented world, and so I will say I finished the

0:22:34.440 --> 0:22:37.800
<v Speaker 1>review about a week ago, and I have used it

0:22:37.840 --> 0:22:41.200
<v Speaker 1>for two things since. I will also just caveat saying

0:22:41.280 --> 0:22:44.120
<v Speaker 1>I have been sick and I've been very nauseous without

0:22:44.160 --> 0:22:46.600
<v Speaker 1>the headset on. It's just the sickness that I seem

0:22:46.640 --> 0:22:48.639
<v Speaker 1>to have come down with. So for the last two

0:22:48.760 --> 0:22:50.680
<v Speaker 1>days I've just been like, I do not want to

0:22:50.720 --> 0:22:53.080
<v Speaker 1>go near that thing. But when I recover, I plan

0:22:53.160 --> 0:22:54.640
<v Speaker 1>to put it back on. But the two things i've

0:22:54.720 --> 0:22:58.320
<v Speaker 1>used it for. One is working, so I don't have

0:22:58.359 --> 0:23:01.520
<v Speaker 1>the best monitor at my Wall Street Journal office. I know,

0:23:01.640 --> 0:23:04.800
<v Speaker 1>shocking Leading it was such a glowing intro you did

0:23:04.800 --> 0:23:08.520
<v Speaker 1>for me, but Leading Technology Columnists has crappy monitor, as

0:23:08.640 --> 0:23:10.919
<v Speaker 1>really the headline here, and so I've been using the

0:23:10.960 --> 0:23:12.160
<v Speaker 1>headset to just work.

0:23:12.200 --> 0:23:14.480
<v Speaker 3>I have a very good setup.

0:23:14.119 --> 0:23:17.640
<v Speaker 1>In there with my three different monitors or virtual monitors,

0:23:17.680 --> 0:23:20.440
<v Speaker 1>and I've kind of arranged it the way I like it,

0:23:20.480 --> 0:23:23.440
<v Speaker 1>and I think I'm actually quite productive in there. And

0:23:23.480 --> 0:23:25.960
<v Speaker 1>the second is I've been watching in it. I've been

0:23:26.000 --> 0:23:27.879
<v Speaker 1>watching Beef. Have you watched Beef?

0:23:28.400 --> 0:23:28.760
<v Speaker 2>I've not.

0:23:29.480 --> 0:23:32.480
<v Speaker 1>Now, Yeah, it's pretty it's a crazy show. It's on Netflix,

0:23:33.280 --> 0:23:35.359
<v Speaker 1>and I watched the last two episodes in there.

0:23:36.359 --> 0:23:39.639
<v Speaker 2>So what was the fitting experience? So you, I assume

0:23:39.760 --> 0:23:42.280
<v Speaker 2>got it straight from Apple. Did they do any kind

0:23:42.320 --> 0:23:43.679
<v Speaker 2>of fitting experience with you?

0:23:45.359 --> 0:23:47.800
<v Speaker 1>They did, but it was very similar to the fitting

0:23:47.840 --> 0:23:50.399
<v Speaker 1>experience that anyone else goes through, which was on the app.

0:23:50.760 --> 0:23:53.960
<v Speaker 1>Really that was the you know, I enrolled my face.

0:23:54.000 --> 0:23:56.320
<v Speaker 1>I did this sort of weird head turns looking at

0:23:56.320 --> 0:23:59.600
<v Speaker 1>the phone. It then gives you prediction of what size

0:23:59.600 --> 0:24:01.960
<v Speaker 1>you're going to be, and that was all I really did.

0:24:02.440 --> 0:24:07.920
<v Speaker 1>But no special, no special. I think mine fits pretty well.

0:24:07.920 --> 0:24:11.400
<v Speaker 1>I mean it's really interesting because now, so the first

0:24:11.400 --> 0:24:12.760
<v Speaker 1>week I had it, I really couldn't show it to

0:24:12.800 --> 0:24:14.560
<v Speaker 1>anyone that was part of the agreement with Apple, and

0:24:14.560 --> 0:24:17.200
<v Speaker 1>couldn't really let other people wear it. And then after

0:24:17.280 --> 0:24:20.199
<v Speaker 1>the bargo broke and we were able to start sharing this,

0:24:20.240 --> 0:24:22.240
<v Speaker 1>I had a lot of colleagues want to test it out.

0:24:22.520 --> 0:24:24.520
<v Speaker 1>By the way, I'm convinced that's how I actually got sick,

0:24:24.560 --> 0:24:28.879
<v Speaker 1>because they were all breathing in my face computer and

0:24:29.880 --> 0:24:32.399
<v Speaker 1>when you put it on them, like you can definitely

0:24:32.400 --> 0:24:35.760
<v Speaker 1>see this thing does not fit them right. It's mostly men,

0:24:35.880 --> 0:24:39.439
<v Speaker 1>and they have big heads and you know literally and figuratively,

0:24:39.480 --> 0:24:42.200
<v Speaker 1>and they and they come out of like the demo

0:24:42.240 --> 0:24:44.120
<v Speaker 1>that I've done with them with like a giant red

0:24:44.280 --> 0:24:46.160
<v Speaker 1>stripe on their head, like it looks like they've gone

0:24:46.160 --> 0:24:46.879
<v Speaker 1>scuba diving.

0:24:47.240 --> 0:24:49.399
<v Speaker 3>And I don't have that. I just don't have that.

0:24:49.520 --> 0:24:51.720
<v Speaker 1>I mean, in the initial hands on I did with

0:24:51.760 --> 0:24:55.560
<v Speaker 1>Apple in June at WWDC, I actually did have that.

0:24:55.680 --> 0:25:00.240
<v Speaker 1>I had that like red mark across my forehead and

0:25:01.000 --> 0:25:03.360
<v Speaker 1>you know, thinking back on it, it was probably because

0:25:03.400 --> 0:25:05.720
<v Speaker 1>they hadn't figured out the fitting situation.

0:25:06.720 --> 0:25:09.960
<v Speaker 2>So when I got mine, I had a horrible experience

0:25:10.160 --> 0:25:13.080
<v Speaker 2>my foot four or five days with it. I scanned

0:25:13.080 --> 0:25:14.840
<v Speaker 2>with the app of five in the morning and the

0:25:14.920 --> 0:25:17.720
<v Speaker 2>day you order it and scam my face and it

0:25:17.760 --> 0:25:22.080
<v Speaker 2>gave me twenty one W. I then immediately was checking

0:25:22.119 --> 0:25:23.879
<v Speaker 2>like Reddit and people were saying, oh, I got that.

0:25:24.359 --> 0:25:26.040
<v Speaker 2>I don't know if this is right. And then when

0:25:26.040 --> 0:25:27.720
<v Speaker 2>it came out I put it on, I'm like, this

0:25:27.880 --> 0:25:30.880
<v Speaker 2>is not this does not feel right. So I got

0:25:30.880 --> 0:25:33.840
<v Speaker 2>a twenty three W based on a reddit post, and

0:25:33.880 --> 0:25:36.560
<v Speaker 2>I just every so often I'd put it on and

0:25:36.600 --> 0:25:38.560
<v Speaker 2>it wouldn't feel right. It wasn't be in focused, the

0:25:38.560 --> 0:25:41.800
<v Speaker 2>eye tracking wasn't working. I just assumed it sucked. And

0:25:41.840 --> 0:25:45.119
<v Speaker 2>then scraping through reddit more, I found someone else with

0:25:45.200 --> 0:25:48.520
<v Speaker 2>the same size situation. They said, oh, by the N

0:25:48.640 --> 0:25:52.760
<v Speaker 2>cushion size, and it was night and day. And it

0:25:52.840 --> 0:25:55.320
<v Speaker 2>just feels to me like this is a massive supply

0:25:55.400 --> 0:25:57.560
<v Speaker 2>chain issue that Apple is not considering.

0:25:58.960 --> 0:26:01.040
<v Speaker 1>Or is it that they got the sizing wrong when

0:26:01.080 --> 0:26:01.800
<v Speaker 1>you first did it?

0:26:01.880 --> 0:26:05.400
<v Speaker 2>But that's what I mean. Though, it's the supply chain

0:26:05.520 --> 0:26:08.119
<v Speaker 2>of the actual scan. It almost feels like they should

0:26:08.160 --> 0:26:09.840
<v Speaker 2>not be relying on it. I don't know if you've

0:26:09.840 --> 0:26:12.520
<v Speaker 2>heard of anyone else. I'm not even trying to load

0:26:12.560 --> 0:26:14.920
<v Speaker 2>a question here. Have you heard of anyone else having

0:26:14.960 --> 0:26:15.600
<v Speaker 2>this problem?

0:26:16.240 --> 0:26:18.200
<v Speaker 3>I haven't. I haven't. I mean that's good.

0:26:18.720 --> 0:26:21.240
<v Speaker 1>I mean, so, you know, and they have the two

0:26:21.320 --> 0:26:23.879
<v Speaker 1>and so it was the it's the light seals what

0:26:23.920 --> 0:26:25.120
<v Speaker 1>you're saying, the difference.

0:26:25.160 --> 0:26:27.600
<v Speaker 2>The light seal and the light seal cushion cushion.

0:26:27.880 --> 0:26:31.320
<v Speaker 1>Yeah, yeah, so, and I have two cushions because or

0:26:31.359 --> 0:26:34.680
<v Speaker 1>maybe everyone gets two cushions, but they say you should

0:26:34.760 --> 0:26:37.199
<v Speaker 1>use the bigger light seal cushion if you plan to

0:26:37.480 --> 0:26:38.560
<v Speaker 1>use the lenses, the.

0:26:40.080 --> 0:26:42.000
<v Speaker 3>Prescription lenses. I don't know if I have those.

0:26:42.320 --> 0:26:46.159
<v Speaker 2>I don't. I also only got one one cushion with

0:26:46.240 --> 0:26:47.040
<v Speaker 2>mine when I bought it.

0:26:47.560 --> 0:26:48.000
<v Speaker 3>Mm hmm.

0:26:48.640 --> 0:26:51.600
<v Speaker 1>Yeah, I actually think that I had the extra cushion

0:26:51.640 --> 0:26:55.399
<v Speaker 1>because I had the lenses too, right, which is a

0:26:55.440 --> 0:26:56.240
<v Speaker 1>little comfier.

0:26:56.880 --> 0:27:01.000
<v Speaker 2>But and the thing is, when it's working now, it's great,

0:27:01.440 --> 0:27:03.880
<v Speaker 2>But I feel like the real elephant in the room

0:27:03.960 --> 0:27:09.400
<v Speaker 2>is the keyboard. The keyboard is just astonishingly bad. Yeah, yeah,

0:27:09.760 --> 0:27:12.960
<v Speaker 2>I Steve Jobs. I'm surprised he didn't come out of

0:27:13.000 --> 0:27:16.040
<v Speaker 2>the grave like an angry zombie over this one. It's awful.

0:27:17.640 --> 0:27:20.440
<v Speaker 1>I mean, I assume it's a place that they're definitely looking.

0:27:20.680 --> 0:27:23.280
<v Speaker 1>How do we make a typing experience better there?

0:27:24.080 --> 0:27:24.480
<v Speaker 2>Yeah?

0:27:25.160 --> 0:27:28.680
<v Speaker 1>I think that, like, you know, could they with swiping,

0:27:28.840 --> 0:27:31.399
<v Speaker 1>you know, sort of the swipe inputs.

0:27:31.320 --> 0:27:33.400
<v Speaker 2>Like gesturing in the air almost exactly?

0:27:33.440 --> 0:27:34.960
<v Speaker 3>Would that be better? Probably?

0:27:36.040 --> 0:27:42.000
<v Speaker 2>Right, It's just so weird because the experience feels cool.

0:27:42.320 --> 0:27:45.720
<v Speaker 2>But then you get to the common way of entering

0:27:45.840 --> 0:27:49.480
<v Speaker 2>text into stuff, which is very common and that you

0:27:49.480 --> 0:27:52.000
<v Speaker 2>should be able to do on anything, and it's just

0:27:52.840 --> 0:27:55.600
<v Speaker 2>it almost doesn't feel like an Apple product.

0:27:56.080 --> 0:27:58.040
<v Speaker 1>I know, and you like, I don't know if you've

0:27:58.040 --> 0:28:00.480
<v Speaker 1>had this too, where it's like you can't touch type

0:28:00.600 --> 0:28:03.880
<v Speaker 1>on that right, so you want to like looked out.

0:28:03.920 --> 0:28:05.840
<v Speaker 1>You have to look at this virtual keyboard, but then

0:28:05.880 --> 0:28:09.120
<v Speaker 1>you're looking up to see where your text is going

0:28:09.119 --> 0:28:10.560
<v Speaker 1>in and is it going right. And they have like

0:28:10.600 --> 0:28:12.760
<v Speaker 1>a little thing above the keyboard where you can see

0:28:12.760 --> 0:28:14.560
<v Speaker 1>the text as it's typing out.

0:28:14.720 --> 0:28:17.800
<v Speaker 3>But it's it's all of this. It's just not natural.

0:28:17.840 --> 0:28:20.000
<v Speaker 1>And I even showed in my videos like thank god

0:28:20.040 --> 0:28:22.000
<v Speaker 1>for a real keyboard, and you compare it with Bluetooth,

0:28:22.080 --> 0:28:24.439
<v Speaker 1>so it's like the killer accessory for this is actually

0:28:24.480 --> 0:28:26.520
<v Speaker 1>a you know, ninety nine dollars keyboard that I was

0:28:26.560 --> 0:28:27.119
<v Speaker 1>going to sell you.

0:28:27.480 --> 0:28:29.080
<v Speaker 2>One thing I loved in your review is when you

0:28:29.080 --> 0:28:30.639
<v Speaker 2>said you can have all of this for lo lolo

0:28:30.760 --> 0:28:33.520
<v Speaker 2>price of what five thousand dollars and yet the MacBook

0:28:33.520 --> 0:28:37.640
<v Speaker 2>throw the keyboard, this and that is it just feels

0:28:37.680 --> 0:28:39.960
<v Speaker 2>like the experience is not complete without that keyboard.

0:28:40.000 --> 0:28:42.800
<v Speaker 3>In my opinion, yeah, I agree, I agree.

0:28:42.840 --> 0:28:45.239
<v Speaker 1>I mean, I think it's fine if you're like going

0:28:45.320 --> 0:28:47.880
<v Speaker 1>to just type in one show, right and you're like, Okay,

0:28:47.960 --> 0:28:50.520
<v Speaker 1>let me go to Netflix and type in beef. That's fine,

0:28:50.640 --> 0:28:52.400
<v Speaker 1>or you can use voice to do that. But when

0:28:52.400 --> 0:28:54.280
<v Speaker 1>you are really trying to do something in there, like

0:28:54.320 --> 0:28:56.880
<v Speaker 1>you're trying to type an email or you're I've been.

0:28:56.720 --> 0:28:57.120
<v Speaker 3>Doing a lot.

0:28:57.120 --> 0:28:59.680
<v Speaker 1>I've actually been writing like a ton of stuff. I've

0:28:59.680 --> 0:29:00.440
<v Speaker 1>been riting in there.

0:29:00.880 --> 0:29:03.840
<v Speaker 2>I wrote the four thousand words script for the full

0:29:03.880 --> 0:29:07.160
<v Speaker 2>episode on the Vision Pro. I can't write on a

0:29:07.200 --> 0:29:09.200
<v Speaker 2>laptop sitting down. I have to be at to desk

0:29:09.320 --> 0:29:12.200
<v Speaker 2>otherwise my rat brain doesn't focus properly. But I was

0:29:12.240 --> 0:29:14.000
<v Speaker 2>able to sit on the couch and right this just

0:29:14.120 --> 0:29:18.160
<v Speaker 2>sitting there, and that's remarkable. I find the focus parts remarkable.

0:29:18.640 --> 0:29:20.800
<v Speaker 1>I think that's and some people have been remarking about

0:29:20.800 --> 0:29:24.320
<v Speaker 1>this on social media and various thing pieces. But the

0:29:24.480 --> 0:29:28.840
<v Speaker 1>irony of this being the killer computing platform for just

0:29:28.920 --> 0:29:36.160
<v Speaker 1>two D basically notes or documents, right like, yeah, that's

0:29:36.200 --> 0:29:38.520
<v Speaker 1>what we have gotten. The future is actually just big

0:29:38.560 --> 0:29:40.560
<v Speaker 1>floating documents in our sky.

0:29:41.360 --> 0:29:43.920
<v Speaker 2>Well to that point, do you think that this or

0:29:43.920 --> 0:29:45.760
<v Speaker 2>a device like this is the future.

0:29:47.480 --> 0:29:49.560
<v Speaker 1>So, I mean, look, that's where I kind of took

0:29:49.640 --> 0:29:52.360
<v Speaker 1>my review, and now I've had some distance from it.

0:29:52.400 --> 0:29:55.480
<v Speaker 1>And been able to reflect and again also just thinking

0:29:55.480 --> 0:29:57.200
<v Speaker 1>about where is this going to fit into our lives?

0:29:57.200 --> 0:29:58.840
<v Speaker 1>That that was the number one thing I wanted to

0:29:58.840 --> 0:30:02.040
<v Speaker 1>answer in this review is, Okay, they've made this crazy

0:30:02.040 --> 0:30:04.120
<v Speaker 1>piece of technology. How are we going to use it

0:30:04.160 --> 0:30:05.080
<v Speaker 1>in our daily lives?

0:30:05.640 --> 0:30:06.040
<v Speaker 3>And it just.

0:30:06.040 --> 0:30:09.360
<v Speaker 1>Seems natural, especially when we have these new pieces of tech,

0:30:09.440 --> 0:30:13.840
<v Speaker 1>you know, whether it was the iPhone or smartphones or tablets,

0:30:13.840 --> 0:30:15.400
<v Speaker 1>et cetera, Like we're going to try to do the

0:30:15.440 --> 0:30:19.080
<v Speaker 1>things that we did on other devices first, right, that

0:30:19.160 --> 0:30:21.040
<v Speaker 1>makes sense, Right, We're going to try to work on it,

0:30:21.080 --> 0:30:23.400
<v Speaker 1>We're going to try to watch TV and videos on it,

0:30:23.440 --> 0:30:24.840
<v Speaker 1>like we've been trying to do that with all of

0:30:24.840 --> 0:30:28.600
<v Speaker 1>our personal tech. And so when it comes to like

0:30:28.760 --> 0:30:33.400
<v Speaker 1>changing those things, sure, but like the future for me

0:30:33.520 --> 0:30:35.080
<v Speaker 1>and those things, like we are still going to have

0:30:35.120 --> 0:30:37.680
<v Speaker 1>a good future writing documents on our computers, right, Like

0:30:37.760 --> 0:30:39.360
<v Speaker 1>the whole entire AI.

0:30:40.560 --> 0:30:43.440
<v Speaker 3>Vision right now is to make that easier, working easier.

0:30:43.880 --> 0:30:45.320
<v Speaker 1>So what I was trying to really look at is like,

0:30:45.320 --> 0:30:47.080
<v Speaker 1>we're going to be the things that are just going

0:30:47.160 --> 0:30:49.400
<v Speaker 1>to break out of the mold of the current things

0:30:49.400 --> 0:30:52.040
<v Speaker 1>we do on these devices, and where will it be better?

0:30:52.640 --> 0:30:54.520
<v Speaker 1>And this is where I kind of got into this

0:30:54.600 --> 0:30:57.480
<v Speaker 1>cooking situation which has gone viral and you know now.

0:30:57.520 --> 0:31:00.000
<v Speaker 2>Oh with and just just for listeners if you haven't

0:31:00.200 --> 0:31:03.640
<v Speaker 2>seeing Joanna's review, she is able to place with the

0:31:03.720 --> 0:31:06.160
<v Speaker 2>vision pro, you're able to place timers above things. So

0:31:06.640 --> 0:31:08.720
<v Speaker 2>while cooking she made it what was a pasta dish?

0:31:08.760 --> 0:31:11.280
<v Speaker 1>I believe, yes, yes, And so this has become the

0:31:12.200 --> 0:31:14.840
<v Speaker 1>running joke like, well, did you not know you could

0:31:14.880 --> 0:31:16.800
<v Speaker 1>also set multiple timers on your phone?

0:31:17.160 --> 0:31:17.920
<v Speaker 3>And did you not know?

0:31:18.120 --> 0:31:20.640
<v Speaker 1>And Colbert is you could maybe pipe the audio in here.

0:31:20.920 --> 0:31:23.920
<v Speaker 1>He's now being making fun of me on his late

0:31:24.000 --> 0:31:26.560
<v Speaker 1>night show saying, well, what else would you do by

0:31:26.600 --> 0:31:27.280
<v Speaker 1>two ovens?

0:31:28.280 --> 0:31:31.360
<v Speaker 2>I think Colbert needs to not throw so many stones

0:31:31.360 --> 0:31:35.520
<v Speaker 2>in glasshouses with how deeply unfunny Midnight is. But that's

0:31:35.600 --> 0:31:39.480
<v Speaker 2>a separate podcast. I think that that whole thing has

0:31:39.560 --> 0:31:42.240
<v Speaker 2>really annoyed me as well, not because I'm particularly defensive

0:31:42.240 --> 0:31:44.160
<v Speaker 2>of Apple, but it's like, if you're going to do

0:31:44.280 --> 0:31:48.400
<v Speaker 2>that kind of thing about a new device, there are

0:31:48.480 --> 0:31:50.920
<v Speaker 2>so many that you could have sat with the Oculus

0:31:51.040 --> 0:31:54.040
<v Speaker 2>quest and done the same thing. Oh I get Oh

0:31:54.040 --> 0:31:56.240
<v Speaker 2>I can work out while wearing a headset. Well, I

0:31:56.280 --> 0:31:58.320
<v Speaker 2>can also do that without anything, I can just do

0:31:58.400 --> 0:32:02.000
<v Speaker 2>jumping jacks. You can make that kind of thing. Sure,

0:32:02.560 --> 0:32:05.000
<v Speaker 2>And actually, here's a good question. Do you think that

0:32:05.080 --> 0:32:08.400
<v Speaker 2>this is going to make people more antisocial? Because that

0:32:08.480 --> 0:32:11.120
<v Speaker 2>feels like the weird meme I'm seeing. It's like, oh,

0:32:11.160 --> 0:32:12.800
<v Speaker 2>this is shutting people off from the world.

0:32:13.880 --> 0:32:16.360
<v Speaker 1>Yes, so just let me finish it. Answering the first

0:32:16.360 --> 0:32:18.000
<v Speaker 1>one because I felt like I didn't do it great. No,

0:32:18.400 --> 0:32:20.440
<v Speaker 1>it's my fault. I was going on now, But my

0:32:20.520 --> 0:32:23.440
<v Speaker 1>point in that review, and maybe I haven't articulated this well.

0:32:23.760 --> 0:32:25.880
<v Speaker 1>I've seen a lot of analysis of the review, which

0:32:26.040 --> 0:32:29.360
<v Speaker 1>thank you everyone for spending time reviewing the review. But

0:32:31.120 --> 0:32:34.320
<v Speaker 1>the point was to show things that that aren't the

0:32:34.360 --> 0:32:37.000
<v Speaker 1>typical things, the things that could bring this into the

0:32:37.000 --> 0:32:40.600
<v Speaker 1>future and that actually make things better and change the

0:32:40.640 --> 0:32:42.440
<v Speaker 1>way we use these devices.

0:32:42.880 --> 0:32:43.960
<v Speaker 3>And I felt.

0:32:43.640 --> 0:32:47.440
<v Speaker 1>That that situation with the cooking really illustrated it. Here

0:32:47.480 --> 0:32:50.080
<v Speaker 1>is a real life thing you're doing. It's better to

0:32:50.160 --> 0:32:53.320
<v Speaker 1>actually have this headset on than use your phone because

0:32:53.480 --> 0:32:55.160
<v Speaker 1>you don't have to hold a phone, and cooking with

0:32:55.240 --> 0:32:56.960
<v Speaker 1>your holding a phone, or you know, even touching a

0:32:57.000 --> 0:32:59.280
<v Speaker 1>phone in the kitchen is a pain. Everyone knows that.

0:32:59.720 --> 0:33:03.000
<v Speaker 1>And on top of that, it was just blend. This

0:33:03.080 --> 0:33:06.800
<v Speaker 1>idea of blending the virtual with the real really really

0:33:07.440 --> 0:33:10.040
<v Speaker 1>stuck out to me there, like I have a physical thing.

0:33:10.360 --> 0:33:12.920
<v Speaker 1>It is this part of pasta. It is boiling, and

0:33:12.960 --> 0:33:16.600
<v Speaker 1>I see a digital interface over it. And I'm not

0:33:16.640 --> 0:33:18.640
<v Speaker 1>saying that he needs to be every use case, but

0:33:18.720 --> 0:33:20.600
<v Speaker 1>that is where I felt like, Okay, I can see

0:33:20.600 --> 0:33:23.640
<v Speaker 1>the future. So that is how I would try to

0:33:23.680 --> 0:33:26.440
<v Speaker 1>answer that, Yes, I think this is the future. We

0:33:26.480 --> 0:33:29.479
<v Speaker 1>still need to have the use cases and the apps

0:33:29.520 --> 0:33:31.600
<v Speaker 1>to prove out what those things are going to be.

0:33:32.080 --> 0:33:35.720
<v Speaker 2>The thing I and you kind of glanced at this

0:33:35.760 --> 0:33:38.080
<v Speaker 2>in the review, but I understand why this wouldn't have

0:33:38.120 --> 0:33:41.880
<v Speaker 2>come up, but it's it feels like the apps are

0:33:41.880 --> 0:33:44.960
<v Speaker 2>not there though, like very basic apps are not there,

0:33:45.320 --> 0:33:47.680
<v Speaker 2>YouTube being the obvious one. And there is, by the way,

0:33:47.720 --> 0:33:51.080
<v Speaker 2>a four ninety nine YouTube app that people are hyping

0:33:51.120 --> 0:33:54.520
<v Speaker 2>as a replacement. It's a goddamn web rapper that developers

0:33:54.520 --> 0:33:56.880
<v Speaker 2>should be kicked off the app store anyway, But like

0:33:57.000 --> 0:34:01.760
<v Speaker 2>Slack isn't there, Signal isn't there, Yep, very funny thing.

0:34:01.960 --> 0:34:04.360
<v Speaker 1>Slack is there, but they're there as an iPad app

0:34:04.400 --> 0:34:05.160
<v Speaker 1>and it's horrible.

0:34:05.280 --> 0:34:06.840
<v Speaker 3>The same it's horrible.

0:34:06.960 --> 0:34:09.000
<v Speaker 1>I mean I didn't even have time in the review,

0:34:09.040 --> 0:34:11.000
<v Speaker 1>but like there was a couple of places when I

0:34:11.080 --> 0:34:12.880
<v Speaker 1>was cursing because you cannot select.

0:34:12.960 --> 0:34:15.080
<v Speaker 3>I mean, this is the issue with putting the iPad

0:34:15.120 --> 0:34:15.480
<v Speaker 3>apps in.

0:34:15.560 --> 0:34:18.640
<v Speaker 1>They weren't they were created for touching, right, so you

0:34:18.680 --> 0:34:21.200
<v Speaker 1>actually when you're using the Slack app and the vision pro,

0:34:21.280 --> 0:34:23.520
<v Speaker 1>you want to bring it closer to you and then

0:34:23.600 --> 0:34:26.600
<v Speaker 1>actually tap in the air versus using the pincher, you know,

0:34:26.719 --> 0:34:31.080
<v Speaker 1>using the pinch gesture. But no, absolutely, And I look,

0:34:31.120 --> 0:34:34.719
<v Speaker 1>we've seen already momentum this week with YouTube saying they're

0:34:34.760 --> 0:34:37.600
<v Speaker 1>going to create and more apps coming, and chat gybt

0:34:37.719 --> 0:34:40.719
<v Speaker 1>announced like there's going to be some momentum and we're

0:34:40.719 --> 0:34:43.520
<v Speaker 1>going to get some of these apps. But what I'm

0:34:43.600 --> 0:34:45.440
<v Speaker 1>more interested in is like, what are these going to be?

0:34:45.480 --> 0:34:48.000
<v Speaker 1>These ideas of these apps that we don't have right

0:34:48.040 --> 0:34:50.880
<v Speaker 1>now that don't run our computers. I agree we have

0:34:50.960 --> 0:34:52.960
<v Speaker 1>to have those other ones, because hey, how do we

0:34:53.000 --> 0:34:54.200
<v Speaker 1>work in there if we don't have Slack?

0:34:54.200 --> 0:34:56.520
<v Speaker 3>I mean, how do you work without Slack? It's impossible.

0:34:57.320 --> 0:34:58.000
<v Speaker 3>I'm just joking.

0:34:58.040 --> 0:35:00.959
<v Speaker 1>I don't really I'm a major Slack user, but would

0:35:00.960 --> 0:35:04.960
<v Speaker 1>happily use anything else to work. So I think those

0:35:04.960 --> 0:35:09.040
<v Speaker 1>are those things will come with time. But on the

0:35:09.040 --> 0:35:12.520
<v Speaker 1>isolation thing, I think that's so. That is the number

0:35:12.600 --> 0:35:15.319
<v Speaker 1>one reason I have not picked it up more, and

0:35:15.440 --> 0:35:17.880
<v Speaker 1>I think might end up being part of you know,

0:35:18.560 --> 0:35:21.320
<v Speaker 1>what happens after this first wave of real big interest

0:35:21.920 --> 0:35:22.840
<v Speaker 1>is do you feel.

0:35:22.640 --> 0:35:25.200
<v Speaker 2>Like something I'd ever use around a person exactly?

0:35:25.400 --> 0:35:27.520
<v Speaker 3>And I live with a person. I don't. I don't

0:35:27.560 --> 0:35:28.440
<v Speaker 3>know about you. I love.

0:35:28.960 --> 0:35:30.799
<v Speaker 1>Yeah, I live with with my wife and I live

0:35:30.840 --> 0:35:32.480
<v Speaker 1>with two kids, so I live with like a lot

0:35:32.520 --> 0:35:35.279
<v Speaker 1>of things at a dog and there's a lot of

0:35:35.280 --> 0:35:38.760
<v Speaker 1>things going on in here. And I had this situation

0:35:38.800 --> 0:35:40.680
<v Speaker 1>this weekend. I was like, I'd love to watch another

0:35:40.680 --> 0:35:43.640
<v Speaker 1>episode of The Beef in here, but my wife is

0:35:43.680 --> 0:35:46.040
<v Speaker 1>sitting right here. I'm going to put this on on

0:35:46.080 --> 0:35:49.360
<v Speaker 1>the couch and she's going to do what right? And

0:35:49.440 --> 0:35:51.880
<v Speaker 1>then you start to think like dystopian, like, oh, what

0:35:51.920 --> 0:35:54.279
<v Speaker 1>if we both had them and we both sat here

0:35:54.320 --> 0:35:58.319
<v Speaker 1>with these on looking at the wall. Eh, I don't

0:35:58.320 --> 0:36:00.480
<v Speaker 1>even if that was an amazing experience, is that what

0:36:00.520 --> 0:36:01.719
<v Speaker 1>I want to do on Saturday night?

0:36:01.800 --> 0:36:04.320
<v Speaker 2>It feels very doesn't feel particularly intimate.

0:36:05.040 --> 0:36:05.960
<v Speaker 3>No.

0:36:05.960 --> 0:36:10.600
<v Speaker 2>No. When mine arrived, I was with my fiance and

0:36:11.160 --> 0:36:12.719
<v Speaker 2>I played with it, but I put a hard cap

0:36:12.760 --> 0:36:16.719
<v Speaker 2>on when I stopped because it felt strange using it

0:36:16.760 --> 0:36:22.239
<v Speaker 2>with another person around it just it felt very much

0:36:22.320 --> 0:36:25.960
<v Speaker 2>like rejecting anyone around me, like I even with passed

0:36:25.960 --> 0:36:28.040
<v Speaker 2>through it felt kind of strange.

0:36:28.880 --> 0:36:32.080
<v Speaker 1>Well, and the pass through thing, while they've done a

0:36:32.120 --> 0:36:35.200
<v Speaker 1>lot more than the others right to put some screen

0:36:35.239 --> 0:36:37.040
<v Speaker 1>on the front, like it's all kind of bullshit, like

0:36:37.719 --> 0:36:40.440
<v Speaker 1>nobody really knows that you're looking at them. If I

0:36:40.520 --> 0:36:43.520
<v Speaker 1>had like a dollar for every time I asked, Hey,

0:36:43.520 --> 0:36:44.759
<v Speaker 1>can you see my eyes in this?

0:36:45.239 --> 0:36:45.520
<v Speaker 2>Yeah?

0:36:45.680 --> 0:36:47.560
<v Speaker 1>Right, Like that's the same thing, and the answer was

0:36:47.600 --> 0:36:49.759
<v Speaker 1>always no, right, the answer is always know and you're

0:36:49.800 --> 0:36:52.000
<v Speaker 1>constantly asking. It's just like, please stop asking me if

0:36:52.000 --> 0:36:52.800
<v Speaker 1>I can see your eyes?

0:36:53.000 --> 0:36:56.920
<v Speaker 2>Like the persona thing is awful? Is I just why

0:36:56.960 --> 0:37:00.359
<v Speaker 2>bother with that? I don't know what they were thinking, king,

0:37:00.680 --> 0:37:04.520
<v Speaker 2>I know that it's this to describe for the listeners,

0:37:05.040 --> 0:37:07.880
<v Speaker 2>it's you scan your face using the vision Pro and

0:37:07.920 --> 0:37:11.000
<v Speaker 2>it spits out a three D clone of your face

0:37:11.040 --> 0:37:14.200
<v Speaker 2>that is not flattering, I should add, yeah, and it

0:37:14.360 --> 0:37:18.000
<v Speaker 2>mimics your facial actions. If someone FaceTime videos you during

0:37:18.080 --> 0:37:19.960
<v Speaker 2>your use of the vision Pro, I just don't I

0:37:20.040 --> 0:37:21.680
<v Speaker 2>know why they did it, but they shouldn't have.

0:37:22.719 --> 0:37:23.279
<v Speaker 3>Yeah, I think.

0:37:23.360 --> 0:37:26.080
<v Speaker 1>Look, I hit on this really hard in my review

0:37:26.120 --> 0:37:30.480
<v Speaker 1>because I had not laughed so hard. I don't remember

0:37:30.480 --> 0:37:32.160
<v Speaker 1>the last time I laughed so hard. When I saw

0:37:32.200 --> 0:37:35.280
<v Speaker 1>my persona, I couldn't. I was like crying of laughter.

0:37:35.360 --> 0:37:37.040
<v Speaker 1>I think it's the funniest thing I've ever seen. It

0:37:37.120 --> 0:37:38.959
<v Speaker 1>just doesn't look like me. And then I would call

0:37:39.000 --> 0:37:41.280
<v Speaker 1>people and they would be laughing, and they would say,

0:37:41.280 --> 0:37:44.800
<v Speaker 1>never call me again looking like this, like, and maybe

0:37:44.800 --> 0:37:45.920
<v Speaker 1>mine was worse than others.

0:37:45.920 --> 0:37:47.200
<v Speaker 3>It seems like to be the case.

0:37:47.640 --> 0:37:49.760
<v Speaker 2>Oh, I have no neck in mine. I will refuse

0:37:49.760 --> 0:37:50.680
<v Speaker 2>to show it to anyone.

0:37:51.200 --> 0:37:54.880
<v Speaker 1>Yeah, I mean, look, most people look bad. I just

0:37:54.920 --> 0:37:57.879
<v Speaker 1>look like I look terrible. I'm another level of bad

0:37:57.920 --> 0:37:58.320
<v Speaker 1>in mine.

0:37:58.840 --> 0:38:01.080
<v Speaker 2>So it makes me look so I used to be

0:38:01.080 --> 0:38:03.440
<v Speaker 2>about one hundred pounds heavier than I currently am about

0:38:03.760 --> 0:38:06.720
<v Speaker 2>buck ninety right now. It makes me look like I

0:38:06.760 --> 0:38:09.359
<v Speaker 2>weigh three hundred pounds, which is not great for myself esteem,

0:38:09.400 --> 0:38:12.520
<v Speaker 2>I should add. But it also looks strange. Yeah, it

0:38:12.520 --> 0:38:13.440
<v Speaker 2>looks very weird.

0:38:14.400 --> 0:38:18.280
<v Speaker 1>It looks strange and like and look, there's a lot

0:38:18.360 --> 0:38:21.080
<v Speaker 1>about they didn't want to go the root of what

0:38:21.200 --> 0:38:23.719
<v Speaker 1>Meta had done, which make us look like cartoons.

0:38:23.800 --> 0:38:24.799
<v Speaker 3>So they're trying to make us.

0:38:24.680 --> 0:38:29.040
<v Speaker 1>Look more realistic and maybe eventually they get there. And

0:38:29.320 --> 0:38:32.360
<v Speaker 1>they clearly they've slapped the beta label on there just

0:38:32.360 --> 0:38:33.799
<v Speaker 1>to make it clear, like we are not.

0:38:33.840 --> 0:38:35.040
<v Speaker 3>Done building this thing.

0:38:36.200 --> 0:38:38.440
<v Speaker 1>I get why they couldn't ship without it, Like, how

0:38:38.440 --> 0:38:41.359
<v Speaker 1>are you going to ship we've just been I actually.

0:38:41.000 --> 0:38:44.879
<v Speaker 2>Can answer that memoji. The memoji works fine. No one

0:38:44.960 --> 0:38:46.759
<v Speaker 2>is going to expect you to do a video call

0:38:46.760 --> 0:38:49.520
<v Speaker 2>well wearing this buddy thing. So do the memoji make

0:38:49.600 --> 0:38:50.400
<v Speaker 2>it fun?

0:38:51.120 --> 0:38:53.480
<v Speaker 1>I agree, I you know, and that's there for the taking.

0:38:53.560 --> 0:38:56.560
<v Speaker 1>Like our iPhones already have memojis that are like mapped

0:38:56.600 --> 0:38:57.160
<v Speaker 1>to our face.

0:38:57.280 --> 0:38:57.920
<v Speaker 3>Like it works.

0:38:58.680 --> 0:38:59.879
<v Speaker 1>I think they didn't want to go to the root

0:38:59.880 --> 0:39:02.560
<v Speaker 1>of Meta, like they didn't want to be competing with

0:39:02.680 --> 0:39:05.080
<v Speaker 1>like Mark Zuckerberg cartoon face, you know.

0:39:05.280 --> 0:39:08.400
<v Speaker 2>Like the irony is that they also released an incomplete

0:39:08.400 --> 0:39:12.640
<v Speaker 2>product that kind of sucks. So who's laughing now, probably

0:39:12.640 --> 0:39:13.959
<v Speaker 2>Mark Zuckerbuck I don't know.

0:39:14.280 --> 0:39:15.880
<v Speaker 1>Right, but I mean, look, on the other hand, we

0:39:16.040 --> 0:39:18.439
<v Speaker 1>just spent ten minutes talking about working in this thing,

0:39:18.719 --> 0:39:20.360
<v Speaker 1>so how are you going to release a device for

0:39:20.480 --> 0:39:22.480
<v Speaker 1>working in this day and age where you should be

0:39:22.480 --> 0:39:24.759
<v Speaker 1>working at your home office and you can't video call

0:39:24.840 --> 0:39:26.760
<v Speaker 1>on it, like you have to have to have something.

0:39:27.760 --> 0:39:31.840
<v Speaker 2>I I don't know. I find the whole thing quite confusing.

0:39:31.920 --> 0:39:33.560
<v Speaker 2>I think you could even just have a still image

0:39:33.560 --> 0:39:35.200
<v Speaker 2>of the person that would do the same job.

0:39:35.440 --> 0:39:37.640
<v Speaker 3>That's true, I don't I don't know why they didn't

0:39:37.680 --> 0:39:37.880
<v Speaker 3>do that.

0:39:38.200 --> 0:39:41.080
<v Speaker 2>So I only got two more questions for you. Do

0:39:41.160 --> 0:39:44.759
<v Speaker 2>you think that Apple rushed this out? No?

0:39:44.960 --> 0:39:50.759
<v Speaker 1>And yes, did they rush this particular version out? No?

0:39:50.920 --> 0:39:54.359
<v Speaker 1>It actually like it works really well, right like, there

0:39:54.360 --> 0:39:57.400
<v Speaker 1>are some small bugs and I'm sure maybe I don't know.

0:39:57.480 --> 0:40:01.320
<v Speaker 2>Selecting on like even Google Docs is extremely broken. Basic

0:40:01.400 --> 0:40:02.640
<v Speaker 2>things like that don't.

0:40:02.400 --> 0:40:06.200
<v Speaker 1>Feel like but that's not so that's where that's a

0:40:06.280 --> 0:40:09.160
<v Speaker 1>design issue, right like that, that's can you navigate the

0:40:09.200 --> 0:40:10.920
<v Speaker 1>whole web with this the way.

0:40:10.719 --> 0:40:11.560
<v Speaker 3>This is designed?

0:40:11.840 --> 0:40:14.239
<v Speaker 2>The only reason I push back on that is you're right,

0:40:14.480 --> 0:40:18.520
<v Speaker 2>the whole web, but Google Docs what billions of uses?

0:40:18.719 --> 0:40:21.640
<v Speaker 2>It just feels The reason I ask is because to me,

0:40:21.680 --> 0:40:24.160
<v Speaker 2>at least, it feels rush because they didn't do their

0:40:24.239 --> 0:40:28.239
<v Speaker 2>due diligence without the developers keep going sorry.

0:40:28.280 --> 0:40:30.759
<v Speaker 1>But then there's the flip side of Hey, these developers

0:40:30.800 --> 0:40:32.880
<v Speaker 1>need to feel and I believe Google will come along

0:40:33.000 --> 0:40:35.560
<v Speaker 1>once they see, oh wow, look we're really seeing an

0:40:36.040 --> 0:40:38.440
<v Speaker 1>x amount of people for x amount of time working here.

0:40:38.520 --> 0:40:42.719
<v Speaker 1>We should probably do something. Right, Microsoft did it. Microsoft

0:40:42.760 --> 0:40:45.200
<v Speaker 1>has apps in there, They have all of almost all

0:40:45.239 --> 0:40:49.040
<v Speaker 1>of Microsoft three sixty five in there, so like they're

0:40:49.040 --> 0:40:51.239
<v Speaker 1>making a bet before it's ready. I think also Microsoft

0:40:51.400 --> 0:40:53.399
<v Speaker 1>has nothing to lose because they don't have their own

0:40:53.400 --> 0:40:54.320
<v Speaker 1>headset coming.

0:40:54.520 --> 0:40:55.960
<v Speaker 3>They've sort of abandoned that.

0:40:56.040 --> 0:40:57.680
<v Speaker 2>Yeah, Holo lens is kind of dead in the war.

0:40:58.120 --> 0:41:00.040
<v Speaker 3>Yeah, but I mean, look I think so.

0:41:00.120 --> 0:41:03.080
<v Speaker 1>But this particular version we all know this is you know,

0:41:03.160 --> 0:41:05.560
<v Speaker 1>this is the first generation. I've actually called it times.

0:41:05.880 --> 0:41:08.400
<v Speaker 1>Is this negative one generation? Should we should this have

0:41:08.480 --> 0:41:10.640
<v Speaker 1>sort of been you know as people have called it

0:41:10.640 --> 0:41:14.320
<v Speaker 1>a dev kid and all of these things. It's certainly

0:41:14.360 --> 0:41:18.279
<v Speaker 1>not a mainstream product, right. The question, like really is

0:41:18.320 --> 0:41:19.840
<v Speaker 1>should they have waited five years?

0:41:20.920 --> 0:41:21.120
<v Speaker 3>Right?

0:41:21.320 --> 0:41:23.960
<v Speaker 1>And would Steve Jobs, as everyone's saying, would he have

0:41:24.000 --> 0:41:26.000
<v Speaker 1>waited the five years? Would you have said, Okay, we've

0:41:26.000 --> 0:41:27.360
<v Speaker 1>got this, so we can do this now, but we

0:41:27.400 --> 0:41:29.520
<v Speaker 1>need to wait five more years until we can slim

0:41:29.560 --> 0:41:31.399
<v Speaker 1>down this and we can make this and we can do.

0:41:31.400 --> 0:41:36.200
<v Speaker 2>This and that's actually my final question for you. How

0:41:36.239 --> 0:41:37.880
<v Speaker 2>do you think Steve Jobs would have done this?

0:41:39.080 --> 0:41:40.960
<v Speaker 3>I was asked this on another podcast. I think.

0:41:42.480 --> 0:41:45.280
<v Speaker 1>I keep thinking about It's funny what you said before.

0:41:45.320 --> 0:41:47.040
<v Speaker 1>You know, you put it on wrong, and or you

0:41:47.040 --> 0:41:49.160
<v Speaker 1>didn't put it on wrong, but you had some issues

0:41:49.200 --> 0:41:52.120
<v Speaker 1>with it, right. And there's the famous Steve Jobs quote, you're.

0:41:51.960 --> 0:41:55.839
<v Speaker 3>Holding it wrong? Yeah right? And so Steve.

0:41:55.640 --> 0:41:59.000
<v Speaker 2>Jobs hated touch screens on laptops because he didn't like

0:41:59.040 --> 0:41:59.799
<v Speaker 2>poking the air.

0:42:00.400 --> 0:42:03.080
<v Speaker 3>Yeah, yes, and here we are.

0:42:04.040 --> 0:42:05.520
<v Speaker 1>But like what he have said to you, you know,

0:42:05.600 --> 0:42:08.279
<v Speaker 1>you're you're wearing it wrong again, and to me too,

0:42:08.320 --> 0:42:10.840
<v Speaker 1>because sometimes I'll put it on and it's like, yeah,

0:42:10.960 --> 0:42:13.320
<v Speaker 1>you know, it's not aligned exactly to my eyes, and

0:42:13.360 --> 0:42:15.200
<v Speaker 1>so if I look at something, it's slightly off and

0:42:15.200 --> 0:42:16.799
<v Speaker 1>then I've got to like change it a.

0:42:16.840 --> 0:42:18.000
<v Speaker 2>Little bit right, right?

0:42:19.400 --> 0:42:20.759
<v Speaker 1>And what have he have been okay with that? Would

0:42:20.760 --> 0:42:22.319
<v Speaker 1>he have said, Nope, We've got to wait. We've got

0:42:22.360 --> 0:42:25.359
<v Speaker 1>to wait a number more years to get this right,

0:42:25.440 --> 0:42:27.080
<v Speaker 1>to get all of these things right into a thing

0:42:27.120 --> 0:42:29.920
<v Speaker 1>that people would wear, or what if you looked at

0:42:29.960 --> 0:42:32.759
<v Speaker 1>it sort of like we've got to get it out there.

0:42:32.880 --> 0:42:35.040
<v Speaker 2>I don't know I don't feel like he was a

0:42:35.120 --> 0:42:37.040
<v Speaker 2>god to get it out that guy. It just feels

0:42:37.080 --> 0:42:42.279
<v Speaker 2>like a very different Apple experience. It lacks it's almost

0:42:42.640 --> 0:42:45.120
<v Speaker 2>fun in the way it lacks it. But when it's

0:42:45.280 --> 0:42:47.760
<v Speaker 2>I feel like, in a like it's kind of funny.

0:42:47.880 --> 0:42:50.600
<v Speaker 2>I guess it's not really fun, but it feels like. Also,

0:42:51.160 --> 0:42:55.160
<v Speaker 2>the format of the vision pro really emphasizes the problems

0:42:55.200 --> 0:42:58.320
<v Speaker 2>when something goes wrong in this environment. It's so claustrophobic.

0:42:58.719 --> 0:43:04.759
<v Speaker 1>Mm hmmmmm. Well, and I think also what we know

0:43:04.880 --> 0:43:08.120
<v Speaker 1>to be true? And I think Neli Petell's review on

0:43:08.160 --> 0:43:10.319
<v Speaker 1>The Verge did a really good job of this is

0:43:10.320 --> 0:43:12.440
<v Speaker 1>what we know to be true? Is what Tim Cook

0:43:12.480 --> 0:43:15.279
<v Speaker 1>sees the vision of this being right. He sees a

0:43:15.360 --> 0:43:20.040
<v Speaker 1>vision of us really at augmented reality type of glasses

0:43:20.080 --> 0:43:22.120
<v Speaker 1>where we can see the real world in this digital

0:43:22.480 --> 0:43:25.440
<v Speaker 1>overlays are there, but to get there they had to

0:43:25.440 --> 0:43:27.359
<v Speaker 1>make a lot of sacrifices in the here and now.

0:43:27.400 --> 0:43:29.520
<v Speaker 1>And so now we have a VR headset that's trying

0:43:29.560 --> 0:43:32.360
<v Speaker 1>to function as an AR mixed reality headset, but it

0:43:32.400 --> 0:43:36.640
<v Speaker 1>really is a VR headset. And again, would Steve Jobs

0:43:36.680 --> 0:43:38.160
<v Speaker 1>have said, Nope, We're just going to wait till we

0:43:38.200 --> 0:43:40.359
<v Speaker 1>get there, we're gonna wait five years, We're gonna wait

0:43:40.400 --> 0:43:41.000
<v Speaker 1>ten years.

0:43:41.920 --> 0:43:45.320
<v Speaker 2>I don't know, Joanna, thank you so much for joining

0:43:45.400 --> 0:43:47.279
<v Speaker 2>me anytime.

0:43:47.400 --> 0:43:48.919
<v Speaker 3>I'd love to see your persona soon.

0:43:49.520 --> 0:43:51.600
<v Speaker 2>Oh God, I will be hiding that from the world.

0:44:08.920 --> 0:44:11.640
<v Speaker 2>All of this comes together to just make it impossible

0:44:12.080 --> 0:44:15.040
<v Speaker 2>to recommend the Vision pro in its current form. It's

0:44:15.080 --> 0:44:19.520
<v Speaker 2>too expensive, its experience is too variable, the supply chain

0:44:19.560 --> 0:44:22.120
<v Speaker 2>and infrastructure to get this thing fitted is too thin,

0:44:22.480 --> 0:44:25.880
<v Speaker 2>and the developer community is just far too sparse. Without

0:44:25.920 --> 0:44:31.080
<v Speaker 2>a Bluetooth keyboard, it's claustrophobic, frustrating, and unproductive. With one,

0:44:31.360 --> 0:44:34.400
<v Speaker 2>it becomes a highly customizable and consistent desktop space that

0:44:34.400 --> 0:44:36.839
<v Speaker 2>I can pop up wherever I am the past through

0:44:36.840 --> 0:44:38.799
<v Speaker 2>feature gives me as much awareness as I needed the

0:44:38.800 --> 0:44:41.279
<v Speaker 2>world around me as i'd like, though not to the

0:44:41.280 --> 0:44:44.040
<v Speaker 2>extent i'd ever use it in public. I can move around,

0:44:44.120 --> 0:44:47.160
<v Speaker 2>I can close things and resize things with tiny gestures,

0:44:47.200 --> 0:44:49.520
<v Speaker 2>and when it works, it looks and feels very cool,

0:44:49.560 --> 0:44:51.520
<v Speaker 2>and it's far more natural than an iPhone or an

0:44:51.560 --> 0:44:54.680
<v Speaker 2>iPad or a magbook. I guess when it works, and

0:44:54.719 --> 0:44:58.120
<v Speaker 2>with the right fit, it's much much more consistent, looking

0:44:58.120 --> 0:45:00.799
<v Speaker 2>and pitching a menu options feels great, and you can

0:45:00.840 --> 0:45:03.000
<v Speaker 2>sweep and move through apps and website like a weird

0:45:03.000 --> 0:45:06.160
<v Speaker 2>little wizard. When it works, I have more space to

0:45:06.200 --> 0:45:08.480
<v Speaker 2>work with than my regular setup, which is a forty

0:45:08.520 --> 0:45:11.160
<v Speaker 2>eight inch curve gaming monitor on a massive L shaped desk.

0:45:11.520 --> 0:45:14.279
<v Speaker 2>But that's when it works. And if you're one of

0:45:14.280 --> 0:45:16.760
<v Speaker 2>the hundreds of thousands of people who bought this, perhaps

0:45:16.800 --> 0:45:19.560
<v Speaker 2>you're listening to this and thinking, oh, it's not meant

0:45:19.560 --> 0:45:22.480
<v Speaker 2>to be this bad, And it isn't. But how the

0:45:22.520 --> 0:45:25.040
<v Speaker 2>hell are you meant to know that? Because Apple certainly

0:45:25.080 --> 0:45:28.160
<v Speaker 2>hasn't tried to make that the case. Apple has not

0:45:28.520 --> 0:45:32.719
<v Speaker 2>put in the time, the energy, and the thought to

0:45:32.800 --> 0:45:37.120
<v Speaker 2>making this the launch it deserved to be. I truly

0:45:37.200 --> 0:45:40.319
<v Speaker 2>believe the Vision Pro could be something revolutionary. It needs

0:45:40.360 --> 0:45:43.200
<v Speaker 2>to be smaller, it needs to be two thousand, if

0:45:43.239 --> 0:45:47.120
<v Speaker 2>not two five hundred dollars cheaper, It needs to have

0:45:47.360 --> 0:45:51.520
<v Speaker 2>the apps. But when it works, it really is something new.

0:45:51.840 --> 0:45:55.120
<v Speaker 2>It is something I will be using a lot. It

0:45:55.200 --> 0:45:58.400
<v Speaker 2>is something that I think could change how we consider computing,

0:45:58.719 --> 0:46:01.520
<v Speaker 2>how we consider the spaces we work in and the

0:46:01.560 --> 0:46:05.480
<v Speaker 2>ways we work in them. And indeed, if Apple actually

0:46:05.520 --> 0:46:09.160
<v Speaker 2>respected their customers, if Apple had the love for their

0:46:09.160 --> 0:46:12.200
<v Speaker 2>customers that I believe they used to have, this wouldn't

0:46:12.200 --> 0:46:15.640
<v Speaker 2>be a problem. None of this would be And I

0:46:15.719 --> 0:46:18.160
<v Speaker 2>just don't think they care enough. And I can't say

0:46:18.160 --> 0:46:22.920
<v Speaker 2>it's worth three five hundred dollars despite its warts. I

0:46:23.000 --> 0:46:25.239
<v Speaker 2>really do plan on keeping my Vision Pro and I'm

0:46:25.239 --> 0:46:27.480
<v Speaker 2>going to use it a great deal, particularly when I'm traveling.

0:46:27.719 --> 0:46:29.920
<v Speaker 2>But for the price of a vision Pro, I can

0:46:29.960 --> 0:46:32.560
<v Speaker 2>get a brand new MacBook Era fifteen inch one, a

0:46:32.680 --> 0:46:35.399
<v Speaker 2>terror By iPhone and still have hundreds of dollars left

0:46:35.400 --> 0:46:38.200
<v Speaker 2>to spare. Well. I love the immersive nature of this

0:46:38.239 --> 0:46:42.320
<v Speaker 2>whole thing. There's nothing it does better, and there's plenty

0:46:42.360 --> 0:46:45.239
<v Speaker 2>of things it can't do at all. There are few

0:46:45.280 --> 0:46:47.600
<v Speaker 2>reasons why the Vision Pro should have shipped in such

0:46:47.680 --> 0:46:50.000
<v Speaker 2>terrible shape, other than the fact that Apple needed to

0:46:50.000 --> 0:46:53.920
<v Speaker 2>show double digit revenue growth to board investors. Apple has

0:46:53.960 --> 0:46:56.480
<v Speaker 2>done very little work to confirm that the very basic

0:46:56.560 --> 0:47:00.239
<v Speaker 2>parts of the Internet work with any reliability. Website that

0:47:00.280 --> 0:47:03.560
<v Speaker 2>you'd expect to be perfect, like Google Docs, like Google itself,

0:47:04.360 --> 0:47:07.279
<v Speaker 2>like Twitter, even are just not ready for this, and

0:47:07.360 --> 0:47:10.279
<v Speaker 2>Apple clearly didn't reach out to any of these providers

0:47:10.440 --> 0:47:14.200
<v Speaker 2>to make sure they did. The app ecosystem marvels the

0:47:14.239 --> 0:47:17.560
<v Speaker 2>iPhone app store when it first launched. The problems I've

0:47:17.600 --> 0:47:20.960
<v Speaker 2>experienced with the Vision Pro are annoying. They're frustrating. They're

0:47:20.960 --> 0:47:23.200
<v Speaker 2>getting a way of an experience I've really wanted to

0:47:23.320 --> 0:47:27.319
<v Speaker 2>enjoy and may indeed enjoy in the future, and it's

0:47:27.360 --> 0:47:30.680
<v Speaker 2>not clear if they're a result of bad quality control

0:47:30.880 --> 0:47:34.600
<v Speaker 2>or the limitations of hardware and software. It really isn't obvious,

0:47:35.280 --> 0:47:38.840
<v Speaker 2>but the problem here is pretty simple. The Vision Pro

0:47:39.400 --> 0:47:43.240
<v Speaker 2>is an intriguing and exciting look into the future, except

0:47:43.239 --> 0:47:46.120
<v Speaker 2>that future is one where a near three trillion dollar

0:47:46.200 --> 0:47:49.960
<v Speaker 2>tech firm ships US beta hardware with alpha software and

0:47:50.080 --> 0:47:52.480
<v Speaker 2>hopes that will thank them for the privilege of helping

0:47:52.520 --> 0:48:05.400
<v Speaker 2>them fix it. I've been at Zeitron. Thank you for

0:48:05.480 --> 0:48:08.719
<v Speaker 2>listening to Better Offline. The editor and composer of the

0:48:08.719 --> 0:48:11.759
<v Speaker 2>Better Offline theme song is Matasowski. You can check out

0:48:11.840 --> 0:48:15.320
<v Speaker 2>more of his music and audio projects at Matasowski dot com,

0:48:15.640 --> 0:48:19.200
<v Speaker 2>M A T T O, S O W s ki

0:48:19.400 --> 0:48:22.040
<v Speaker 2>dot com. You can go to Better Offline dot com

0:48:22.080 --> 0:48:24.879
<v Speaker 2>to find more episodes, find my newsletter, Where's your ad app?

0:48:25.320 --> 0:48:27.280
<v Speaker 2>Or even shoot me an email at easy At Better

0:48:27.320 --> 0:48:31.080
<v Speaker 2>Offline dot com, you can find this podcast on Iheartradios app,

0:48:31.239 --> 0:48:34.520
<v Speaker 2>or anywhere else you find podcasts. Thank you for listening.

0:48:37.600 --> 0:48:40.080
<v Speaker 3>Better Offline is a production of cool Zone Media.

0:48:40.200 --> 0:48:43.040
<v Speaker 2>For more from cool Zone Media, visit our website cool

0:48:43.120 --> 0:48:46.479
<v Speaker 1>Zonemedia dot com, or check us out on the iHeartRadio app,

0:48:46.520 --> 0:49:01.360
<v Speaker 1>Apple Podcasts, or wherever you get your podcasts.