WEBVTT 00:00:00.000 --> 00:00:02.620 A small team reportedly built this native Mac 00:00:02.620 --> 00:00:06.099 app in just a few days. They used Google's own 00:00:06.099 --> 00:00:09.279 AI coding tool, which is called anti -gravity. 00:00:09.619 --> 00:00:12.580 Just think about that for a second. It is literally 00:00:12.580 --> 00:00:16.660 AI building AI. Wow. Yeah, that completely rewrites 00:00:16.660 --> 00:00:18.920 the rules of software deployment, I mean. If 00:00:18.920 --> 00:00:22.059 the friction to build a native app just drops 00:00:22.059 --> 00:00:25.559 from months down to... you know, days. We are 00:00:25.559 --> 00:00:28.480 about to see a massive tidal wave of desktop 00:00:28.480 --> 00:00:30.760 integrations. Absolutely. It's wild to think 00:00:30.760 --> 00:00:33.899 about. Welcome to this deep dive. Today, we are 00:00:33.899 --> 00:00:36.100 looking at Google's newly launched native Mac 00:00:36.100 --> 00:00:38.820 app for Gemini. Our mission here is pretty straightforward. 00:00:39.119 --> 00:00:41.659 We want to understand how AI is officially abandoning 00:00:41.659 --> 00:00:43.880 the browser tab. Right. It's finally moving down 00:00:43.880 --> 00:00:46.399 to sit natively on your desktop. Exactly. And 00:00:46.399 --> 00:00:48.079 we'll explore how this app becomes an always 00:00:48.079 --> 00:00:50.509 available system. We're going to unpack the three 00:00:50.509 --> 00:00:52.950 major features, including how it physically sees 00:00:52.950 --> 00:00:55.070 your screen. That screen sharing part is just 00:00:55.070 --> 00:00:57.609 a game changer. It really is. And finally, we 00:00:57.609 --> 00:00:59.750 will discuss what is glaringly missing from this 00:00:59.750 --> 00:01:01.750 early release. Because it definitely has some 00:01:01.750 --> 00:01:04.390 rough edges right now. But the overall direction 00:01:04.390 --> 00:01:07.650 is just fascinating to watch. It is. So let's 00:01:07.650 --> 00:01:10.810 start with how and why this app exists in its 00:01:10.810 --> 00:01:13.890 current form. We're essentially moving from a 00:01:13.890 --> 00:01:17.859 hidden Chrome tab to a dedicated native... desktop 00:01:17.859 --> 00:01:20.439 assistant. Right. Because before this release, 00:01:20.799 --> 00:01:23.739 Gemini mostly lived trapped inside your browser 00:01:23.739 --> 00:01:27.140 window. Yeah. And that meant managing extra tabs. 00:01:27.260 --> 00:01:30.260 It meant dealing with extra clicks just to ask 00:01:30.260 --> 00:01:32.560 a simple question. It also meant constant breaks 00:01:32.560 --> 00:01:35.280 in focus. I have to admit something here. I still 00:01:35.280 --> 00:01:38.599 wrestle with tab fatigue and losing my train 00:01:38.599 --> 00:01:40.459 of thought pretty constantly. Oh, you are definitely 00:01:40.459 --> 00:01:42.819 not alone in that. Context switching is completely 00:01:42.819 --> 00:01:45.379 exhausting for the human brain. Yeah, it really 00:01:45.379 --> 00:01:47.000 drains you. Every single time you switch tabs, 00:01:47.159 --> 00:01:49.299 you lose a tiny bit of your working memory. Look 00:01:49.299 --> 00:01:52.299 at it this way. The old browser -based AI was 00:01:52.299 --> 00:01:55.159 a lot like a dusty encyclopedia. You literally 00:01:55.159 --> 00:01:57.000 had to stop what you were doing, walk across 00:01:57.000 --> 00:01:59.120 the room, and fetch it. That's a great way to 00:01:59.120 --> 00:02:02.359 put it. But this new native app feels entirely 00:02:02.359 --> 00:02:04.980 different. It is more like slipping on a pair 00:02:04.980 --> 00:02:07.359 of glasses with a translucent overlay. It just 00:02:07.359 --> 00:02:09.879 sits right there, quietly augmenting whatever 00:02:09.879 --> 00:02:12.340 you are already looking at. I love that analogy. 00:02:12.500 --> 00:02:14.759 It stays intimately close to your actual workflow. 00:02:14.939 --> 00:02:17.719 But to get that seamless experience, there are 00:02:17.719 --> 00:02:21.039 some pretty strict hardware requirements, right? 00:02:21.080 --> 00:02:24.300 It is completely free download. However, it only 00:02:24.300 --> 00:02:27.340 works on Mac OS Sequoia 15 .0 or later. Exactly. 00:02:27.580 --> 00:02:30.560 And the big catch is that it requires Apple Silicon. 00:02:30.780 --> 00:02:33.639 So if you are still rocking an older Intel Mac, 00:02:33.780 --> 00:02:36.580 you are totally out of luck for now. Let's explain 00:02:36.580 --> 00:02:38.919 why that hardware restriction exists, actually. 00:02:39.000 --> 00:02:41.349 Because it is not just arbitrary, is it? No, 00:02:41.449 --> 00:02:43.830 not at all. Apple silicon chips have something 00:02:43.830 --> 00:02:46.949 called a neural engine. It is essentially a dedicated 00:02:46.949 --> 00:02:49.150 processor just for handling machine learning 00:02:49.150 --> 00:02:53.289 tasks efficiently. Running AI locally or even 00:02:53.289 --> 00:02:56.349 just processing screen context quickly requires 00:02:56.349 --> 00:02:59.030 a massive amount of raw computing power. And 00:02:59.030 --> 00:03:00.870 the unified memory architecture helps a lot, 00:03:00.930 --> 00:03:03.569 too. Oh, absolutely. Unified memory means the 00:03:03.569 --> 00:03:05.830 main processor and the graphics processor share 00:03:05.830 --> 00:03:08.469 the exact same pool of data. Right. So they do 00:03:08.469 --> 00:03:10.330 not have to copy information back and forth. 00:03:10.439 --> 00:03:12.340 That makes the whole system incredibly fast and, 00:03:12.360 --> 00:03:15.099 you know, super efficient. That makes total sense. 00:03:15.259 --> 00:03:19.479 It allows the AI to process visual data without 00:03:19.479 --> 00:03:22.919 lagging the whole machine. Which brings us back 00:03:22.919 --> 00:03:25.120 to that mind -bending fact from the start. The 00:03:25.120 --> 00:03:27.599 anti -gravity tool. Yeah. They built this app 00:03:27.599 --> 00:03:30.379 in just a few days using anti -gravity. But I 00:03:30.379 --> 00:03:32.620 have to push back here. Okay. If AI is building 00:03:32.620 --> 00:03:35.419 these tools so incredibly fast, doesn't that 00:03:35.419 --> 00:03:38.759 just lead to a flood of rushed buggy software? 00:03:39.370 --> 00:03:41.370 integrating into our daily workflows. Well, that 00:03:41.370 --> 00:03:43.909 is a very fair concern. Speed can definitely 00:03:43.909 --> 00:03:47.289 lead to sloppiness. But what AI coding tools 00:03:47.289 --> 00:03:49.669 like anti -gravity actually do is remove the 00:03:49.669 --> 00:03:52.270 mechanical friction. They handle the boring, 00:03:52.430 --> 00:03:54.909 repetitive parts of writing code. So like setting 00:03:54.909 --> 00:03:57.419 up the basic framework of the native app. Exactly. 00:03:57.580 --> 00:03:59.400 Writing the boilerplate code, setting up the 00:03:59.400 --> 00:04:02.080 Xcode project, compiling the basic user interface. 00:04:02.340 --> 00:04:05.159 The AI handles the grunt work there. Wow. And 00:04:05.159 --> 00:04:07.659 that leaves the human engineers completely free 00:04:07.659 --> 00:04:10.360 to focus on refining the actual user experience 00:04:10.360 --> 00:04:13.340 and the core features. So AI accelerates development, 00:04:13.659 --> 00:04:16.519 bringing tools closer to our real work much faster. 00:04:16.819 --> 00:04:19.040 Precisely. It fundamentally changes the speed 00:04:19.040 --> 00:04:20.959 limit of the tech industry. That's incredible. 00:04:21.600 --> 00:04:23.720 Let's transition to what this actually feels 00:04:23.720 --> 00:04:25.839 like to use on your machine. Yeah. Because if 00:04:25.839 --> 00:04:28.139 it was built in days, you might expect it to 00:04:28.139 --> 00:04:31.139 feel clunky. But actually opening it on the Mac. 00:04:31.560 --> 00:04:33.839 The experience is the exact opposite. It really 00:04:33.839 --> 00:04:35.600 is. The first thing that hits you is just how 00:04:35.600 --> 00:04:38.560 clean it looks. Yeah. The design is incredibly 00:04:38.560 --> 00:04:41.139 minimal compared to the bulky web interface. 00:04:41.459 --> 00:04:44.019 It feels very polished. It strips away all the 00:04:44.019 --> 00:04:46.100 visual noise of a traditional browser window. 00:04:46.300 --> 00:04:48.660 Right. And that makes a profound difference for 00:04:48.660 --> 00:04:52.060 your focus. When an app looks simple, your brain 00:04:52.060 --> 00:04:54.759 does not waste cognitive energy hunting for the 00:04:54.759 --> 00:04:57.040 right button. Tools and file attachments are 00:04:57.040 --> 00:04:59.980 grouped simply into one clean menu. You do not 00:04:59.980 --> 00:05:02.199 have to jump between. five different nested sections. 00:05:02.439 --> 00:05:04.680 Exactly. You can just drag and drop files directly. 00:05:05.000 --> 00:05:07.879 You can pull from Google Drive, Google Photos, 00:05:07.879 --> 00:05:11.100 or use creation tools from one single spot. Which 00:05:11.100 --> 00:05:14.500 brings us to the first major feature, the option 00:05:14.500 --> 00:05:17.980 plus space keyboard shortcut. Oh, this is probably 00:05:17.980 --> 00:05:20.139 the single biggest reason people will adopt this 00:05:20.139 --> 00:05:22.579 app. You just press option and space together. 00:05:23.139 --> 00:05:26.079 The Gemini interface opens instantly from anywhere 00:05:26.079 --> 00:05:28.879 on your Mac. It is very similar to how Apple's 00:05:28.879 --> 00:05:31.759 built -in spotlight search works, but it opens 00:05:31.759 --> 00:05:34.899 as a small floating chat window instead. Exactly. 00:05:35.040 --> 00:05:37.639 And crucially, it does not take over your entire 00:05:37.639 --> 00:05:40.379 screen. That is absolutely vital for maintaining 00:05:40.379 --> 00:05:42.540 your psychological flow state. Right. You ask 00:05:42.540 --> 00:05:45.300 a quick question, grab the answer, and dive straight 00:05:45.300 --> 00:05:47.180 back into your workflow without your focus getting 00:05:47.180 --> 00:05:49.870 hijacked. Yep. The second major feature centers 00:05:49.870 --> 00:05:52.189 around the built -in creation tools. This makes 00:05:52.189 --> 00:05:54.470 it a lot more than just a simple text chat bot. 00:05:54.610 --> 00:05:57.790 You can generate complex images, video, and even 00:05:57.790 --> 00:06:00.769 music right inside the same workspace. You are 00:06:00.769 --> 00:06:03.689 literally building media assets inside the floating 00:06:03.689 --> 00:06:07.050 window. It completely cuts down the need to switch 00:06:07.050 --> 00:06:09.629 over to dedicated editing apps. Now let's explore 00:06:09.629 --> 00:06:12.350 the third and honestly most critical feature, 00:06:12.670 --> 00:06:15.550 window sharing. Oh, this is definitely where 00:06:15.550 --> 00:06:17.389 the magic happens. This is where the app truly 00:06:17.389 --> 00:06:19.649 shows its potential. You can share a specific 00:06:19.649 --> 00:06:21.889 window and Gemini can actually look at your screen. 00:06:22.009 --> 00:06:24.170 Let's clarify the technical jargon here simply. 00:06:24.910 --> 00:06:28.050 Screen context means the AI sees exactly what 00:06:28.050 --> 00:06:30.889 you are looking at right now. Yes. It can process 00:06:30.889 --> 00:06:33.389 the live documents, the chaotic websites, or 00:06:33.389 --> 00:06:35.589 the dense graphs you have open. But I need to 00:06:35.589 --> 00:06:37.769 challenge this a bit. Sure. You say it is an 00:06:37.769 --> 00:06:40.670 always available system, but frankly, my Mac 00:06:40.670 --> 00:06:43.500 is already cluttered. How does an always -on 00:06:43.500 --> 00:06:46.819 AI not just become another annoying pop -up constantly 00:06:46.819 --> 00:06:49.000 demanding my attention? Well, that is the beauty 00:06:49.000 --> 00:06:51.600 of the specific shortcut design. It is not an 00:06:51.600 --> 00:06:53.600 aggressive pop -up that interrupts you. Okay. 00:06:53.680 --> 00:06:56.360 It only appears exactly when you summon it with 00:06:56.360 --> 00:06:58.959 option plus space. And regarding the clutter, 00:06:59.199 --> 00:07:02.060 window sharing actually reduces your digital 00:07:02.060 --> 00:07:04.699 mess. How so? Think about the old copy -paste 00:07:04.699 --> 00:07:07.019 loop. You mean the endless cycle of moving text 00:07:07.019 --> 00:07:10.720 between windows? Yes. Before, you found data 00:07:10.720 --> 00:07:13.660 on a website. You carefully highlighted it. You 00:07:13.660 --> 00:07:16.500 copied it. You switched over to the AI tab. You 00:07:16.500 --> 00:07:18.759 pasted it. And you pray the formatting did not 00:07:18.759 --> 00:07:21.000 break. Exactly. With window sharing, you completely 00:07:21.000 --> 00:07:23.920 bypass that entire mechanical process. You just 00:07:23.920 --> 00:07:26.339 point the AI directly at your spreadsheet or 00:07:26.339 --> 00:07:29.160 your code editor. Right. It reads the raw visual 00:07:29.160 --> 00:07:32.829 data on its own. Right. Less copying means you 00:07:32.829 --> 00:07:35.230 stay completely immersed in your actual workflow. 00:07:35.449 --> 00:07:37.850 Exactly. You eliminate the busy work so you can 00:07:37.850 --> 00:07:40.110 focus entirely on the deep thinking. We are going 00:07:40.110 --> 00:07:42.449 to take a brief pause here. Support for this 00:07:42.449 --> 00:07:44.829 deep dive comes from our partners. They help 00:07:44.829 --> 00:07:47.170 us continue exploring these complex technological 00:07:47.170 --> 00:07:49.750 shifts with you. We appreciate their commitment 00:07:49.750 --> 00:07:53.430 to bringing in -depth. accessible analysis to 00:07:53.430 --> 00:07:55.769 our listeners. If you enjoy these deep dives, 00:07:55.810 --> 00:07:57.970 please support the partners who make them possible. 00:07:58.250 --> 00:08:00.769 Now let's get back to unpacking the Gemini Mac 00:08:00.769 --> 00:08:03.550 app. Sounds good. Let's build directly on this 00:08:03.550 --> 00:08:06.410 idea of window sharing. We need to explore what 00:08:06.410 --> 00:08:09.949 you actually do when the AI can finally see your 00:08:09.949 --> 00:08:12.990 screen. Yeah, the real world use cases here are 00:08:12.990 --> 00:08:15.490 what separate this from a gimmick. It is not 00:08:15.490 --> 00:08:18.129 just for writing polite emails anymore. The source 00:08:18.129 --> 00:08:20.310 material provides some excellent concrete examples. 00:08:20.629 --> 00:08:23.050 Let's say you are staring at a dense, highly 00:08:23.050 --> 00:08:26.089 technical financial graph. Or a massive, completely 00:08:26.089 --> 00:08:28.829 chaotic Excel spreadsheet. I mean, we've all... 00:08:29.000 --> 00:08:32.120 stared blankly at one of those. Absolutely. You 00:08:32.120 --> 00:08:34.440 can trigger the shortcut and share that specific 00:08:34.440 --> 00:08:37.179 window. Then you just ask Gemini to explain the 00:08:37.179 --> 00:08:40.080 trends in plain English. That is incredibly powerful, 00:08:40.360 --> 00:08:43.720 especially when the raw data looks entirely overwhelming 00:08:43.720 --> 00:08:46.379 at first glance. It essentially acts as an instant 00:08:46.379 --> 00:08:49.419 translator for complex visual data. Right. Another 00:08:49.419 --> 00:08:52.419 fantastic use case is alongside content creation. 00:08:52.700 --> 00:08:55.730 Yeah. Imagine you have a dense research paper 00:08:55.730 --> 00:08:58.009 open on one side of your screen. You can keep 00:08:58.009 --> 00:09:00.070 that source material right where it is. You ask 00:09:00.070 --> 00:09:03.070 Gemini to draft a summary or create related graphic 00:09:03.070 --> 00:09:06.330 assets. You never leave your primary task. You 00:09:06.330 --> 00:09:09.570 are reading, analyzing, and generating new material 00:09:09.570 --> 00:09:12.169 in the exact same unified workflow. What about 00:09:12.169 --> 00:09:15.059 analyzing live websites? Because that is a massive 00:09:15.059 --> 00:09:17.740 part of modern digital work. Oh, this is a game 00:09:17.740 --> 00:09:19.779 changer for marketers and developers. You can 00:09:19.779 --> 00:09:22.320 share a live website or a complex analytics dashboard 00:09:22.320 --> 00:09:24.799 directly. You can just ask it for an immediate 00:09:24.799 --> 00:09:27.820 SEO audit based on what is visible. Or you can 00:09:27.820 --> 00:09:30.620 ask for structural redesign ideas. You get keyword 00:09:30.620 --> 00:09:33.240 optimization suggestions based entirely on the 00:09:33.240 --> 00:09:35.559 live metrics it sees. So instead of manually 00:09:35.559 --> 00:09:37.379 typing out your bounce rates, you just show it 00:09:37.379 --> 00:09:40.600 the screen. Exactly. You ask direct, highly specific 00:09:40.600 --> 00:09:43.080 questions about the visual evidence right in 00:09:43.080 --> 00:09:46.409 front of you. It is also incredibly useful for 00:09:46.409 --> 00:09:49.129 app troubleshooting. Let's walk through a practical 00:09:49.129 --> 00:09:51.809 scenario here. Okay, say you are setting up a 00:09:51.809 --> 00:09:54.889 complex workflow automation in a tool like Zapier. 00:09:54.970 --> 00:09:57.429 You are connecting two apps, but the webhook 00:09:57.429 --> 00:10:00.139 is failing and you have no idea why. Normally, 00:10:00.179 --> 00:10:02.240 you would have to take a screenshot, obscure 00:10:02.240 --> 00:10:05.100 your API keys, and post it to a forum somewhere. 00:10:05.279 --> 00:10:08.120 Yeah. Or you would copy the cryptic error code 00:10:08.120 --> 00:10:10.720 into a search engine and just hope for the best. 00:10:10.860 --> 00:10:13.080 But here you just share that specific automation 00:10:13.080 --> 00:10:16.759 window. You ask Gemini exactly why the setup 00:10:16.759 --> 00:10:19.379 is failing. It acts exactly like contextual tech 00:10:19.379 --> 00:10:21.919 support. It reads the error state and your configuration 00:10:21.919 --> 00:10:24.600 simultaneously. Let me ask you a deeper question 00:10:24.600 --> 00:10:27.200 about this dynamic. Sure. Does this specific 00:10:27.200 --> 00:10:30.080 feature transform Gemini from a passive search 00:10:30.080 --> 00:10:33.659 engine into an active shoulder to shoulder collaborator 00:10:33.659 --> 00:10:36.320 i absolutely think it does a traditional search 00:10:36.320 --> 00:10:39.620 engine is entirely passive it waits patiently 00:10:39.620 --> 00:10:43.299 for you to formulate the perfect query it relies 00:10:43.299 --> 00:10:45.779 on you to translate your visual problem into 00:10:45.779 --> 00:10:48.820 text but when the ai app is sitting directly 00:10:48.820 --> 00:10:52.299 on your desktop looking at the exact same broken 00:10:52.299 --> 00:10:55.419 automation you are staring at the entire relationship 00:10:55.419 --> 00:10:58.159 changes completely it is no longer just blindly 00:10:58.159 --> 00:11:01.539 fetching answers from the web it is active diagnosing 00:11:01.539 --> 00:11:04.480 your specific local digital environment right 00:11:04.480 --> 00:11:06.659 alongside you. Yeah, it sits right on your desktop 00:11:06.659 --> 00:11:09.200 helping you fix things in real time. That real 00:11:09.200 --> 00:11:12.639 -time shared visual context is the defining shift 00:11:12.639 --> 00:11:14.820 of this era. It sounds like a perfect productivity 00:11:14.820 --> 00:11:17.700 utopia. But we always have to pivot to the reality 00:11:17.700 --> 00:11:20.059 check. There is always a reality check in tech. 00:11:20.299 --> 00:11:22.460 Always. Especially when you are dealing with 00:11:22.460 --> 00:11:24.919 software built in a matter of days. Right. We 00:11:24.919 --> 00:11:26.799 need to look closely at the actual trade -offs. 00:11:27.139 --> 00:11:29.159 Let's start with what is actually working well 00:11:29.159 --> 00:11:31.259 right now. Well, the core foundational tools 00:11:31.259 --> 00:11:33.720 are surprisingly solid. You can switch between 00:11:33.720 --> 00:11:37.360 different backend AI models very smoothly. You 00:11:37.360 --> 00:11:39.960 can attach local files without issue. You have 00:11:39.960 --> 00:11:42.809 reliable access to your past chat history. And 00:11:42.809 --> 00:11:44.750 the Canvas feature made it into this version, 00:11:44.830 --> 00:11:47.330 too. That gives you a dedicated space for longer 00:11:47.330 --> 00:11:49.350 writing or coding projects. Though the source 00:11:49.350 --> 00:11:51.529 notes it is still missing some of the advanced 00:11:51.529 --> 00:11:54.429 editing features found on the web. Right. It 00:11:54.429 --> 00:11:57.129 works, but it is definitely a slightly stripped 00:11:57.129 --> 00:11:59.710 down version of Canvas. It manages to pull a 00:11:59.710 --> 00:12:01.370 lot of different media into one environment. 00:12:01.830 --> 00:12:04.610 But what is glaringly missing from this release? 00:12:04.909 --> 00:12:07.850 The biggest, most painful omissions right now 00:12:07.850 --> 00:12:11.429 are gems and notebooks. They are simply not available 00:12:11.429 --> 00:12:13.690 in the native app. Let's explain what those actually 00:12:13.690 --> 00:12:16.610 are. Why does missing them matter so much? Notebooks 00:12:16.610 --> 00:12:19.860 essentially act as a personalized AI brain. You 00:12:19.860 --> 00:12:22.720 upload your specific documents and the AI only 00:12:22.720 --> 00:12:24.879 uses that trusted information to answer you. 00:12:25.019 --> 00:12:27.240 It is a process called retrieval augmented generation, 00:12:27.360 --> 00:12:30.399 right? Exactly. It gives the AI a specific folder 00:12:30.399 --> 00:12:32.879 of your documents to reference. And gems are 00:12:32.879 --> 00:12:35.419 similar. They are customized AI personas you 00:12:35.419 --> 00:12:38.440 build for very specific repeatable tasks. So 00:12:38.440 --> 00:12:41.419 if you have spent months building these custom 00:12:41.419 --> 00:12:43.700 environments on the web, they just do not exist 00:12:43.700 --> 00:12:46.440 here. Right. The synchronization between the 00:12:46.440 --> 00:12:49.500 web platform and the native Mac app. is currently 00:12:49.500 --> 00:12:52.539 broken for those features. That completely fractures 00:12:52.539 --> 00:12:54.159 the unified experience they're trying to sell. 00:12:54.299 --> 00:12:58.100 It does. Also, the fully seamless conversational 00:12:58.100 --> 00:13:01.779 live voice experience is not ready yet. There 00:13:01.779 --> 00:13:04.080 is a basic speech -to -text setting buried inside 00:13:04.080 --> 00:13:06.480 the app right now. Yeah, it clearly suggests 00:13:06.480 --> 00:13:09.200 Google is laying the groundwork for it, but the 00:13:09.200 --> 00:13:12.600 fluid two -way conversational voice feature just 00:13:12.600 --> 00:13:15.899 is not functional today. Let me probe a bit on 00:13:15.899 --> 00:13:18.049 the missing notebooks. Okay. Doesn't this break 00:13:18.049 --> 00:13:21.330 the brain of a power user? Do these missing features 00:13:21.330 --> 00:13:23.690 make the app too frustrating to actually use 00:13:23.690 --> 00:13:26.490 right now? It is definitely a massive point of 00:13:26.490 --> 00:13:28.929 friction for power users. People build incredibly 00:13:28.929 --> 00:13:31.269 complex workflows around their custom notebooks. 00:13:31.470 --> 00:13:34.570 They curate highly specific knowledge bases over 00:13:34.570 --> 00:13:37.250 months. When those do not smoothly sync over 00:13:37.250 --> 00:13:39.789 to the new desktop app, you essentially end up 00:13:39.789 --> 00:13:42.649 with two entirely different AI brains. You have 00:13:42.649 --> 00:13:45.809 your smart... customized web brain and your somewhat 00:13:45.809 --> 00:13:49.490 amnesiac native app brain it actively forces 00:13:49.490 --> 00:13:52.210 the user to constantly remember which platform 00:13:52.210 --> 00:13:55.169 holds which context that sounds exhausting it 00:13:55.169 --> 00:13:57.690 absolutely creates frustration if you rely heavily 00:13:57.690 --> 00:13:59.970 on those meticulously organized environments 00:13:59.970 --> 00:14:03.070 got it it's early but the sheer speed outweighs 00:14:03.070 --> 00:14:05.610 the temporary missing pieces for most standard 00:14:05.610 --> 00:14:09.190 daily tasks yes the sheer speed of hitting option 00:14:09.190 --> 00:14:12.779 plus space is just too powerful to ignore So 00:14:12.779 --> 00:14:15.100 looking ahead, what is next for this application? 00:14:15.419 --> 00:14:17.799 The billetment roadmap seems pretty transparent. 00:14:18.269 --> 00:14:20.690 Google is clearly aiming for complete feature 00:14:20.690 --> 00:14:23.450 parity across your phone, the web, and the Mac 00:14:23.450 --> 00:14:26.149 app. So those frustrating missing pieces like 00:14:26.149 --> 00:14:28.470 notebooks and live voice features will eventually 00:14:28.470 --> 00:14:30.909 arrive. Undoubtedly. But beyond just catching 00:14:30.909 --> 00:14:32.929 up to the web, the ultimate goal is making the 00:14:32.929 --> 00:14:35.409 app much more agent -like. Meaning deeper access 00:14:35.409 --> 00:14:37.929 to your local file system, better integration 00:14:37.929 --> 00:14:40.470 across your entire operating system. Exactly. 00:14:40.590 --> 00:14:43.210 It shows exactly where the entire Gemini ecosystem 00:14:43.210 --> 00:14:46.169 is heading, even if this specific app is not 00:14:46.169 --> 00:14:49.029 fully mature yet. Let's take a moment to synthesize 00:14:49.029 --> 00:14:51.450 everything we have unpacked today. I think this 00:14:51.450 --> 00:14:54.370 release is a massive, highly consequential step 00:14:54.370 --> 00:14:57.929 forward for desktop AI. I agree. The Gemini Mac 00:14:57.929 --> 00:15:00.789 app is not just another standard product update 00:15:00.789 --> 00:15:03.450 you scroll past. It represents a fundamental 00:15:03.450 --> 00:15:06.490 philosophical shift in computing. Yeah, it really 00:15:06.490 --> 00:15:09.370 does. This is the exact moment AI officially 00:15:09.370 --> 00:15:12.850 stopped being a destination. You no longer have 00:15:12.850 --> 00:15:15.669 to deliberately travel to a browser tab to visit 00:15:15.669 --> 00:15:18.269 it. Exactly. It has officially become an ever 00:15:18.269 --> 00:15:21.230 -present, invisible layer woven into your operating 00:15:21.230 --> 00:15:23.990 system. It is demonstrably faster, it demands 00:15:23.990 --> 00:15:26.450 less friction, and it feels vastly more natural 00:15:26.450 --> 00:15:28.830 to use. If you are listening to this right now, 00:15:28.929 --> 00:15:31.190 I highly encourage you to check your system specs. 00:15:31.389 --> 00:15:33.370 See if you have an Apple Silicon Mac running 00:15:33.370 --> 00:15:35.830 macOS Sequoia. Yeah, and if you do meet the requirements, 00:15:36.049 --> 00:15:38.590 go download the app. Try integrating that Option 00:15:38.590 --> 00:15:41.600 Plus Space shortcut into your work today. Seriously, 00:15:41.700 --> 00:15:44.519 see how it alters your own flow state? Notice 00:15:44.519 --> 00:15:46.799 how fundamentally different it feels to have 00:15:46.799 --> 00:15:49.559 an intelligent assistant quietly sitting directly 00:15:49.559 --> 00:15:52.139 on top of your work, rather than hiding behind 00:15:52.139 --> 00:15:55.120 a web address. It really is a tactile shift. 00:15:55.240 --> 00:15:57.240 It is something you genuinely have to feel to 00:15:57.240 --> 00:16:00.500 fully understand the impact. The source material 00:16:00.500 --> 00:16:03.179 leaves us with a fascinating note. It points 00:16:03.179 --> 00:16:05.200 out that the entire industry is aggressively 00:16:05.200 --> 00:16:07.639 pushing toward future computer use features. 00:16:08.870 --> 00:16:10.710 I want you to really think about the trajectory 00:16:10.710 --> 00:16:13.990 here. We started this deep dive by talking about 00:16:13.990 --> 00:16:16.789 an AI coding tool that built this very application 00:16:16.789 --> 00:16:20.490 in a matter of days. We have established that 00:16:20.490 --> 00:16:23.590 the AI can perfectly see your screen. It can 00:16:23.590 --> 00:16:26.230 audit a live website visually. It can look at 00:16:26.230 --> 00:16:28.370 a messy Zapier dashboard and troubleshoot a broken 00:16:28.370 --> 00:16:31.350 app. If it can already see, analyze, and understand 00:16:31.350 --> 00:16:34.269 your screen perfectly, how long until it doesn't 00:16:34.269 --> 00:16:36.110 just give you polite advice but actually reaches 00:16:36.110 --> 00:16:38.549 out, takes control of the mouse, and fixes the 00:16:38.549 --> 00:16:39.690 broken automation for you?