> The root problem is that permissions right now are super hard to adjust for users
Unlike you I'm not getting paid enough by google to accept this narrative. The root problem for google is "high denial rates" of geolocation prompts, as clearly stated by Google in the post.
Now please tell me what information the geolocation prompt actually provides to the website that cannot be taken from the IP address, which is already tracked and processed by google and every single website tracking tool. IP address tells the website about the city where users come from.
The root problem with "high denial rates" is that Google wants to know if you live in the rich part of town or in the poor part of town. This is why google engineers try to find new ways for users to permanently undo their blocking of geolocation permission.
If google engineers had any concern about their users, then the default option would be a way to temporarily allow geolocation for duration of the browser session, e.g. when you need to really use google maps. And after the browser window closes it would later go back to the previously blocked state from before.
It's a cognitive dissonance.
> Now please tell me what information the geolocation prompt actually provides to the website that cannot be taken from the IP address, which is already tracked and processed by google and every single website tracking tool.
Show me the bus schedule for the nearest bus stop, show me the nearest store, share my location in a chat..
The browser's IP-based geolocation (as per what https://mylocation.org/ can find out from my session) is kilometers away.