The thing is that Google maps is so old and the api is so domain specific, it doesn't need to change. The data required is just maps.google.com/v2/<z>/<x>/<y>.p

The thing is that Google maps is so old and the api is so domain specific, it doesn't need to change. The data required is just maps.google.com/v2/<z>/<x>/<y>.png There are new things like vector tiles with multiple layers of vector data, so we will definitely see more breakage with clients using that. And the routing is response JSON also had a stable layout. It's not hard to continue to support these api because the type of data they send doesn't change. Google also versions, and accounts and charges for the api usage. I wish there was more standardization for calendar data but many calendars, including Google, like to mess with the the underlying data and functionality, and there is not ground truth like xyz to really ground them =)