WEBVTT 00:00:00.160 --> 00:00:05.040 I don't know if it was scary good or 00:00:02.399 --> 00:00:07.200 just plain scary scary, but the Android 00:00:05.040 --> 00:00:11.920 show just wrapped up today and the theme 00:00:07.200 --> 00:00:14.000 is Android everywhere with a side of uh 00:00:11.920 --> 00:00:16.640 oh, by the way, that means Gemini is 00:00:14.000 --> 00:00:19.439 also everywhere. Hence the rebranding of 00:00:16.640 --> 00:00:20.800 Android from an operating system to an 00:00:19.439 --> 00:00:23.519 intelligence system. 00:00:20.800 --> 00:00:25.119 >> It's uh it's pretty telling that they 00:00:23.519 --> 00:00:27.279 turned off comments on the video, isn't 00:00:25.119 --> 00:00:29.439 it? I mean, to be clear, Google's not 00:00:27.279 --> 00:00:31.679 the only one who does this, but it 00:00:29.439 --> 00:00:34.480 really does say a lot about the current 00:00:31.679 --> 00:00:36.399 state of tech that major brands are so 00:00:34.480 --> 00:00:38.399 afraid of what their terminally online 00:00:36.399 --> 00:00:40.879 customers might say about their new 00:00:38.399 --> 00:00:43.840 products and features. Features that 00:00:40.879 --> 00:00:46.480 admittedly look very cool. It's just 00:00:43.840 --> 00:00:48.800 that they're often privacy and data 00:00:46.480 --> 00:00:51.039 collection nightmares. So, here's an 00:00:48.800 --> 00:00:53.680 idea. If you've got something to say to 00:00:51.039 --> 00:00:56.239 big tech, maybe watch our video instead 00:00:53.680 --> 00:00:57.840 and leave your comments there. Unless 00:00:56.239 --> 00:01:00.640 you want to trash talk Microsoft, who 00:00:57.840 --> 00:01:03.680 bravely leaves comments enabled. Bold 00:01:00.640 --> 00:01:05.920 move, Satcha. I respect it almost as 00:01:03.680 --> 00:01:08.880 much as I respect our sponsor, UG, 00:01:05.920 --> 00:01:12.799 Green. UG Green's DX 4800 Pro NAS can 00:01:08.880 --> 00:01:15.280 hold up to 144 terab of your favorite 00:01:12.799 --> 00:01:17.040 photos, movies, and files. And it's 00:01:15.280 --> 00:01:19.040 compatible with a variety of hard 00:01:17.040 --> 00:01:21.759 drives. Grab yours at the link down 00:01:19.040 --> 00:01:24.000 below. We've got to kick things off with 00:01:21.759 --> 00:01:26.799 the Google book. Not to be confused with 00:01:24.000 --> 00:01:29.040 other books like Pixelbooks or MacBooks. 00:01:26.799 --> 00:01:30.880 See, those are made by one brand, but 00:01:29.040 --> 00:01:32.880 Google books are going to be like 00:01:30.880 --> 00:01:34.720 Chromebooks, which come in a variety of 00:01:32.880 --> 00:01:37.520 hardware configurations from partner 00:01:34.720 --> 00:01:40.400 brands like Lenovo and Asus. Which 00:01:37.520 --> 00:01:42.159 raises the question, okay, what's the 00:01:40.400 --> 00:01:44.720 difference then between a Google book 00:01:42.159 --> 00:01:47.040 and a Chromebook? Well, let me tell you. 00:01:44.720 --> 00:01:50.079 For one thing, Google books will have 00:01:47.040 --> 00:01:52.880 this, the glow bar that tells everyone 00:01:50.079 --> 00:01:56.960 around you, "This ain't no Chromebook." 00:01:52.880 --> 00:01:59.680 No, ma'am. This is a Google book. Cool. 00:01:56.960 --> 00:02:01.520 Also, unlike Chromebooks, Google Books 00:01:59.680 --> 00:02:04.000 are going to be using a new operating 00:02:01.520 --> 00:02:07.920 system that unifies Android and Chrome 00:02:04.000 --> 00:02:09.520 OS. It doesn't have a name yet, which is 00:02:07.920 --> 00:02:11.599 kind of awkward for a company the size 00:02:09.520 --> 00:02:13.760 of Google. So, the media has taken to 00:02:11.599 --> 00:02:16.800 referring to its development code name, 00:02:13.760 --> 00:02:20.959 Aluminium OS. We don't know too much 00:02:16.800 --> 00:02:23.599 about it yet. Um, hint hint, Google IO 00:02:20.959 --> 00:02:25.280 is next week. But what we do know is 00:02:23.599 --> 00:02:27.360 that it's going to come with a new magic 00:02:25.280 --> 00:02:29.760 pointer feature, not to be confused with 00:02:27.360 --> 00:02:32.160 magic mouse. Do do you feel like when I 00:02:29.760 --> 00:02:34.080 have to say not to be confused with this 00:02:32.160 --> 00:02:36.319 many times, um, your product 00:02:34.080 --> 00:02:40.400 announcement might just be confusing? 00:02:36.319 --> 00:02:42.959 Anyone? Buler. Anyway, magic pointer 00:02:40.400 --> 00:02:44.879 allows anyone to easily use Gemini by 00:02:42.959 --> 00:02:46.800 simply wiggling the cursor and then 00:02:44.879 --> 00:02:50.000 pointing it at an on-screen element and 00:02:46.800 --> 00:02:52.400 asking it to do AI things like say draft 00:02:50.000 --> 00:02:54.080 a reply to the text in this email. I can 00:02:52.400 --> 00:02:56.000 actually see this being very useful, 00:02:54.080 --> 00:02:58.800 much like the circle to search feature 00:02:56.000 --> 00:03:00.480 on Android today. However, if you're 00:02:58.800 --> 00:03:03.120 anything like me, it'll probably be 00:03:00.480 --> 00:03:04.720 between one and three accidental 00:03:03.120 --> 00:03:07.680 activations of the gesture before you 00:03:04.720 --> 00:03:09.280 rebind it to something anything else. 00:03:07.680 --> 00:03:12.400 Something I'm legitimately stoked on, 00:03:09.280 --> 00:03:14.800 though, is custom widgets. Now, Google's 00:03:12.400 --> 00:03:16.959 not the first to talk about how they 00:03:14.800 --> 00:03:18.720 need more AI in their operating system, 00:03:16.959 --> 00:03:20.560 and pretty much every example of that 00:03:18.720 --> 00:03:24.959 we've seen so far has been kind of 00:03:20.560 --> 00:03:28.159 cringe. This one, not so. Custom widgets 00:03:24.959 --> 00:03:29.840 have got to be the best example of AI in 00:03:28.159 --> 00:03:33.040 an operating system that I've seen so 00:03:29.840 --> 00:03:35.440 far. You want just rain and wind speed 00:03:33.040 --> 00:03:37.120 in your weather app? Boom. You give it a 00:03:35.440 --> 00:03:39.360 plain text prompt and it creates a 00:03:37.120 --> 00:03:40.720 widget for you. Finding exactly the 00:03:39.360 --> 00:03:42.640 right widget is something that I have 00:03:40.720 --> 00:03:44.879 personally struggled with in the past. 00:03:42.640 --> 00:03:46.799 Uh like I can't wait for example to 00:03:44.879 --> 00:03:48.959 create a time zone and alarm management 00:03:46.799 --> 00:03:50.879 widget that really works for me. And 00:03:48.959 --> 00:03:52.879 this is coming to both the new unnamed 00:03:50.879 --> 00:03:56.480 OS as well as Android mobile with 00:03:52.879 --> 00:03:58.239 Android 17. I'm stoked. Also, Google 00:03:56.480 --> 00:04:00.560 Books are getting quick access, which is 00:03:58.239 --> 00:04:03.040 the ability to browse and access files 00:04:00.560 --> 00:04:05.680 on your phone directly from your laptop 00:04:03.040 --> 00:04:07.680 and then just like drop that file as an 00:04:05.680 --> 00:04:09.920 attachment on an email, even if you 00:04:07.680 --> 00:04:12.560 don't necessarily use Google Photos and 00:04:09.920 --> 00:04:15.680 Cloud Sync. And sure, Windows has had 00:04:12.560 --> 00:04:17.840 the your phone feature since like 2018, 00:04:15.680 --> 00:04:19.840 but it is great to see app mirroring and 00:04:17.840 --> 00:04:22.079 phone access that are now available to 00:04:19.840 --> 00:04:25.360 everyone, regardless of which developer 00:04:22.079 --> 00:04:26.960 garden you prefer to sip tea in. tea 00:04:25.360 --> 00:04:28.479 that's getting much sweeter on the 00:04:26.960 --> 00:04:31.199 Google side of things because the rest 00:04:28.479 --> 00:04:33.840 of their Gemini sizzle reel looked, if 00:04:31.199 --> 00:04:35.440 I'm being honest, legitimately amazing. 00:04:33.840 --> 00:04:37.040 Running late for a very important date, 00:04:35.440 --> 00:04:38.960 but you see an upcoming concert poster 00:04:37.040 --> 00:04:41.040 as you exit the train station? Just snap 00:04:38.960 --> 00:04:42.960 a pic of it, tell your AI assistant to 00:04:41.040 --> 00:04:45.520 book you a couple of floor tickets, 00:04:42.960 --> 00:04:48.240 enjoy the concert, then ask Gemini to 00:04:45.520 --> 00:04:50.400 find some good late night zah. Then, 00:04:48.240 --> 00:04:51.840 assuming things went well, ask it to 00:04:50.400 --> 00:04:54.639 book a spot in your calendar to do it 00:04:51.840 --> 00:04:56.960 all over again next week. Wow. It's like 00:04:54.639 --> 00:04:59.680 everyone having their very own Vance. 00:04:56.960 --> 00:05:01.840 >> Hey Vance, can you look up how many 00:04:59.680 --> 00:05:03.759 times Google has promised this level of 00:05:01.840 --> 00:05:05.440 integration between like my personal 00:05:03.759 --> 00:05:06.479 life and my calendar and my Google 00:05:05.440 --> 00:05:08.880 Assistant? 00:05:06.479 --> 00:05:11.360 >> I don't know, a lot. 00:05:08.880 --> 00:05:13.280 >> Yeah, we've kind of reached a bit of a 00:05:11.360 --> 00:05:15.520 boy who cried wolf point now, haven't 00:05:13.280 --> 00:05:17.360 we? Remember that clip-on camera that 00:05:15.520 --> 00:05:19.520 claimed to use AI to take pictures at 00:05:17.360 --> 00:05:21.919 opportune moments? Remember that feature 00:05:19.520 --> 00:05:23.680 where assistant would totally seamlessly 00:05:21.919 --> 00:05:26.160 phone and book hair appointments on your 00:05:23.680 --> 00:05:28.479 behalf? And remember the image 00:05:26.160 --> 00:05:30.160 searchability that just time and time 00:05:28.479 --> 00:05:32.880 again on ShortCircuit has failed to 00:05:30.160 --> 00:05:35.120 find or in many cases even recognize the 00:05:32.880 --> 00:05:36.720 LTT Northern Lights deskpad in spite of 00:05:35.120 --> 00:05:38.160 there being countless images of it 00:05:36.720 --> 00:05:40.240 online and it being available at 00:05:38.160 --> 00:05:42.960 ltstore.com. 00:05:40.240 --> 00:05:45.600 I mean to be fair, some of this stuff, 00:05:42.960 --> 00:05:48.400 especially that last one, does work way 00:05:45.600 --> 00:05:51.680 better these days. And if all this new 00:05:48.400 --> 00:05:54.320 stuff works, it sounds great. But I can 00:05:51.680 --> 00:05:56.720 already tell that that concert demo is 00:05:54.320 --> 00:05:59.120 pure weaponsgrade bologonium because it 00:05:56.720 --> 00:06:02.400 doesn't ask any follow-up questions like 00:05:59.120 --> 00:06:04.400 what time when you're booking a date. 00:06:02.400 --> 00:06:05.840 That's kind of important. And I wish 00:06:04.400 --> 00:06:08.240 Google would just be honest and 00:06:05.840 --> 00:06:11.360 realistic about how it's going to work 00:06:08.240 --> 00:06:14.160 outside of their perfect dev environment 00:06:11.360 --> 00:06:16.319 bubble. Like here's another example. 00:06:14.160 --> 00:06:18.720 that auto form filling feature where 00:06:16.319 --> 00:06:20.720 they talked about how Gemini could scan 00:06:18.720 --> 00:06:22.319 your photo library for that time you 00:06:20.720 --> 00:06:24.960 took a picture of your passport last 00:06:22.319 --> 00:06:26.960 year and then automatically input your 00:06:24.960 --> 00:06:29.039 passport number or your expiration date 00:06:26.960 --> 00:06:31.280 into a form for you. That sounds 00:06:29.039 --> 00:06:33.120 awesome. But will it work in the real 00:06:31.280 --> 00:06:35.199 world where maybe you've got multiple 00:06:33.120 --> 00:06:37.199 passport photos for yourself and some 00:06:35.199 --> 00:06:39.440 for your kids and one for your wife? Is 00:06:37.199 --> 00:06:40.800 it going to get the right one? I don't 00:06:39.440 --> 00:06:42.560 think it's crazy to be skeptical about 00:06:40.800 --> 00:06:46.400 this. I mean, okay, look. How often does 00:06:42.560 --> 00:06:47.039 your autocomplete say, "Oo, 3663 Crowley 00:06:46.400 --> 00:06:48.000 Drive." 00:06:47.039 --> 00:06:49.440 >> ALL THE TIME. 00:06:48.000 --> 00:06:50.080 >> YEAH. And when's the last time you lived 00:06:49.440 --> 00:06:51.039 there? 00:06:50.080 --> 00:06:52.639 >> Years ago. 00:06:51.039 --> 00:06:54.800 >> That's what I'm talking about. I mean, 00:06:52.639 --> 00:06:58.000 for me, even just setting alarms screws 00:06:54.800 --> 00:07:01.520 up a solid like 5 to 10% of the time. 00:06:58.000 --> 00:07:03.840 So, I'm not sure when, if ever, I'm 00:07:01.520 --> 00:07:06.880 going to get past the trust but verify 00:07:03.840 --> 00:07:09.440 phase for my AI personal assistant. and 00:07:06.880 --> 00:07:12.000 all of that ignores the privacy and 00:07:09.440 --> 00:07:14.400 targeted ad side of this whole data 00:07:12.000 --> 00:07:16.800 collection conversation. 00:07:14.400 --> 00:07:19.919 But hey, you know, some of this stuff, 00:07:16.800 --> 00:07:21.840 again, if it works, looks so good that 00:07:19.919 --> 00:07:24.319 people probably will turn it on 00:07:21.840 --> 00:07:27.039 regardless of the privacy implications. 00:07:24.319 --> 00:07:28.639 Rambler is a new feature for phones, but 00:07:27.039 --> 00:07:30.720 also Android Auto, which we're going to 00:07:28.639 --> 00:07:32.880 get into in a second. And I'm really 00:07:30.720 --> 00:07:34.960 excited about both Rambler and the 00:07:32.880 --> 00:07:36.960 Android Auto overhaul. Okay, guys. Have 00:07:34.960 --> 00:07:39.039 you ever tried responding to a message 00:07:36.960 --> 00:07:40.720 through voice to text while you're 00:07:39.039 --> 00:07:42.080 driving and someone cuts you off? Or 00:07:40.720 --> 00:07:44.479 maybe your kids won't shut up in the 00:07:42.080 --> 00:07:47.039 back seat? Well, with Rambler, you don't 00:07:44.479 --> 00:07:50.080 have TO WORRY ABOUT, "HEY, WATCH WHERE 00:07:47.039 --> 00:07:51.840 you'reing driving." 00:07:50.080 --> 00:07:53.520 Any of the expletives that you might be 00:07:51.840 --> 00:07:55.599 shouting in the middle of your reply 00:07:53.520 --> 00:07:57.599 that could accidentally make it to your 00:07:55.599 --> 00:07:59.840 wife or your boss, who for me is the 00:07:57.599 --> 00:08:01.599 same person, which doubles the risk. 00:07:59.840 --> 00:08:03.680 supposedly rambler is going to take the 00:08:01.599 --> 00:08:07.599 entire context of YOUR DICTATION AND 00:08:03.680 --> 00:08:09.440 HEY, WATCH IT as 00:08:07.599 --> 00:08:11.199 pick out only the relevant parts of your 00:08:09.440 --> 00:08:14.400 voice note and then condense it into a 00:08:11.199 --> 00:08:16.240 proper message. Super cool. On the 00:08:14.400 --> 00:08:18.319 subject of distracted driving, Google is 00:08:16.240 --> 00:08:21.120 also rolling out a massive update to 00:08:18.319 --> 00:08:25.120 maps, making it look more 3D, so you can 00:08:21.120 --> 00:08:27.440 tell, is that an overpass, an underpass, 00:08:25.120 --> 00:08:29.440 a touchdown pass? 00:08:27.440 --> 00:08:31.280 And that's almost as cool as the way 00:08:29.440 --> 00:08:33.039 that Android Auto is not only going to 00:08:31.280 --> 00:08:35.919 fit better on all the various display 00:08:33.039 --> 00:08:37.919 sizes in cars these days, but it's also 00:08:35.919 --> 00:08:40.959 getting the ability to play video 00:08:37.919 --> 00:08:43.440 through that screen and with Dolby 00:08:40.959 --> 00:08:45.200 Atmos. Now, that's only going to be on 00:08:43.440 --> 00:08:46.959 vehicles or apps that support it and 00:08:45.200 --> 00:08:49.600 only while the vehicle is parked. But 00:08:46.959 --> 00:08:51.040 guys, if you've got an EV that isn't a 00:08:49.600 --> 00:08:53.040 Tesla and you've ever been stuck at a 00:08:51.040 --> 00:08:55.600 charging station, you are going to 00:08:53.040 --> 00:08:57.440 freaking love this. Google's also 00:08:55.600 --> 00:08:59.600 rolling out more customization for your 00:08:57.440 --> 00:09:02.399 in-car display, like different fonts, 00:08:59.600 --> 00:09:05.519 widgets, or backgrounds to help enhance 00:09:02.399 --> 00:09:07.440 the Android Auto experience. And if 00:09:05.519 --> 00:09:09.120 you're driving one of the roughly 100 00:09:07.440 --> 00:09:11.440 vehicles that are rolling out with 00:09:09.120 --> 00:09:13.680 Google Builtin, formerly known as 00:09:11.440 --> 00:09:15.600 Android Automotive, thank goodness they 00:09:13.680 --> 00:09:17.760 changed that, any of the apps that you 00:09:15.600 --> 00:09:19.519 might use should feel more seamless and 00:09:17.760 --> 00:09:21.440 more responsive thanks to direct 00:09:19.519 --> 00:09:23.600 hardware integration and being on board 00:09:21.440 --> 00:09:25.839 instead of running on your phone. Okay, 00:09:23.600 --> 00:09:27.920 so what does that look like? This one's 00:09:25.839 --> 00:09:29.279 pretty cool. If a symbol pops up on your 00:09:27.920 --> 00:09:32.160 digital dash that you've never seen 00:09:29.279 --> 00:09:34.560 before, supposedly you can just ask 00:09:32.160 --> 00:09:36.399 Gemini what it means. Or another great 00:09:34.560 --> 00:09:38.240 example they gave was asking about trunk 00:09:36.399 --> 00:09:40.800 dimensions and whether or not a TV would 00:09:38.240 --> 00:09:43.279 fit in your car. Okay, that's stuff that 00:09:40.800 --> 00:09:44.720 you could look up yourself and you're 00:09:43.279 --> 00:09:46.800 still going to probably want to verify 00:09:44.720 --> 00:09:48.880 that before you just like carry a 75 in 00:09:46.800 --> 00:09:50.560 TV into the parking lot and just go for 00:09:48.880 --> 00:09:52.080 it. I've done that, by the way. It 00:09:50.560 --> 00:09:53.600 sucks. I had to actually take the 00:09:52.080 --> 00:09:55.920 packaging off and take it back into the 00:09:53.600 --> 00:09:57.279 store in order to get. Anyway, um the 00:09:55.920 --> 00:09:58.880 point is that these are the kinds of 00:09:57.279 --> 00:10:01.200 hassles that a lot of folks would 00:09:58.880 --> 00:10:02.880 genuinely be very happy to live without, 00:10:01.200 --> 00:10:05.120 especially if you're not a car person 00:10:02.880 --> 00:10:07.200 and you don't care what exact make, 00:10:05.120 --> 00:10:08.480 model, and trim level you drive. With 00:10:07.200 --> 00:10:09.680 that in mind, they really need to step 00:10:08.480 --> 00:10:11.600 up their game when it comes to 00:10:09.680 --> 00:10:14.079 co-arketing these features with vehicle 00:10:11.600 --> 00:10:16.560 manufacturers. Some of the links on the 00:10:14.079 --> 00:10:18.640 Google built-in site go to specific 00:10:16.560 --> 00:10:20.959 models that support it. Honda is a 00:10:18.640 --> 00:10:23.760 shining example here, but others when 00:10:20.959 --> 00:10:25.519 you click through, they just dump you on 00:10:23.760 --> 00:10:28.000 the partner manufacturer's homepage, 00:10:25.519 --> 00:10:31.279 which leaves you with questions like 00:10:28.000 --> 00:10:33.200 which Mazda or BYD vehicle supports this 00:10:31.279 --> 00:10:35.920 feature. 00:10:33.200 --> 00:10:38.000 Moving away from AI, endto-end RCS 00:10:35.920 --> 00:10:40.320 encryption with iOS is rolling out 00:10:38.000 --> 00:10:42.399 effective now. Even Apple has an 00:10:40.320 --> 00:10:44.000 announcement for that. And Google says 00:10:42.399 --> 00:10:46.640 on that subject, they're making it 00:10:44.000 --> 00:10:48.720 easier than ever to swap from Apple to 00:10:46.640 --> 00:10:51.040 Android. Quick Share is coming to more 00:10:48.720 --> 00:10:53.040 devices later this year and juiced up 00:10:51.040 --> 00:10:55.839 voice isolation and sound separation 00:10:53.040 --> 00:10:57.279 looks awesome for clearer calls. Even 00:10:55.839 --> 00:10:59.200 cooler though is their new screen 00:10:57.279 --> 00:11:01.440 reactions feature. I am loving this. 00:10:59.200 --> 00:11:03.760 This allows you to record your screen 00:11:01.440 --> 00:11:06.560 and also at the same time record 00:11:03.760 --> 00:11:08.320 yourself over top of whatever is showing 00:11:06.560 --> 00:11:11.519 so that you can pop up over your photos 00:11:08.320 --> 00:11:13.760 as you talk about them or for me you can 00:11:11.519 --> 00:11:16.079 explain what's going on as you are 00:11:13.760 --> 00:11:18.560 marking up a document or giving feedback 00:11:16.079 --> 00:11:20.160 on something that might be broken. The 00:11:18.560 --> 00:11:21.279 one thing that I'd love to see improve 00:11:20.160 --> 00:11:23.680 here is I'd like to see some 00:11:21.279 --> 00:11:25.279 transparency options so that my viewer 00:11:23.680 --> 00:11:26.640 can see whatever part of the screen I 00:11:25.279 --> 00:11:28.640 happen to be covering in case that's 00:11:26.640 --> 00:11:30.320 important for troubleshooting. In all, 00:11:28.640 --> 00:11:32.160 Google showed off some really cool and 00:11:30.320 --> 00:11:33.680 exciting stuff today, or well, maybe 00:11:32.160 --> 00:11:36.480 yesterday, depending on when this gets 00:11:33.680 --> 00:11:38.399 edited and posted. And the idea of 00:11:36.480 --> 00:11:43.040 automating some of life's tediousness 00:11:38.399 --> 00:11:44.800 sounds great, but I'm going to be a bit 00:11:43.040 --> 00:11:47.360 skeptical until I actually try it out 00:11:44.800 --> 00:11:51.200 for myself. Oh, when is that coming, you 00:11:47.360 --> 00:11:54.880 ask? Later this year, sometime after 00:11:51.200 --> 00:11:56.959 this segue to our sponsor, you green. If 00:11:54.880 --> 00:11:58.640 you find yourself carrying around extra 00:11:56.959 --> 00:12:01.360 hard drives for your laptop or your 00:11:58.640 --> 00:12:03.839 other devices, maybe it's time to stop. 00:12:01.360 --> 00:12:05.600 Maybe it's time to look into a NAS. If 00:12:03.839 --> 00:12:07.440 you don't already know what that is, in 00:12:05.600 --> 00:12:10.320 the simplest of terms, you can think of 00:12:07.440 --> 00:12:12.240 a NAS as kind of like your own personal 00:12:10.320 --> 00:12:14.720 cloud storage where you can put your 00:12:12.240 --> 00:12:19.040 files safely and they live back at your 00:12:14.720 --> 00:12:21.200 home. UG's DX4800 ProNaz is a reasonably 00:12:19.040 --> 00:12:23.360 priced option that has four bays for you 00:12:21.200 --> 00:12:25.120 to plug in your own hard drives. From 00:12:23.360 --> 00:12:27.360 there, you'll have access to all of your 00:12:25.120 --> 00:12:29.839 favorite pictures, videos, and important 00:12:27.360 --> 00:12:33.440 documents wherever you go. And since it 00:12:29.839 --> 00:12:36.639 supports up to 144 terabytes of storage, 00:12:33.440 --> 00:12:40.560 that means roughly 50 million photos, 00:12:36.639 --> 00:12:42.639 9800 movies, or 150 million files. And 00:12:40.560 --> 00:12:45.839 if you already have existing hard 00:12:42.639 --> 00:12:48.160 drives, the DX4800 Pro already supports 00:12:45.839 --> 00:12:49.680 a wide variety of drives, so you don't 00:12:48.160 --> 00:12:51.680 have to stress about needing to buy 00:12:49.680 --> 00:12:53.440 something proprietary. They are beginner 00:12:51.680 --> 00:12:55.440 friendly and swapping drives is easier 00:12:53.440 --> 00:12:57.360 than putting in an IKEA drawer. So stop 00:12:55.440 --> 00:12:59.360 lugging around external hard drives. 00:12:57.360 --> 00:13:01.839 Don't pay for overpriced cloud storage 00:12:59.360 --> 00:13:04.880 and use our link below to grab your UG 00:13:01.839 --> 00:13:06.480 Green DX4800 Pro today. Thanks for 00:13:04.880 --> 00:13:07.920 watching guys. If you like this video, 00:13:06.480 --> 00:13:09.519 maybe check out Apple's latest 00:13:07.920 --> 00:13:12.320 announcement. I'm actually feeling like 00:13:09.519 --> 00:13:13.920 Apple and Google are competing pretty 00:13:12.320 --> 00:13:15.680 hard these days cuz it's hard to 00:13:13.920 --> 00:13:17.600 differentiate on the hardware side. So 00:13:15.680 --> 00:13:21.440 it's going to have to be making your 00:13:17.600 --> 00:13:21.440 life easier and better through software.