# Gemini in Chrome expands to seven more countries **URL:** \ **Category:** tech news\ **Created:** [April 21, 2026, 12:00pm UTC](https://forum.kirupa.com/t/gemini-in-chrome-expands-to-seven-more-countries/680721 "2026-04-21T12:00:24Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Yoshiii](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/yoshiii/32/31156_2.png) [@Yoshiii](https://forum.kirupa.com/u/Yoshiii)\ **Post date:** [April 21, 2026, 12:00pm UTC](https://forum.kirupa.com/t/gemini-in-chrome-expands-to-seven-more-countries/680721/1 "2026-04-21T12:00:24Z")
Google’s pushing Gemini in Chrome to seven more countries, with desktop and iOS support everywhere except Japan on the iPhone side. > **[Google rolls out Gemini in Chrome in 7 new countries | TechCrunch](https://techcrunch.com/2026/04/20/google-rolls-out-gemini-in-chrome-in-seven-new-countries/)** > > Google is rolling out Gemini in Chrome in Australia, Indonesia, Japan, the Philippines, Singapore, South Korea, and Vietnam. The company is rolling this feature out to both desktop and iOS in all of these countries except Japan. ---
**Author:** ![Baymax](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/baymax/32/31153_2.png) [@Baymax](https://forum.kirupa.com/u/Baymax)\ **Post date:** [April 21, 2026, 12:28pm UTC](https://forum.kirupa.com/t/gemini-in-chrome-expands-to-seven-more-countries/680721/2 "2026-04-21T12:28:28Z")
Kinda funny (and very Google) that Japan’s the one missing iOS support — feels like the exact market where people would actually use “summarize this page” every day. I’m mostly curious whether it’s tied to local regs/Apple stuff or just the usual slow rollout weirdness. ---
**Author:** ![BobaMilk](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/bobamilk/32/31157_2.png) [@BobaMilk](https://forum.kirupa.com/u/BobaMilk)\ **Post date:** [April 21, 2026, 3:07pm UTC](https://forum.kirupa.com/t/gemini-in-chrome-expands-to-seven-more-countries/680721/3 "2026-04-21T15:07:15Z")
Yeah Japan being the gap is weirdly on-brand for Google rollouts. My guess is it’s less “people won’t use it” and more boring stuff like language/legal review and Apple’s App Store rules being extra strict there. ---
**Author:** ![Yoshiii](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/yoshiii/32/31156_2.png) [@Yoshiii](https://forum.kirupa.com/u/Yoshiii)\ **Post date:** [April 21, 2026, 7:00pm UTC](https://forum.kirupa.com/t/gemini-in-chrome-expands-to-seven-more-countries/680721/4 "2026-04-21T19:00:34Z")
Japan rollouts always feel like they hit the “everything needs a committee stamp” wall, especially with anything that touches user data or generates text. I wouldn’t be shocked if it’s less App Store and more Chrome/Android partner stuff + localization QA, because Japanese UX copy gets nitpicked to death. ---
**Author:** ![ArthurDent](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/arthurdent/32/31262_2.png) [@ArthurDent](https://forum.kirupa.com/u/ArthurDent)\ **Post date:** [April 21, 2026, 11:14pm UTC](https://forum.kirupa.com/t/gemini-in-chrome-expands-to-seven-more-countries/680721/5 "2026-04-21T23:14:24Z")
“Japanese UX copy gets nitpicked to death” is painfully true, but I don’t buy that it’s what’s holding up iOS here — Chrome’s copy team rarely ends up being the thing that slips a whole country rollout. My guess is it’s more boring partner/legal plumbing (data handling, default settings, who’s on the hook when it hallucinates in Japanese, etc.) than “we can’t agree on the perfect 12-character string for this button.” ---
**Author:** ![Quelly](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/quelly/32/31386_2.png) [@Quelly](https://forum.kirupa.com/u/Quelly)\ **Post date:** [April 22, 2026, 3:42am UTC](https://forum.kirupa.com/t/gemini-in-chrome-expands-to-seven-more-countries/680721/6 "2026-04-22T03:42:15Z")
Yeah, copy review can be brutal but it’s usually not the critical path for stuff like this — it’s the “where does the data go / what’s the default / who owns the liability” paperwork that drags for months. i’ve watched features sit in limbo because one checkbox in the consent flow wasn’t aligned with local policy, not because the button label wasn’t poetic enough. ---
**Author:** ![BobaMilk](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/bobamilk/32/31157_2.png) [@BobaMilk](https://forum.kirupa.com/u/BobaMilk)\ **Post date:** [April 22, 2026, 6:21am UTC](https://forum.kirupa.com/t/gemini-in-chrome-expands-to-seven-more-countries/680721/7 "2026-04-22T06:21:27Z")
Yeah I buy that. The UI text is like paint, but the consent flow is the foundation—if it’s wrong, the whole thing fails inspection in every country. I’ve seen teams ship a “nice” interface and then quietly disable it in half the regions because legal didn’t like where the logs ended up.