WEBVTT - What will the Internet be like in 2021? 0:00:04.240 --> 0:00:12.200 Get a text technology with tech Stuff from stuff dot com. 0:00:12.240 --> 0:00:14.800 Hey there, and welcome to tex Stuff. I'm your host, 0:00:14.880 --> 0:00:18.080 Jonathan Strickland, and we are going to do a brand 0:00:18.079 --> 0:00:21.919 new Predictions episode. You may remember that the last episode 0:00:21.960 --> 0:00:24.279 I played was a rerun from two thousand eleven where 0:00:24.320 --> 0:00:27.000 Chris Pallette and I decided to kind of guess what 0:00:27.080 --> 0:00:30.680 the Internet would be like in about five years time. Well, 0:00:30.720 --> 0:00:33.320 now we're gonna look another five years into the future. 0:00:33.360 --> 0:00:36.240 And Chris could not be here, but I brought on 0:00:36.479 --> 0:00:39.640 a good friend of mine up here, a guy who 0:00:39.720 --> 0:00:43.320 works for cen Net. Very clever dude, who's got it 0:00:43.400 --> 0:00:46.680 all together. I as actor, How you doing, I'm doing 0:00:46.680 --> 0:00:48.600 really well. Thanks for having me on today. Thanks for 0:00:48.760 --> 0:00:51.880 being on the show. And I as is sounding very formal, 0:00:51.960 --> 0:00:55.279 but trust us. We we're we're buddies. We often give 0:00:55.320 --> 0:00:58.240 each other the business as it were. Of course, of course, 0:00:58.320 --> 0:01:02.440 Mr Strickland, we always give each other business. Uh. Those 0:01:02.560 --> 0:01:06.040 those those plain envelopes filled with dollar bills will continue 0:01:06.080 --> 0:01:08.680 to come to you. I as, so we we wanted 0:01:08.720 --> 0:01:10.760 to take a look and kind of just have a 0:01:10.800 --> 0:01:14.840 casual conversation of what we think the internet and our 0:01:14.880 --> 0:01:18.560 interactions with the Internet might be like in another five years, 0:01:18.560 --> 0:01:22.840 so in twenty twenty one, and uh, we're just kind 0:01:22.880 --> 0:01:25.520 of shooting from the hip here. We're not not really 0:01:26.000 --> 0:01:29.440 consulting any gurus or anything like that, but we did 0:01:29.480 --> 0:01:31.840 come up with a bunch of little questions that we 0:01:31.959 --> 0:01:34.640 thought would be good starters for this kind of thing. 0:01:34.720 --> 0:01:37.400 And one of the points we made in the two 0:01:37.400 --> 0:01:40.800 thousand eleven podcast that Chris and I did was that 0:01:41.200 --> 0:01:44.440 we both felt that mobile browsing was definitely going to 0:01:44.680 --> 0:01:49.960 be increasingly important, that we would see desktops and laptop 0:01:50.040 --> 0:01:54.280 traffic on the Internet get surpassed by mobile devices. And 0:01:54.280 --> 0:01:57.600 in fact, that did happen. And uh, it wasn't like 0:01:57.680 --> 0:02:00.120 we were sticking our next really far out or anything. 0:02:00.120 --> 0:02:02.320 That it was pretty clear that that was the trend 0:02:03.120 --> 0:02:06.240 even when we started back then. Now, I as, do 0:02:06.280 --> 0:02:08.320 you think that's gonna be something that we'll see continue 0:02:08.400 --> 0:02:12.320 That will will mobile devices continue to be one of 0:02:12.360 --> 0:02:16.080 the most important, maybe the predominant way that we interact 0:02:16.120 --> 0:02:20.000 with the Internet, at least on a on an active scale. Yeah, 0:02:20.000 --> 0:02:21.960 I think the mobile devices, I mean, they've shown how 0:02:22.000 --> 0:02:24.200 important they've been over the years. And the thing is, 0:02:24.320 --> 0:02:25.960 for a lot of people of their phone is their 0:02:26.000 --> 0:02:29.960 first real personal computer. So what I'm expecting is essentially 0:02:30.080 --> 0:02:34.120 laptops and desktops not as important, but we might actually 0:02:34.120 --> 0:02:36.920 have the ability to have in five years now where 0:02:36.919 --> 0:02:39.040 you have your phone, it's your brain for all your 0:02:39.040 --> 0:02:42.080 other little systems, because I think other smart devices like 0:02:42.120 --> 0:02:45.320 watching his glasses, other devices and form factors that we've 0:02:45.360 --> 0:02:47.840 even thought up yet, those things will be around, but 0:02:47.880 --> 0:02:51.000 they're really gonna be powered by your phone, right, Yeah, 0:02:51.000 --> 0:02:52.959 So that that makes sense. Like even stuff with Google 0:02:53.000 --> 0:02:55.880 Glass that was something that you used a Bluetooth connection 0:02:55.919 --> 0:02:57.480 with the phone. The phone ended up doing most of 0:02:57.480 --> 0:03:00.680 the processing. The glass was just kind of a interface 0:03:00.720 --> 0:03:04.720 and display, and you still were relying upon the actual 0:03:04.720 --> 0:03:07.440 connection with your phone to grab the data from the cloud. 0:03:07.760 --> 0:03:09.799 And that does make sense. I mean you that way 0:03:09.840 --> 0:03:14.080 you remove the need for the more powerful processors and 0:03:14.160 --> 0:03:17.720 the various antenna that you would require to to tap 0:03:17.760 --> 0:03:20.519 into those networks. You can offload that. You just need 0:03:20.560 --> 0:03:24.960 that Bluetooth interface in order for it to to communicate 0:03:25.040 --> 0:03:29.520 with the devices the real brain. Also, I'm noticing I 0:03:29.560 --> 0:03:32.960 just notice recently a video that kind of blew my 0:03:33.000 --> 0:03:34.920 mind because it reminded me of something we saw at 0:03:35.000 --> 0:03:38.080 CS many years ago, and it was a video of 0:03:38.240 --> 0:03:42.560 a new product where you use your smartphone to act 0:03:42.640 --> 0:03:46.640 as the processor for what was really just a terminal, 0:03:46.720 --> 0:03:49.560 but it looks like, you know, a laptop computer and 0:03:49.600 --> 0:03:52.600 you dock your phone into it and that essentially ends 0:03:52.680 --> 0:03:55.920 up being the brains behind your computer. And I can't 0:03:55.920 --> 0:03:58.720 remember you you might I as I don't know, but 0:03:58.800 --> 0:04:01.520 I can't remember the name of the the thing that 0:04:01.680 --> 0:04:05.720 was essentially that same idea from several years ago where 0:04:06.080 --> 0:04:09.800 your your smartphone and uh could just dock into a 0:04:09.880 --> 0:04:13.960 docking station and power a laptop. Um to me, it 0:04:14.040 --> 0:04:16.599 was interesting to see that idea come back again because 0:04:16.720 --> 0:04:19.560 it didn't seem to go anywhere after that initial c 0:04:19.720 --> 0:04:24.200 e S debut. But it does kind of fall into 0:04:24.240 --> 0:04:28.000 that same idea that the the smartphone will be kind 0:04:28.040 --> 0:04:31.520 of the the center of a of a hub of devices, 0:04:31.680 --> 0:04:34.960 all of which will rely very heavily on it. Yeah, 0:04:34.960 --> 0:04:36.920 the device I think you're talking about the motto atrix, 0:04:37.920 --> 0:04:40.200 a phone that were plug into a docking station that 0:04:40.240 --> 0:04:42.760 kind of makes it a laptop. It wasn't elegant at all. 0:04:42.839 --> 0:04:45.600 It didn't work with every single docking station. Need to 0:04:45.600 --> 0:04:47.880 get a proprietary thing, so that kind of takes people off, 0:04:48.120 --> 0:04:50.359 I know, the Kickstarter you're talking about or Indigogo. Not 0:04:50.400 --> 0:04:53.440 sure which crowd funding site it is, but I mean, well, also, 0:04:53.440 --> 0:04:55.880 I would imagine in five years we would have more 0:04:55.920 --> 0:04:58.200 smart devices that can be on their own. But I 0:04:58.240 --> 0:05:01.080 still think that having a the power and all the 0:05:01.160 --> 0:05:04.360 brains on a singular device driving the other the other 0:05:04.400 --> 0:05:07.880 devices makes more sense because, like you were mentioning other radio's, 0:05:07.880 --> 0:05:11.080 other antennas, other battery concerns. To have all of that 0:05:11.320 --> 0:05:14.720 and each self contained object you're talking about a lot 0:05:14.720 --> 0:05:16.520 of items you have to keep charged all the time, 0:05:16.600 --> 0:05:18.719 it seems like I don't know if five years is 0:05:18.800 --> 0:05:21.520 enough time for this to really get mature. Maybe ten 0:05:21.600 --> 0:05:23.560 years from now and now we're going too far. But 0:05:23.640 --> 0:05:27.200 if battery technology moves ahead, maybe what we would see 0:05:27.440 --> 0:05:30.920 these devices that are I guess cloud connected, So you're 0:05:31.000 --> 0:05:33.520 the brain is still a computer somewhere, it's just nowhere 0:05:33.600 --> 0:05:37.560 near you, right, I think. Also another important element to 0:05:37.600 --> 0:05:41.400 take into account is cost, and by having your phone 0:05:41.480 --> 0:05:45.400 be the primary brains behind all these different devices, it 0:05:45.440 --> 0:05:48.279 helps bring the cost down to each of those individual devices. 0:05:48.279 --> 0:05:52.280 They don't need as many expensive components and that will 0:05:52.320 --> 0:05:56.240 make adoption um less difficult. Right, It's still gonna be 0:05:56.320 --> 0:05:59.920 a barrier, obviously. It's any time we're talking about technology, 0:06:00.320 --> 0:06:03.440 there's a barrier of intrigue that's there. Um. Not everyone 0:06:03.480 --> 0:06:06.719 can afford to do it. But by going that that 0:06:06.839 --> 0:06:11.159 route where your phone remains the primary processing unit of 0:06:11.200 --> 0:06:14.200 all these different devices, you can at least create a 0:06:14.279 --> 0:06:18.880 suite of technologies that aren't prohibitively expensive for all but 0:06:19.000 --> 0:06:22.599 you know the top of the one per centers. Yeah, 0:06:22.600 --> 0:06:24.440 we're talking about a lot of silos, right, you can 0:06:24.440 --> 0:06:27.159 probably like an Apple silo, you'll have a Android silo 0:06:27.240 --> 0:06:30.320 or Samsung silo. There's things that you can't just mix 0:06:30.360 --> 0:06:32.520 and match your accessories. You're just gonna have to get 0:06:33.240 --> 0:06:36.200 one company's to make it work. Well, I still see 0:06:36.240 --> 0:06:39.360 that happening because sometimes I think about in the old days, 0:06:39.400 --> 0:06:42.960 how no standards were ever happened. I couldn't imagine actually 0:06:42.960 --> 0:06:47.120 having one standard port or electrical outlets. If this is privatized, 0:06:47.160 --> 0:06:50.240 weight is now it's like, well, USB A B C 0:06:50.880 --> 0:06:54.440 about three point one. Just it seems so wonky. Yeah, yeah, 0:06:54.880 --> 0:06:57.080 that's a great point. I mean it's and that kind 0:06:57.120 --> 0:06:59.599 of ties into The next question that I have on 0:06:59.600 --> 0:07:03.039 our list the idea of silos, and this whether you 0:07:03.080 --> 0:07:07.520 have interoperability between different you know, families of technologies or 0:07:07.520 --> 0:07:10.120 if it's all within one group. One of the things 0:07:10.200 --> 0:07:13.040 we've seen kind of come to prominence over the last 0:07:13.440 --> 0:07:17.720 year or two is this idea of the digital personal assistant. Now. 0:07:18.120 --> 0:07:20.360 In the two thousand eleven episode, Chris and I talked 0:07:20.400 --> 0:07:23.600 about how voice recognition was going to become more important, 0:07:24.360 --> 0:07:27.760 but it wouldn't take over as our primary means of 0:07:27.760 --> 0:07:31.040 interacting with our technology for various reasons. I mean, if 0:07:31.080 --> 0:07:34.320 you want to search anything that's remotely personal in nature, 0:07:34.320 --> 0:07:38.040 you probably don't want to speak it out loud in public. Also, 0:07:38.360 --> 0:07:40.840 you don't want to make people think you're crazy as 0:07:40.840 --> 0:07:45.640 you're talking to absolutely no one visible at any rate. Um, 0:07:45.680 --> 0:07:49.200 But we're starting to see them really get more more 0:07:49.280 --> 0:07:54.240 traction these days, whether it's Apple's Sirie or Amazon's Alexa, 0:07:54.440 --> 0:07:59.360 or Google's Assistant. You know, we have lots of different examples. 0:07:59.640 --> 0:08:02.560 Do you think those are going to continue to get 0:08:02.680 --> 0:08:07.040 more sophisticated? Are are we going to see more integration 0:08:07.120 --> 0:08:11.320 into various devices, not just the standalonees or the smartphones, 0:08:11.360 --> 0:08:14.160 but perhaps other things as well well. I could see 0:08:14.240 --> 0:08:17.360 people getting very used to talking to the Internet in general. 0:08:17.760 --> 0:08:19.600 Like you might think, now you might look a little 0:08:19.640 --> 0:08:22.640 crazy that you're talking to yourself. Although these days you 0:08:22.680 --> 0:08:24.840 see somebody talking themselves in the street, you're like, do 0:08:24.880 --> 0:08:27.000 they have a Bluetooth headset or not? Because it used 0:08:27.000 --> 0:08:29.200 to be twenty years ago you're like, oh, you're just nuts. 0:08:29.200 --> 0:08:31.240 Now it's like, oh, you might be having a conversation. 0:08:31.480 --> 0:08:34.559 But there's a generation of kids growing up talking to 0:08:34.760 --> 0:08:37.680 smart speakers like the Echo, like Google Home when that 0:08:37.720 --> 0:08:39.800 comes out, and when Apple goes ahead, where there's that 0:08:39.880 --> 0:08:41.800 rumor that they're going to have their own smart speaker. 0:08:42.400 --> 0:08:46.200 I see that kind of interface and that natural language 0:08:46.200 --> 0:08:50.280 really being more important. Now maybe you're not necessarily talking 0:08:50.320 --> 0:08:53.080 to your watch, but you might be writing the same 0:08:53.160 --> 0:08:57.120 kinds of questions that you would say because the way 0:08:57.160 --> 0:09:00.120 everything is changing with deep learning, the chance in five 0:09:00.160 --> 0:09:01.960 years I'm really hoping to five years and you were 0:09:02.000 --> 0:09:04.760 able to just ask a simple question without having to 0:09:04.840 --> 0:09:08.680 have all of these modifiers that are search engine optimized, 0:09:08.720 --> 0:09:10.400 you know what I mean, right, Yeah, without having to 0:09:10.480 --> 0:09:13.400 parse your language in a way that search engines know 0:09:13.600 --> 0:09:16.840 what it is. You're actually asking you to have that 0:09:17.200 --> 0:09:20.240 natural length language recognition. I think we've we've definitely come 0:09:20.280 --> 0:09:24.160 a far away over the last decade, definitely UH with 0:09:24.320 --> 0:09:26.440 natural language where you know, it used to be that 0:09:27.200 --> 0:09:30.839 you could do a Google search for a particular string 0:09:30.880 --> 0:09:33.040 of terms and come up with a page of results 0:09:33.040 --> 0:09:37.320 and think, this isn't remotely what I was hoping to find. 0:09:37.400 --> 0:09:39.680 And then you just go and rearrange the order of 0:09:39.720 --> 0:09:42.240 words that were in your Google query and come up 0:09:42.280 --> 0:09:45.080 with different results and see, oh this is I just 0:09:45.120 --> 0:09:47.800 have to think the way the computer thinks. Once we 0:09:47.840 --> 0:09:51.120 get away from that, where computers are able to interpret 0:09:51.120 --> 0:09:53.640 the way we think and the way different people think 0:09:53.679 --> 0:09:57.200 about the same thing, but still bring back relevant results, 0:09:57.640 --> 0:10:01.560 then we see real advances in and and a seamless 0:10:01.640 --> 0:10:04.840 experience when we start interacting with the Internet. I think 0:10:04.880 --> 0:10:08.319 that is definitely going to improve over the next five years. 0:10:08.360 --> 0:10:12.720 We've already seen some amazing results as it stands now. 0:10:13.160 --> 0:10:16.840 I also hope to see more of One of the 0:10:16.840 --> 0:10:19.480 things I really like the way Amazon has approached this 0:10:19.520 --> 0:10:25.680 Personal Digital Assistant UM model is their approach is all 0:10:25.760 --> 0:10:29.880 about integrating with other systems so that you can control 0:10:30.240 --> 0:10:33.280 different things within your home, even if they were not 0:10:33.320 --> 0:10:37.920 originally designed to work together through a single interface, right 0:10:38.040 --> 0:10:41.120 Like Hugh light bulbs are an example. Let's say that 0:10:41.160 --> 0:10:43.800 I've got Hugh light bulbs in my house. Let's say 0:10:43.960 --> 0:10:50.040 I've got some sort of of Internet connected security system. 0:10:50.080 --> 0:10:52.319 Maybe I've got a couple of other appliances that are 0:10:52.320 --> 0:10:56.240 also connected through my my home network and with Alexa, 0:10:56.320 --> 0:10:59.000 assuming that the capability has been built in by developers, 0:10:59.200 --> 0:11:01.160 I would be able to interact with all of those 0:11:01.240 --> 0:11:04.760 as opposed to having to go through each proprietary system 0:11:04.800 --> 0:11:08.440 and interface, which gets extremely clunky. It's kind of like 0:11:08.800 --> 0:11:11.960 being in front of a a an entertainment system where 0:11:12.000 --> 0:11:15.440 you have twelve different remote controls and trying to remember 0:11:15.480 --> 0:11:18.880 which one goes to what component. Uh. I hope to 0:11:18.920 --> 0:11:21.720 see more of that because, like you were saying, if 0:11:21.800 --> 0:11:24.480 we go with the siloed approach, unless you're all in 0:11:25.320 --> 0:11:30.800 with one provider, your experience is going to be really fragmented. Yeah. 0:11:30.800 --> 0:11:32.680 It just makes me think about the Internet of Things 0:11:32.760 --> 0:11:35.400 because I have an Amazon Echo and I've had some 0:11:35.440 --> 0:11:37.840 smart technologies in my house and smart light bulbs and things, 0:11:38.000 --> 0:11:39.880 and most people would ask me, like, why would you 0:11:39.920 --> 0:11:42.400 need a smart light bulb, and these are just little 0:11:42.400 --> 0:11:46.200 fancy ways to make my apartment more personalized. But when 0:11:46.280 --> 0:11:48.320 you have an echo, you have a brain that can 0:11:48.360 --> 0:11:51.480 talk to multiple devices, you start thinking what other devices 0:11:51.520 --> 0:11:53.800 you can get. So I'm expecting in five years a 0:11:53.800 --> 0:11:56.800 lot of people will be very aware of the good 0:11:56.920 --> 0:12:00.360 uses or connected devices, because I connected life all began 0:12:00.520 --> 0:12:03.040 is a very strange idea at first, but when you 0:12:03.080 --> 0:12:04.719 get used to it, you're like, wait a minute, why 0:12:04.720 --> 0:12:07.680 didn't this happen before? So I'm expecting a lot more 0:12:08.040 --> 0:12:10.680 dumb things to get a lot smarter five years. Yeah, 0:12:10.720 --> 0:12:13.400 And and you know, we've we've seen this is a 0:12:14.040 --> 0:12:18.080 a progression that starts with some kind of you know, 0:12:18.200 --> 0:12:21.360 uncertain moves. Again, going back to c e S. I 0:12:21.400 --> 0:12:23.160 love talking about ce S because that's kind of like 0:12:23.200 --> 0:12:27.400 the proving grounds for these new technologies. Typically a technology 0:12:27.440 --> 0:12:30.240 will start to kind of creep in, and then the 0:12:30.280 --> 0:12:34.200 next year it will be almost everywhere, and then maybe 0:12:34.240 --> 0:12:36.120 three more years it will be to a point where 0:12:36.120 --> 0:12:39.440 people will actually want it. Right because we've seen the 0:12:39.520 --> 0:12:44.160 smart technology move into various appliances for the better part 0:12:44.160 --> 0:12:47.439 of the decade now, and in many cases, those early 0:12:47.520 --> 0:12:52.920 implementations were either short sighted or not terribly useful. But 0:12:53.280 --> 0:12:56.160 as people are learning how to interact, and as developers 0:12:56.160 --> 0:12:59.559 are learning, you know, what people expect from their technologies, 0:13:00.040 --> 0:13:04.640 we're seeing that improve over time. I think in Internet 0:13:04.679 --> 0:13:08.160 of Things is going to continue going strong. It it 0:13:08.200 --> 0:13:11.839 isn't just a fad or a buzzword. It is going 0:13:11.920 --> 0:13:16.560 to be a pervasive technology that UH surrounds us and 0:13:16.600 --> 0:13:20.440 binds us like the force UM. It also has some 0:13:20.480 --> 0:13:24.880 potential for some some negative stuff as well, not just 0:13:24.960 --> 0:13:27.680 the idea of making our lives easier, but we'll talk 0:13:27.720 --> 0:13:31.920 about that UH in a little bit. So one of 0:13:31.960 --> 0:13:34.680 the other elements I have here on our list is 0:13:34.720 --> 0:13:40.000 this question about again getting kind ofto that fragmented experience idea, 0:13:40.720 --> 0:13:42.480 the rise of the app. That was one of those 0:13:42.480 --> 0:13:44.840 things that that Chris and I didn't really touch on. 0:13:44.880 --> 0:13:48.560 We didn't talk about apps. I don't think either of 0:13:48.679 --> 0:13:52.160 us had really figured out how important apps were going 0:13:52.240 --> 0:13:56.319 to be UH in general, and apps on smart devices 0:13:56.440 --> 0:14:00.679 on on smartphones and mobile devices in particular have become 0:14:01.679 --> 0:14:05.160 one of the most important stories in technology over the 0:14:05.240 --> 0:14:09.480 last few years. UH companies can spring up overnight and 0:14:09.520 --> 0:14:13.679 become incredibly successful with the right app a lot of 0:14:13.720 --> 0:14:16.800 companies out there are banking on that success. Many of 0:14:16.800 --> 0:14:20.000 them are failing um and and it's weird because it 0:14:20.040 --> 0:14:24.000 also creates this very siloed approach to how you access 0:14:24.040 --> 0:14:27.280 and interact with the Internet, particularly apps that are related 0:14:27.280 --> 0:14:29.520 to content, where you know you might ask the question, 0:14:29.560 --> 0:14:33.960 why do I use this app versus use a more 0:14:34.120 --> 0:14:37.680 universal interface like a browser. Do you think that we're 0:14:37.720 --> 0:14:41.160 going to continue to see, you know, a wide variety 0:14:41.160 --> 0:14:43.040 of apps moving forward, or do you think that's a 0:14:43.120 --> 0:14:47.360 bubble that will burst sometime between now and I don't 0:14:47.400 --> 0:14:49.920 see apps necessarily going away. I can see a lot 0:14:49.960 --> 0:14:52.320 of like hyper visor style apps, like we're talking about 0:14:52.360 --> 0:14:54.760 with the Echo, where it controls lots of different things. 0:14:54.880 --> 0:14:57.920 I could see a lot more apps that control other apps, 0:14:57.960 --> 0:15:00.080 if that makes any sense. Like its like right now 0:15:00.120 --> 0:15:02.360 we have things like hoot Suite, which can access to 0:15:02.440 --> 0:15:05.560 different Twitter accounts, Facebook and all that other information. So 0:15:05.600 --> 0:15:07.760 I could see that happening, which is a little strange 0:15:07.800 --> 0:15:09.600 if you think about it, because a browser should be 0:15:09.640 --> 0:15:13.360 able to handle it. But apps on their own, they 0:15:13.520 --> 0:15:16.400 offer so much control to the companies that I think 0:15:16.440 --> 0:15:18.640 that that's not going anywhere. Because the other thing is 0:15:18.880 --> 0:15:20.920 you can create a lot of things that are offline 0:15:21.400 --> 0:15:23.040 that you couldn't do in a browser. I think that's 0:15:23.040 --> 0:15:25.160 one of the bigger things. Unless in five years the 0:15:25.200 --> 0:15:29.480 Internet wirelessly or is that connectivity is always around, you 0:15:29.560 --> 0:15:32.600 still have to deal with being offline, and if you 0:15:32.640 --> 0:15:34.680 don't have an app, there's a good chance there's no 0:15:34.720 --> 0:15:36.840 way a browser is gonna work unless there's some kind 0:15:36.880 --> 0:15:39.640 of cash feature, which isn't something that really works so 0:15:39.680 --> 0:15:43.320 well right now. That's a good point. Yeah. For example, 0:15:43.360 --> 0:15:45.920 I've got I've got an app that I used for 0:15:45.920 --> 0:15:49.000 for podcatching too, to listen to the various podcasts I 0:15:49.080 --> 0:15:54.920 subscribe to, and I can either stream stuff directly from 0:15:54.960 --> 0:15:57.600 the Internet to my headphones and that way I can 0:15:57.680 --> 0:16:00.960 listen live, or I can down load an episode and 0:16:01.000 --> 0:16:02.920 listen to it even if I'm offline, which of course 0:16:03.000 --> 0:16:04.720 is useful if you're going to be like on a 0:16:04.720 --> 0:16:07.359 long flight or something and you don't have in flight WiFi. 0:16:08.200 --> 0:16:12.320 That's a really useful, uh feature. So I didn't really 0:16:12.320 --> 0:16:14.040 think of it that way, but that is interesting. I 0:16:14.040 --> 0:16:17.200 would I would love to see some more experimentation with apps. 0:16:17.200 --> 0:16:19.480 Sometimes it gets a little tricky, but you know, something 0:16:19.480 --> 0:16:24.840 that would um allow you to maximize the reach of 0:16:24.840 --> 0:16:29.360 your various music services would be nice because not all 0:16:29.520 --> 0:16:33.840 artists have work all in one or all in the 0:16:33.920 --> 0:16:38.240 same music service. And being able to go through all 0:16:38.280 --> 0:16:40.680 of them simultaneously so that you can listen to what 0:16:40.760 --> 0:16:44.080 you want to listen to. Uh, you know, subscribing to 0:16:44.120 --> 0:16:47.280 whichever services you want, but being able to search all 0:16:47.320 --> 0:16:49.840 of them at once would be really nice instead of 0:16:49.840 --> 0:16:52.400 having to you know, go into one and they oh, wait, 0:16:52.440 --> 0:16:56.880 that's right, that musicians label doesn't work with Spotify or 0:16:56.920 --> 0:17:01.080 Pandora or whatever it may be. Um, so yeah, it's interesting. 0:17:01.120 --> 0:17:03.080 I do think I do think there's going to be 0:17:03.120 --> 0:17:07.520 a bit of a reckoning between now and where we 0:17:07.560 --> 0:17:11.600 will see a lot of apps, um, kind of collapse 0:17:11.640 --> 0:17:13.199 in on themselves. I think we're going to see on 0:17:13.200 --> 0:17:18.040 the investment front, some capitalists venture Catalyst being a little 0:17:18.080 --> 0:17:21.680 more careful with which apps they jump in and back. 0:17:22.560 --> 0:17:25.880 I just don't see it as sustainable in the long 0:17:26.000 --> 0:17:29.080 run for the kind of approach we're seeing right now. 0:17:29.160 --> 0:17:33.040 Where you know, it seems like every week you're getting 0:17:33.080 --> 0:17:37.720 one or two stories about some brand new app debuting 0:17:37.800 --> 0:17:43.199 with incredible amounts of financial backing. Uh, and no business 0:17:43.280 --> 0:17:47.240 plan to speak of that that cannot continue indefinitely. So 0:17:47.320 --> 0:17:49.560 I think there's probably gonna be a bit of a 0:17:49.560 --> 0:17:54.600 shaky bubble kind of moment between now and hopefully by 0:17:55.359 --> 0:17:58.280 one it will have settled back down so that we 0:17:58.320 --> 0:18:03.320 can have product of useful apps continue. I don't I 0:18:03.400 --> 0:18:06.960 don't want to see anyone tank. I just don't think 0:18:07.000 --> 0:18:10.560 that the way things have been going is sustainable in 0:18:10.600 --> 0:18:12.560 the long run. The other thing I was thinking is 0:18:12.600 --> 0:18:16.639 that the way I've seen companies talk to developers, the 0:18:16.680 --> 0:18:20.280 idea that you write one app and runs on multiple platforms, Android, Chromos, 0:18:20.800 --> 0:18:22.520 or if you run a Windows app it runs on 0:18:22.560 --> 0:18:25.159 every Windows thing and iOS at some point has to 0:18:25.280 --> 0:18:27.919 have some kind of ties to os ten or mac os. 0:18:28.320 --> 0:18:31.080 I would imagine in five years these apps that are 0:18:31.119 --> 0:18:32.600 just kind of like, oh, it's only for my phone, 0:18:32.600 --> 0:18:34.359 it's only from my watch, or it's only for whatever, 0:18:34.760 --> 0:18:37.840 these these apps will actually be much more powerful than 0:18:37.840 --> 0:18:40.240 when you can install them on full fledged computers, or 0:18:40.280 --> 0:18:43.640 you can have the same experience or slightly modified experiences 0:18:43.640 --> 0:18:45.800 for different screens. I think that's the future we're headed for. 0:18:46.040 --> 0:18:47.800 So we're not gonna lose the apps. We might get 0:18:47.840 --> 0:18:51.720 more productive apps, But I don't see it being this 0:18:51.840 --> 0:18:53.920 world of the way it is now. It's definitely gonna 0:18:53.960 --> 0:18:55.760 be much more, kind of like the way the i 0:18:55.880 --> 0:18:59.200 OS apps can be iPhone and iPad. I can imagine 0:18:59.400 --> 0:19:02.440 this happened with all other kinds of apps as well. Yeah, 0:19:02.480 --> 0:19:04.800 that's something that Microsoft has been pushing for for a 0:19:04.800 --> 0:19:08.360 long time. I mean Windows eight was our first indication 0:19:08.440 --> 0:19:13.000 that they really wanted to create this universal experience where 0:19:13.560 --> 0:19:17.680 the technology, the programs you depended upon would work across 0:19:17.840 --> 0:19:22.639 multitude multiple platforms seamlessly. And we're we're seeing that with 0:19:22.720 --> 0:19:26.320 a lot of ways that apps are uh designed, you know, 0:19:26.440 --> 0:19:29.600 like um, Netflix is a great example where you're watching 0:19:29.600 --> 0:19:33.679 Netflix on one platform, you pause your viewing, you go, 0:19:33.840 --> 0:19:35.920 you turn on a different platform, and you can pick 0:19:36.000 --> 0:19:38.719 up right where you left off. That that's sort of 0:19:38.760 --> 0:19:41.159 that same idea, this idea that you can have a 0:19:41.200 --> 0:19:44.560 persistent experience across whichever platform you want. It may be 0:19:44.720 --> 0:19:47.560 that the interaction with that platform has to be different 0:19:47.600 --> 0:19:50.359 because it's just a it's you know, it doesn't have 0:19:50.400 --> 0:19:53.560 the same interface, but the experience you get is as 0:19:53.640 --> 0:19:57.680 close to being universal as you can possibly get. Um. 0:19:57.720 --> 0:20:00.600 I agree that that's definitely gonna continue you and and 0:20:02.160 --> 0:20:05.159 it will probably be very impressive, at least to the 0:20:05.160 --> 0:20:09.240 twenty sixteen versions of US. Maybe versions of US will 0:20:09.280 --> 0:20:13.320 be you know, totally blase about it, but but right 0:20:13.359 --> 0:20:15.560 now we'd be really we'd really be thrilled by that. 0:20:16.760 --> 0:20:19.240 One of the other things we did not talk about 0:20:19.359 --> 0:20:22.320 in two thousand and eleven, neither Chris nor I anticipated 0:20:22.359 --> 0:20:26.760 it was the rise of Google Fiber. Uh, and seeing 0:20:26.760 --> 0:20:30.639 Google Fiber come out. I'm in Atlanta and Google Fiber 0:20:30.720 --> 0:20:34.800 is currently deploying in Atlanta to the point where lots 0:20:34.840 --> 0:20:38.240 of different neighborhoods in the Atlanta area are eligible for 0:20:38.320 --> 0:20:42.160 signing up for Google Fiber. Not me yet, but any 0:20:42.200 --> 0:20:46.880 day now. Um, So we didn't anticipate Google Fiber showing up. 0:20:47.320 --> 0:20:49.880 Do you think Google Fiber is actually going to have 0:20:50.320 --> 0:20:53.680 a disruptive effect on the industry as a whole or 0:20:53.720 --> 0:20:56.480 do you see this as being something that might might 0:20:56.520 --> 0:21:02.280 be beneficial for certain regions. But that's all we're going 0:21:02.320 --> 0:21:05.440 to see. We're not gonna get a wider effect than that. 0:21:06.160 --> 0:21:08.280 I think there's gonna be quite a wide effect. In 0:21:08.359 --> 0:21:11.240 recent news, Versing went out and bought a o L 0:21:11.400 --> 0:21:13.840 and uh something else was the other one, Yahoo, right, 0:21:14.080 --> 0:21:16.399 And essentially it makes it some kind of digital advertising 0:21:16.440 --> 0:21:19.080 giant to take on Google. And I loved seeing the 0:21:19.080 --> 0:21:21.679 news only for the reason that maybe it would get 0:21:21.720 --> 0:21:25.120 like like light a fire under Google and go, wait 0:21:25.160 --> 0:21:27.960 a second, if those guys are going to be an 0:21:27.960 --> 0:21:30.560 I s P and they're going to have this kind 0:21:30.600 --> 0:21:32.800 of content management, why don't we do the same thing 0:21:32.840 --> 0:21:36.040 considering we're competitors with them. So I'm expecting Google to 0:21:36.080 --> 0:21:38.680 be one of the first to just full on go 0:21:38.840 --> 0:21:42.640 head to head against a horizon against the wireless carriers 0:21:42.640 --> 0:21:46.400 out there, because Google Fiber, while it's good, the infrastructure 0:21:46.480 --> 0:21:48.959 layout just seems to take so long and then run 0:21:49.000 --> 0:21:52.040 into a lot of regulation problems. But if they can 0:21:52.080 --> 0:21:55.439 buy up you know, essentially the wireless last mile, if 0:21:55.440 --> 0:21:57.280 that's how this is going to go, I would think 0:21:57.320 --> 0:21:58.879 they would be one of the companies to do it. 0:21:59.200 --> 0:22:01.320