There are multiple internal approaches to building things. Several of these approaches get funding and head count based on the amount of influence of the people who back them.
Decisions about which product to present to the public are made on technical merit with little consideration to consistency in user experience. The resulting chaos leaks to the end user.
Once a product has launched successfully, the best members (not just engineers) of the team that built it diffuses back into the main body of Google to work on other cool projects (they now have the required political momentum). Product enters stagnation phase.
In 2 - 4 years a technologically slightly better alternative is picked. No one thinks about how to make this switch seamless for their users. End users suffer even harder.
Used to work at Google.
For example, the decision to start charging users for storage beyond 15GB. Even though I am not happy about it, I am paying and it looks unlikely that I will leave the Google ecosystem anytime soon.
The interesting thing about Google, though, is that they have so many products that they can actually run experiments over different approaches to product development.
Unfortunately, I doubt many people at Google would want to experiment with a product development approach by putting their career progression at risk.
Beware depending on any Google tool for your business.
[0] https://www.reddit.com/r/FlutterDev/comments/d51o4w/were_the...
[1] https://github.com/flutter/flutter/issues/80860
[2] https://github.com/flutter/flutter/issues/31453
[3] https://github.com/flutter/flutter/issues/70751
[4] https://medium.com/flutter/flutter-package-ecosystem-update-...
[5] https://www.reddit.com/r/FlutterDev/comments/ju2zza/flutters...