I read your strategy doc, and it doesn't change anything I said. Front and center is your commitment to developer experience, which is great, but what seems woefully absent is consideration for the end-user. I'm sure that you'll eventually get around to things like accessibility and bring them up to par with what we already have. It's worth saying that nothing should be built for production using Flutter until that's taken care of, but enough people have already said it.
What's absent is a commitment to empower end-users in the same way that the web does now. Your doc puts the developer front and center, but "developer" can be read two ways: the person writing code who wants good tools that make their job a delight, or The Business that wants tools to enable them to deliver products that the end user cannot open open the hood and tinker with. A consistent UI toolkit that lets you develop once and deliver to six platforms is great for the coder, and if in the process it just so happens that the frontend is reduced to indecipherable pixels that can't be modified, ads that can't be blocked, and tracking that can't be escaped, well, that's just perfect for The Business.
I don't doubt you or your team's sincere good intentions. I really don't. But after pulling stunts like AMP, Tag Manager, FLoC/Topics, etc. Google, the business, doesn't deserve a charitable interpretation. It's like Prisoners of Geography. Google is an advertising company, and always will be. Regardless of the ideology or stated goals of the day, everything they do is to sell ads. If Flutter allows Google to display more ads and collect more data, and Google is funding the development of Flutter, it stands to reason that Google is purposefully pushing Flutter because Flutter will allow them to sell more ads and subvert user privacy.