I follow an 80/20 rule with both Google Maps and Google Translate: 80% of the time it's ok, 20% of the time though, it'll get you in serious trouble.
I recall testing out various apps and one time in NL, a place with no shortage of official bike paths, GM was directing me across a field. Not a field with a path. Just a field.
Another time, it was telling me I was in Belgium when I was definitely in NL. Osmand, on the same phone, had my location accurately, GM for whatever reason didn't.
In more far off places, taking a rest on a long, uphill day, I tried again and the elevation info it gave was something like "mild climb" and the graphic looked very benign. Osmand set me straight! Another time, very tired, hungry, thirsty and trying to be smart with CycleTravel I pulled out GM to save a km. How bad could it be? Bloody dangerous is what it was. Back to CT and the slightly longer way.
It has its uses in touring, especially the ability to "load up" a map with useful services/locations that can be accessed offline, and to track your travels (both Maps and Photos do this) but for navigation on a bike? Just no. It can also be useful for landslide, flooding and wildfire warnings
I think there's a cohort of people who "switch off" when an app plots a route, follow it slavishly and stop thinking critically. Not a great idea on a bike.