Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Now, in practice, within Google we further delegate the prioritization decisions to the individual leads of each subteam, for example Google has a team of a few people working on Flutter-on-iOS, and a few people working on Flutter-on-Android, and so on, and within each of those groups, the team members work together to decide what they will work on, with that team's lead having the final decision, driven primarily from guidance from myself (as TL) and u/timsneath and his small team of PMs. That guidance is mostly of the form "listen to what people are saying on GitHub issues and use that as your guide", with some general advice like "developer experience is a higher priority than virtual reality", but rarely specific enough to distinguish between e.g. implementing 120Hz support on iPad Pros or iPhone 13 vs implementing better fidelity date pickers on iOS. You can see the guidance in more detail on our wiki, e.g. see Roadmap, Issue Hygiene.
FWIW I wrote up https://github.com/flutter/engine/pull/28927 a while back to support high refresh rate for windows based on what Chrome does. I personally use a 144hz monitor for gaming so the difference is very noticable. I think it needs a bit of rebasing, but if someone were to review it then at least it would be done for Windows.