Would like instructions on how to use Flutter in a large team w/o all developers needing to install Flutter or know that Flutter is being used.

For example, can the Flutter SDK be a git submodule and the tooling used be relative to the checkout (instead of all developers installing Flutter separately)?

Or can Flutter be used to produce an intermediate build product (a .framework, .aar, etc.) that then can be checked-in/cached, but other parts of the app could depend on?

We've received this question (or ones like it) from several large firms using/exploring-use-of Flutter.

FYI @matthew-carroll who might have other bugs to link this to/dup it to.