Google’s pushing Gemini in Chrome to seven more countries, with desktop and iOS support everywhere except Japan on the iPhone side.
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.
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.
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.
“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.”
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.
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.
