I have a theory that by optimizing for the UI/UX of a First time user, things have gotten worse for the power user. In the past when most of our apps were desktop apps, there was a hidden assumption that the user would be using the apps for years and therefore had the time to build up muscle memory, currently when bulk of the apps on App Store are not downloaded and those that are, are barely opened twice, it makes sense to optimize to make the whole thing easy for the FT User. That by definition makes it harder for the power user. Notice that the really responsive websites are ones that cater to a group of people who by definition are more likely to be power users: HN, Github etc

There is a big dose of fashion and fad-following in usability. The things you mention are manifestations of poor decisions made in the name of usability, but actually in the interest of being pretty.

I think even making the right decisions in terms of usability, tethered to a few short-sighted user stories, will result in this situation. Usability should be in service of a higher purpose, which should be enabling the user to understand how to use something powerful and flexible that does not constrain them only to what is envisioned by the developer or the UI architect. That's what has happened here with Maps. You can perform User Story #1 or #2 with zero friction. But there is no way to do what @gravislizard wants to do, which wasn't anticipated by Google or specifically designed for.

Not only is there a lot of fashion and fad-following, but there is a distinct lack of measurement and metrics. You want this animation or to change the color on this control? Fine--show me the empirical data that demonstrates that it improves usability or any of our KPIs. None of this, "I'm an artist and I subjectively feel this will be good for users." That's total BS. Show me the measurement that justifies your design request, or let's A/B test it.