HN Debrief

I Fired Google

  • AI
  • Consumer Tech
  • Privacy
  • Developer Tools

The post is a consumer rant about a familiar pattern. Google Home used to be useful for small, specific jobs like music, timers, weather, and quick facts. After Google pushed Gemini-style AI into the experience, those same requests became slower, wordier, and less reliable. The author frames it as a classic "upgrade" that made a working product worse and says they gave up and bought an Alexa instead.

If you ship voice or agent features, protect the narrow high-frequency tasks first and treat verbosity and unpredictability as product regressions, not personality. There is also an opening for simpler local or tightly scoped assistants that do a small set of commands fast and consistently.

Discussion mood

Mostly frustrated and resigned. People feel Google made a once-useful appliance worse by swapping deterministic command handling for verbose, flaky LLM behavior, and many think Amazon is following the same path rather than offering a real alternative.

Key insights

  1. 01

    Appliance jobs beat conversational intelligence

    The useful frame is that smart speakers succeeded as tiny appliances, not as general AI. People reliably want a few hands-free actions like music, alarms, lights, timers, reminders, and weather. Once the product moved from crisp command execution toward open-ended conversation, it got worse at the jobs that justified owning it in the first place. The strongest version of this point came from the timer example. A motivated user was willing to learn a verbal command language, but the product offered no discoverable syntax, no documentation, and no path to mastery.

    Treat voice control as an interface to a bounded command system. If your product cannot expose capabilities clearly enough for power users to learn and rely on them, it will never feel dependable to mainstream users either.

      Attribution:
    • bsimpson #1
    • Xeoncross #1
    • RajT88 #1
    • cfiggers #1
  2. 02

    LLM turn-taking is a bad fit for interruption

    The annoying part is not just verbosity. It is that token-by-token chat systems are poor at stopping, yielding, or recognizing that the user wants the interaction to end. That makes normal assistant behavior feel combative. Instead of doing one thing and shutting up, the system keeps asking follow-ups, restarts itself on ambient noise, or cannot cleanly honor "stop" in the middle of speech. In a car or while using tools, that is not a cosmetic flaw. It makes voice interaction feel physically hostile.

    If you add an LLM to a voice product, build interruption, cancel, and silence as first-class control paths outside the model. Do not rely on the model alone to decide when to stop talking.

      Attribution:
    • dminik #1
    • aNapierkowski #1
    • aliasxneo #1
    • ravetcofx #1
  3. 03

    Local voice stacks are now viable

    A practical replacement path is emerging for people who only need a safe subset of actions. One commenter described a home setup using openWakeWord, faster-whisper, Orpheus-TTS, Gemma, and a Raspberry Pi satellite, with web search, reminders, file context, memory, and barge-in. Another commenter wanted exactly a "dumb smart speaker" wired to their own API and tools like Wikipedia, recipes, and music control. The point is not that everyone will self-host. It is that the component stack now exists for focused assistants that stay local, respond fast, and avoid the product incentives that cause cloud assistants to get chatty and promotional.

    There is room for products built around local processing or tightly scoped tool use instead of ad-driven engagement. If you operate in this space, speed, privacy, and bounded actions are stronger differentiators than trying to out-chat the big platforms.

      Attribution:
    • pwython #1 #2
    • data-ottawa #1
  4. 04

    Mainstream users are now saying it out loud

    What gave the post extra weight was not technical novelty. It came from where the complaint came from. A home and lifestyle blog reaching this level of irritation signals that dissatisfaction has escaped the usual tech bubble. When nontechnical users start treating Google products as unreliable appliances instead of trusted defaults, that is a demand problem, not just a reputation problem among enthusiasts.

    Watch mainstream trust indicators, not just power-user sentiment. Once basic reliability complaints show up in broad consumer channels, switching costs stop protecting incumbents as much as they used to.

      Attribution:
    • krabizzwainch #1

Against the grain

  1. 01

    Prompt defaults can tame Gemini somewhat

    One commenter said a blunt default instruction set, described as "caveman instructions," made Gemini much more usable across logged-in surfaces including Android Auto. That does not fix the deeper product direction, but it suggests some failures are caused by default assistant behavior rather than hard capability limits.

    If you are stuck with Gemini, test strong custom instructions before abandoning it. Product teams should also notice that users are hand-rolling brevity and directness because the defaults are wrong.

      Attribution:
    • ihaveone #1
  2. 02

    Some people prefer the smarter assistant

    Not everyone sees the old assistant as the gold standard. One commenter said Gemini on Google Home feels much better because the earlier system was too limited. That is a reminder that richer reasoning does create value for users who want broader queries and do not mind a more conversational interaction style.

    Segment the product instead of forcing one behavior on everyone. Fast deterministic mode and open-ended chat mode should be separate choices, especially on shared household devices.

      Attribution:
    • CephalopodMD #1

In plain english

Android Auto
Google’s in-car interface that lets an Android phone handle navigation, music, messages, and voice control through a car display.
faster-whisper
An optimized implementation of OpenAI’s Whisper speech-to-text model for transcribing audio.
Gemini
Google’s family of artificial intelligence models and assistant features that replaced or augmented older Google Assistant behavior.
LLM
Large Language Model, an AI system trained to generate and analyze text.
openWakeWord
An open-source tool for detecting custom wake words like 'Hey Assistant' from audio input.
Orpheus-TTS
A text-to-speech system that turns generated text into spoken audio.

Reference links

DIY local assistant tools

  • alisorcorp GitHub profile
    Planned repository for a commenter’s local voice assistant setup built as a Google Home replacement.

Ad blocking and security guidance

BMW heated seats references

Related Google criticism