Repository navigation
How to use Flutter in a large team w/o all developers knowing? #25979
Description
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.
Activity
neiljaywarner commentedon Jan 2, 2019
Thanks so much for filing this Eric. I've worked with this quite a bit lately and am down so far to two concerns . re: submodules
2b. Maybe it can all come down to "flutter create -t --full" and it does it all for us eventually :) . Similar to how gradle version if typically tied to a specific Android project.
thanks again!
zoechi commentedon Jan 2, 2019
Related #24948
xster commentedon Jan 3, 2019
Also one of the issues that various Chinese developers ran into and independently solved (by jerry rigging Flutter tools to output .framework/aars and then hosting in their internal pods/maven repository). Would be nice to have official support.
kangwang1988 commentedon Jan 3, 2019
I think there are several points for this case:
P1. In a multiple team co-working environment, when only one team use flutter, it's quite simple. The flutter team can develop flutter in a flutter development environment, export their codes as a bundle(aar for android or pod for ios) to other people who don't know flutter. For the non-flutter team, all they need is to import the bundle as before, they don't know/need flutter environment.
P2. However, when multiple team are using flutter(not all), those flutter developers need a unified flutter environment. They can't do as said in P1 directly. Instead, they needs to develop flutter and export multiple pubs. Then a flutter wrapper project will import those pubs and export a bundle(arr or pod) as said in P1. The rest is the same as P1.
neiljaywarner commentedon Jan 5, 2019
@xster I wonder if there jerry rigging solution is a) Suitable for production and b) a tecnique they would share unofficially.
i.e. can a technique like theirs serve as a backup solution that is still reliable until their is an official solution..
xster commentedon Jan 5, 2019
@kangwang1988: I suspect you guys probably had a blog post somewhere for @neiljaywarner :)
neiljaywarner commentedon Mar 1, 2019
@eseidelGoogle great job on getting 1.2 out the door at MWC. Any ideas on this for March?
eseidelGoogle commentedon Mar 1, 2019
@dnfield has done some thinking here (as has possibly @csells), but nothing concrete at this time.
pszklarska commentedon Jul 16, 2019
Hello, are there any updates regarding this issue? I've seen some work done for the Android (e.g. #35217), but nothing for the iOS. I think that's the use case that many companies (including mine) may benefit from. I'd love to see higher priority set on this.
neiljaywarner commentedon Jul 16, 2019
The dependency on cocoapods can also be A challenge...
xster commentedon Jul 16, 2019
This is currently being looked at on iOS as well. Follow progress on #26099
xster commentedon Nov 15, 2019
Solved by #26099 and #36968. Currently documented in https://github.com/flutter/flutter/wiki/Add-Flutter-to-existing-apps and soon moved to flutter.dev website.
github-actions commentedon Aug 14, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.