bamnet

K-Anonymity isn't the only technique. Differential Privacy is arguably more robust.

This isn't just a theoretical point. Chrome extensions are the canonical example of products which start off with the best intentions, get acquired, and then ...

It's a super cool API, but last I chatted with the team who maintains this (~2020?) it was already understaffed and they only had capacity for bug fixes. The roadmap hasn't been updated since 2017 so YMMV.

This isn't how it works. The Google Maps API doesn't know where users are.

Instead, it's probably being used for an autocomplete widget to help users type in an address.

Last I checked the new Google Maps licensing [1] is a bit more permissive, placing no restrictions on the behind a login bit.

The Google Maps JavaScript API does support UIWebView [2] so it should work embedded on iOS. There's a native SDK too.

[1] https://cloud.google.com/maps-platform/terms/ [2] https://developers.google.com/maps/documentation/javascript/...

Users are never happy with chatbots, but they can be happy with chat experiences if they never realize there's a bot behind the scenes.

GEE lets you take a lots of imagery and vector data and process it together so that it can be displayed on Google Earth or anything that can render simple imagery tiles like the Google Maps API. It can run locally / on prem which is a big benefit if connectivity is a challenge for your business or end-users. Previously, this was something Google sold but was deprecated a few years ago. Now that it's open source people can keep using it :-)

Disclaimer: I work for Google, but not on GEE.

You should probably migrate to the V3 API.