I chalk this up to Google Maps' overall bloat and sluggishness on my 2-year-old phone.
The music just cuts out for a few seconds, but there's no navigation audio.
I've turned off navigation prompts for that reason, and just check the "next turn" thing at the top every now and then.
No, straight from the phone.
Last weekend I had a friend in the car using apple maps on a newish iPhone, and every prompt from his phone was around a second earlier than from my phone. At 35 mph, one second is 50 feet (15 meters). That's enough to turn a safe maneuver into an unsafe one.
I use Google Maps many years already but it just became so slow in the last year or so. Maybe they just don't support non-high end phones anymore.
Now, I actually don't have a mapping app on my phone. It takes a little planning ahead, but I'm happier to do without.
Also, no lag (especially wierd lags) and no interruptions from notifications, phone calls and similar.
Switch back to version 9.42.3, or possibly a couple releases later if you need the "Favorites" and "Want to go" features in addition to just "Starred". It's pretty snappy and a breath of fresh air.
The only fix was reverting to the stock version, and it was AMAZING. So smooth. I had completely forgotten how fast it was while they boiled this frog's water over the years with their updates.
The telsa maps are based on google maps.
I heard there were two ways to speed up maps:
1) turn off traffic, which significantly slowed things down
2) switch from vector maps to satellite maps. Apparently the map tiles of the vector maps require costly rendering for display, but the satellite maps just required a blit.
#2 may also explain #1, I'll bet traffic requires rendering too.
I agree on annoyance with "design changes" sometimes. Last weekend having the map always oriented to the North was driving me nut. They used to have a compass with a N to toggle it. While I was driving it took me 15 minutes to find the option under all the advanced options.
But that said I think Google is in general pretty good in trying to reduce the "featurite" in the app and simplify the UI.
200 Mbps
I do not have "Start AR" at the moment so I cannot test that.
-The app always loads with an "Explore {your_location}" card that takes half the screen. I am usually at my suburban house, near which there is nothing worth exploring. Even when I'm somewhere else, my primary use of the app is to get directions to an _already determined_ destination. The card is useless 95% of the time, but obscures half of the map, which is what I want to see and is so important as to be the name of the application.
-If I so much as brush the screen with more than one finger, it enters its 3D map mode. Like the "Explore" card, this seems to be screaming "look what we can do!", but it ignores what I want to do, which is navigate using the bird's-eye paradigm that has been used by every other map since the dawn of cartography.
-If I search for a place and tap a result, I get a full-screen card with information about that place, but no map. I just searched for "pizza" and tapped the first result and got a large picture of a pizza. I already knew what a pizza looks like, but I still don't know where the restaurant is. If I swipe the card down and then tap the map to try to get a better view of the restaurant's location, I lose the location indicator on the restaurant and the map re-centers on my current location.
I could go on, but I feel like an old man shouting into the void.
Google Mail is quite fast for me as well... And I'm not even using some crazy fast computer, just old PC with Core i5.
On a dual core cpu from 2014 with an ssd running linux I opened first firefox 70 and then chrome 75.
In both cases I was logged into my google account. In both cases I opened and then closed gmail to ensure what could be cached was cached.
In each I then entered mail.google.com and measured the time between hitting enter and seeing what looked like a usable interface. Lets compare that to other local ways of accessing email.
Running mu find maildir:/Gmail/INBOX took 9 ms this is easy to measure as it happens in the terminal.
Creating an emacsclient frame takes about 150ms added to the mu query which takes about 9. Logically there is some time required to render the view but its quite small and challenging to measure so lets say aprox 200ms or 1/5th of a second.
Loading the old school plain interface html interface to gmail took aprox 1.5 seconds.
It took 10 seconds in either browser to load the "modern" javascript gmail view.
For reference this is about 7 times slower than the html view or 50 times slower than mu4e.
Reading
https://www.pubnub.com/blog/how-fast-is-realtime-human-perce...
> A response time of 100ms is perceived as instantaneous. Response times of 1 second or less are fast enough for users to feel they are interacting freely with the information. Response times greater than 10 seconds completely lose the user’s attention.
This is why the slow loading Gmail interface has a loading screen so it is perceptibly doing something rather than appearing to be frozen. After this the interface is fast enough in the context of web apps wherein the user expects a small delay between actions but not as quick as a desktop app which can trivially be perceptibly instant.
Interestingly the old interface despite using vastly less ram and loading much much quicker initially appears to say load a message slightly slower than the slower loading interface so the optimum web interface would appear to be the slower loading more sophisticated interface if you don't mind keeping that browser tab pinned and always running.
A desktop app is still on the overall the superior option.
Is your gmail experience objectively different?
I don't know how could you expect ms-time response. I have 70ms ping to mail.google.com. It's just not possible for a web app to 9ms time response, unless you're living at data center. But as a web app, Gmail is amazing and pretty fast. I don't know why it's slow for other people, I'm not Google engineer and I don't have performance insights. I just telling that it's far from slow for me. Definitely not 10 seconds.
It's slow for others because a huge range of machines exist and tons have slower cpu, storage, or especially network.
Worldwide the majority is probably using worse machines especially in poorer countries than ours.
If you want to see fast mail, go load the basic html version of Gmail. I have it bookmarked because it loads as fast as you think it should.
Regular google mail loads so painfully slow in comparison, they needed a splash screen.
with possibly 8 gigs of RAM?
Thats still WAY faster than most machines being used in the wild.
Sorry, your SV bubble is showing.