Google Dropped Too Many AI Tools. Which Ones Matter?

Drew and Rory are back for episode 69, which is legally required to begin with at least one immature joke before immediately collapsing under the weight of Google’s latest AI product avalanche.This week, they dig into Google Omni, Gemini 3.5 Flash, Google Flow, Google Pics, Nano Banana, Veo, and whatever else Google launched before anyone had time to make coffee. The big question: are these actually meaningful creative upgrades, or did Google just throw 19 AI names into a blender and call it innovation?They break down early Omni and Flow tests, why video physics still feel weird, where Seedance and Kling may still be ahead, and why Runway Aleph 2.0 feels promising but imperfect. Rory shares hands-on examples with character swaps, driving videos, golf swings, agent mode, and Flow’s new tool-building features. Drew tries to keep the conversation coherent while quietly wondering if every AI product now needs a map, glossary, and mild sedative.The episode also gets into Gemini as a search replacement, creepy context awareness, privacy tradeoffs, AI tools connecting to personal data, the fuzzy definition of “agentic,” the limits of auto-clipping tools, GPT Image 2’s SynthID watermarking, metadata headaches for client work, and the universal pain of wasting $15 trying to make an image model spell “stump.”If you’re trying to understand what Google’s AI updates actually mean for creators, marketers, AI video workflows, image generation, creative direction, and the future of agentic media tools, this episode is half useful breakdown, half group therapy for people with too many tabs open.---⏱️ Fast Hour00:00 Cold open00:32 Google’s AI naming avalanche01:39 AI hype vs actual workflow value02:34 Why AI launches feel like iPhone upgrades06:12 Google’s “throw everything” strategy07:08 Omni vs Veo 4 expectations07:43 Video physics and speed problems09:03 Google Pics, Flow, Omni, and Flash10:04 How Rory actually uses Gemini11:51 Gemini 3.5 Flash breakdown12:38 AI benchmarks feel like marketing13:42 Gemini as a better search layer15:18 Creepy Gemini context awareness17:35 Why AI data connections feel too early19:15 The privacy tradeoff gets darker21:19 Google Omni vs Runway Aleph 2.022:12 Google Omni testing starts rough23:39 Google Veo 3.1 feels forgettable25:21 Why Omni feels early26:19 Higgsfield clipper test fails27:59 Why auto-clipping still misses31:30 Rory tests Flow and Omni live32:41 Omni character swap struggles33:33 Runway Aleph panda test34:07 Flow’s new interface and tools35:02 Building custom tools inside Flow36:10 The joy of making tools from nothing37:39 Agent mode for still-image workflows39:05 Batch creative directions in Flow40:03 Omni turns six images into video40:47 Driving physics still feel off41:55 Why consistency matters for adoption43:03 Kling, Seedance, and the update race43:59 Seedance handles complex camera motion45:42 GPT Image setup for golf video46:53 Testing the same prompt in Flow49:25 Why agentic platforms can feel thin51:10 The need for visual design systems52:21 Flow’s golf swing result53:56 Everyone is racing toward agentic54:18 What “agentic” actually means56:03 Claude feels more genuinely agentic57:04 Josh Hart quote analysis detour58:44 Reverse-engineering creative patterns59:53 Pizza, calzones, and prompt structure01:00:26 SynthID and GPT Image 2 watermarking01:01:47 Metadata problems for client work01:02:51 Google Pics enters the chat01:04:03 Too many image models to track01:04:52 Midjourney color still hits different01:06:01 GPT Image 2 quality frustration01:06:59 Image models still struggle with scale01:08:26 Bad AI weeks happen too01:09:20 Midjourney 8.2 speculation01:10:01 Tell your florist