Moneycontrol

Google quietly kills the Nest Hub app grid, years after launching it

Google has effectively phased out the app-style interface on Nest Hub smart displays. What began as a convenience feature in 2021 has now almost entirely vanished, with only a handful of services still visible. The change appears gradual rather than sudden, but it signals yet another simplification of Google’s smart display experience.

January 31, 2026 / 21:00 IST
Story continues below Advertisement
Google Nest Hub
Snapshot AI
  • Google Nest Hub's app grid interface has quietly disappeared from all models
  • Only a few shortcuts like Search and YouTube TV remain on the home screen
  • Google has not officially explained the removal of most app-style shortcuts

Google’s smart displays have changed significantly since their early years, and one of the more subtle shifts has now become hard to ignore. The app-style shortcuts that once lived on the home screen of the Google Nest Hub are largely gone.

Back in 2021, Google rolled out an update that introduced a grid of touch-friendly “apps” on Nest Hub devices. The idea was simple and sensible. Instead of relying entirely on voice commands, users could tap icons to jump straight into common actions like checking the weather, starting a timer, or opening YouTube. For a product with a touchscreen, it felt like a step towards making the display more self-sufficient.

Story continues below Advertisement

Fast forward to today, and that interface has almost completely disappeared. Reports over the past year, first spotted by users on Reddit, suggest that the app grid is no longer available on Nest Hub devices. What remains is a very slim list, including Search, YouTube TV, Sling TV, and Stories. Everything else has quietly vanished.

This is not limited to one model or generation. Checks across the Nest Hub Max, the original Nest Hub, and the second-generation Nest Hub all show the same outcome. The team at Android Authority has also confirmed identical behaviour across their own devices, suggesting this is a platform-wide change rather than a regional bug or temporary glitch.