Moments in Chromecast's history

Original Article ↗ Hacker News Discussion ↗

Google’s decision to end production of Chromecast dongles and replace them with a pricier “Google TV Streamer” box has sparked concern about rising costs, added complexity and heavier emphasis on ads and AI features. Many users valued the original Chromecast for its cheap, phone-centric, plug‑and‑play casting model—especially for travel, guests, multi-room audio and retrofitting “dumb” TVs—and worry that this simple, device-agnostic experience is being displaced by app-centric, account-bound smart TV platforms. The shift also renews calls for an open casting standard and reinforces broader skepticism about Google’s product longevity and ecosystem lock-in.

What Changed

  • Google is ending production of Chromecast dongles (including “Chromecast with Google TV”) and introducing the more expensive, box‑style Google TV Streamer.
  • The Cast protocol and “cast button” UX are expected to continue; many TVs and third‑party devices already implement casting.

Hardware, Pricing, and Form Factor

  • Old HD/4K Chromecasts at ~$30–50 were praised as great value; the new Streamer at $99 is widely seen as overpriced, especially given a 2021 SoC, Wi‑Fi 5, and modest CPU gains.
  • Many liked the dongle form factor: invisible behind the TV, powered by TV USB, ideal for travel/Airbnbs.
  • Others welcome a set‑top box for better thermals, more RAM, and hopefully smoother performance, noting current Chromecasts have become sluggish over time.
  • Several compare it unfavorably to Apple TV and Nvidia Shield on performance, and to Roku/Onn on price.

UX: Casting vs Smart TV Box

  • Strong nostalgia for the original Chromecast model: phone/laptop as remote, TV as dumb receiver, no login, minimal UI, guests can cast from their own apps.
  • The Google TV paradigm (apps, home screen, mandatory Google login, profiles) is seen by some as a privacy and UX regression, especially in multi‑user/guest contexts.
  • Others argue most people now prefer a remote‑driven, app‑centric device, and that rebranding away from “Chrome” reflects this shift.

Ads, Tracking, and “AI”

  • Heavy criticism of ads on home screens (Google, Fire TV, Roku) and smart‑TV tracking; some keep TVs offline and use external boxes only.
  • AI features like show/movie summaries on the new device are widely mocked as useless marketing, unlikely to run locally and mainly a pretext for more engagement/ads.

Alternatives and Replacements

  • Frequent mentions of Apple TV (performance, price premium, fewer ads), Roku (simple but increasingly ad‑heavy), Nvidia Shield (codec/HD‑audio support), Walmart Onn and TiVo Stream (cheap Android TV with Cast).
  • For multi‑room audio / Chromecast Audio replacement: suggestions include WiiM, networked receivers with “Cast for Audio,” and open‑source stacks like Snapcast or soundsync.

Open Protocols and DIY

  • Strong desire for an open, Chromecast‑like standard. Discussed options: Miracast, DLNA, DIAL, Open Screen Protocol, Matter Cast; each has limitations (battery, latency, DRM, app requirements).
  • Some plan to pivot to Raspberry Pi / HTPC solutions plus software (Kodi, Jellyfin, DLNA, etc.) instead of proprietary dongles.

Trust in Google

  • Many see this as another example of “Killed by Google,” say they’ll avoid new Google hardware, and worry about support ending and devices becoming e‑waste.
  • A minority view it as a normal rebrand/hardware refresh rather than a true product killing.