HackerNews中文版

在过去的一年里，我一直在开发 GM Pro——一个提升 Google Meet 聊天体验的 Chrome 扩展程序。一开始很简单：反应、回复、提及、聊天的黑暗模式。然后我添加了自动加入、自动静音、转录工具、大厅通知、与会者随机分配。基本上就是你希望 Meet 聊天默认具备的所有功能。人们对此非常喜爱，获得了五星好评，安装量稳定，实际使用频繁。然而，在多年乏善可陈的聊天体验后，谷歌宣布将 Meet 聊天与 Google Chat 直接整合——持久的对话、反应、文件共享等等。这意味着……我所构建的功能正好成为了一个第一方特性。一方面，这验证了我的想法。方向是正确的，需求是真实的。另一方面，平台风险让我感到措手不及。当你在一个巨型平台上构建时，实际上是在为他们原型设计功能。如果这个功能有效，他们会吸收它；如果无效，你就会悄然消失。无论如何，他们都是赢家。现在我在思考：我是否应该转向那些谷歌不会优先考虑的强用户工具？加大对自动化和工作流功能的投入？还是远离聊天，转向会议智能？或者接受消费者 Chrome 扩展程序在核心用户界面上本质上是脆弱的？我很好奇其他开发者是如何看待平台依赖性的。你是否曾经在所构建的平台上经历过产品被“Sherlocked”的情况？你接下来做了什么？

查看原文

For the past year, I’ve been building GM Pro — a Chrome extension that upgrades the chat experience inside Google Meet.It started simple: reactions, replies, mentions, dark mode for chat. Then I added auto-join, auto-mute, transcription tools, lobby notifications, attendee shuffling. Basically all the things you wish Meet chat had by default.People loved it. 5-star reviews. Steady installs. Real usage.And then, after many years of lackluster chat, Google announced they’re integrating Meet chat directly with Google Chat — persistent conversations, reactions, file sharing, the works.Which means… the exact surface area I built on top of is becoming a first-party feature.On one hand, this validates the idea. The direction was right. The need was real.On the other hand, platform risk just punched me in the face.When you build on top of a giant platform, you’re effectively prototyping features for them. If the feature works, they absorb it. If it doesn’t, you disappear quietly. Either way, they win.Now I’m thinking through:Do I pivot to power-user tools Google won’t prioritize?Double down on automation and workflow features?Move away from chat and toward meeting intelligence?Or accept that consumer Chrome extensions sitting on core UI are inherently fragile?Curious how other builders here think about platform dependency.Have you ever had your product “Sherlocked” by the platform you’re building on? What did you do next?

谷歌刚刚终止了我的项目。