The problem with this theory of course is that Google basically doesn't do finished products, things sit in beta for half a decade and maybe they'll bother to take that label off the product or kill it or suddenly charge 4000% or whatever.
Google needs a clearer product pipeline, right now there's "we're not showing this to the public", "arbitrarily special people who are mostly press can see it" and "it's out in the wild". That's too flat for the public and doesn't really engage the developer part of the pipeline.
I/O is a public event, it's broadcast worldwide, live. It's the most consumer-level/press-level developer event I've ever seen outside of WWDC.
These are all ATAP projects revealed during a DEVELOPERS conference, so that there can be a collaboration in getting the software in place before general market release.
The overhype is why Google stopped doing device announcements at IO, because all the oversized tech blogs would grab the tickets just to be there to oh and ah at the new device, but not come up with new code and uses for the tech showed. Rather they would often pan what was clearly meant to be early prototypes as if they were the finished product.
Google, and to some degree Microsoft, is doing things the old PARC way. Create stuff, show it off, and if they can't find a use for it maybe someone else will.
Apple on the other hand sit on things until they have a use for it, and if they never find a use for it nobody else gets to see it and find a use for it.
In the end the PARC way of doing gave the world things like Ethernet and the GUI. Personally i prefer this way to the Apple "take my ball and go" approach.
But the press sadly love the coy ones, as they are so much easier to write clickbait about.