Google Chrome 150 for Android Adds Dedicated Back Button in Major UI Update
Google has commenced the wide distribution of Google Chrome version 150 for Android, introducing one of the most substantial structural redesigns to its overflow menu in recent history. The headline change addresses a long-standing parity gap with the iOS iteration of the mobile browser: a native, dedicated on-screen Back button inside the application interface.
While Android users have traditionally relied on system-level swipe gestures or physical navigation controls to step back a page, the inclusion of a dedicated layout control inside the browser targets immediate quality-of-life adjustments for large-screen tablets, foldables, and one-handed accessibility.
What’s New in Chrome 150’s Three-Dot Menu?
The introduction of the Back button has triggered a domino effect across the iconic top shortcut row of Chrome’s three-dot menu. To map out how these alterations impact muscle memory, the mechanical layout adjustments are detailed below:
| Old Overflow Menu Configuration | New Chrome 150 Layout |
| Top Row Controls: Forward Arrow, Bookmark (Star), Download (Down Arrow), Page Info (“i”), Refresh | Top Row Controls: Back Arrow, Forward Arrow, Bookmark (Star), Download (Down Arrow), Refresh |
| Information Gateway: Page Info (“i”) shortcut inside the top row | Information Gateway: Removed from top row; replaced by scrollable Site controls lower down |
| Shortcut Labeling: “Add to Home screen” | Shortcut Labeling: “Install and create shortcut” |
By dropping the long-standing Info (“i”) button from the top horizontal header strip, the bookmark and download icons have shifted exactly one spot to the right. Power users should expect a brief adjustment phase as old muscle memory recalibrates to the new tap points.
What’s New in Google Chrome 150?
1. Unified Navigation Strip
Previously, Chrome’s top menu row was asymmetrical, only showing a Forward arrow that remained grayed out until a user had already triggered a system-level back gesture. Version 150 pairs the Back and Forward arrows symmetrically, standardizing the application layout across both Android and iOS ecosystem footprints.
2. Consolidated “Site Controls” Hub
Rather than locking individual permissions away inside an isolated icon at the top of the menu, a new Site controls line item has been embedded directly into the scrollable list below. Tapping this opens a centralized dashboard where users can quickly modify granular, per-site parameters:
- Camera and microphone accessibility toggles.
- Localized notification rules.
- Geographical location access.
- Active cookie states and third-party privacy rules.
3. Clearer PWA and Shortcut Labeling
The rebranding of “Add to Home screen” to “Install and create shortcut” resolves long-standing backend syntax confusion. When visiting a site configured as a Progressive Web App (PWA), tapping the option cleanly installs it as a standalone app framework; when visiting standard pages, it creates a traditional launcher shortcut.
How to Get Chrome 150’s New Menu
Important Rollout Note: Google is deploying this interface update via staggered server-side parameter changes. Testing reveals that the menu state and your application version are currently independent; some users on Chrome 149 already have the button, while others on stable Chrome 150 are still waiting for the UI flag to flip.
To force a refresh and check your active environment state, follow this sequence:
1. Initiate Play Store Update Check: Step 1.
Open the Google Play Storetap your profile icon in the upper right corner, and select Manage apps and devices to download the latest Chrome 150 stable release package.

2.Access Application Diagnostics: Step 2.
Launch Chrome, tap the three-dot menu, scroll to the bottom, and choose Settings > About Chrome. Verify that the base application version string reads 150.x or higher.
3. Force Application Clear (Optional): Step 3.
If you are on version 150 but the old menu still shows, open your phone’s central Settings > Apps > Manage Apps > Chrome and tap Force Stop. Re-launching the application will force it to pull down the newest server-side UI flag configurations from Google’s servers.
Comments are closed.