Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code Push Support for Flutter #624

Closed
rodydavis opened this issue Mar 14, 2019 · 9 comments
Closed

Code Push Support for Flutter #624

rodydavis opened this issue Mar 14, 2019 · 9 comments

Comments

@rodydavis
Copy link

Would it be possible to support Flutter?

https://flutter.dev/

https://github.com/flutter

@gagangoku
Copy link

This will be a good feature to have. This was one of the main reasons I went for React Native instead of Flutter.
Btw, Flutter 2019 roadmap does have Android Dynamic updates (https://github.com/flutter/flutter/wiki/Roadmap). I'm not sure how they'll support it though. My guess its something they have to fix in Flutter first, since the dart code is compiled into binary when packaged.

@alexandergoncharov-zz
Copy link
Contributor

Hi @AppleEducate,
Thanks for reporting!

That's is good point! But unfortunately we don't have supporting for Flutter item on our roadmap.
I'll investigate if it is possible to support Flutter and discuss with my team a bit later. I'll be keep you posted.

@rodydavis
Copy link
Author

@alexandergoncharov thank you!

@eseidelGoogle
Copy link

Discussion of Google's explorations in flutter/flutter#14330 (comment). I would be happy to speak with others from code-push further about this if desired. eseidel@google reaches me.

@HerrNiklasRaab
Copy link

HerrNiklasRaab commented Sep 18, 2019

There are some serious security concerns. Since these patches would essentially allow arbitrary code execution, they would be extremely attractive malware vectors. We could mitigate this by requiring that patches be signed using the same key as the original package, but this is error prone and any mistake would have serious consequences. This is, fundamentally, the same problem that has plagued platforms that allow execution of code from third-party sources. This problem could be mitigated by integrating with a platform update mechanism, but this defeats the purpose of an out-of-band patching mechanism.

React Native, Cordova and Ionic are supporting this feature, through the browser as a sandbox. This means it must also be possible through a sandbox for flutter.

There is currently no out-of-the-box open source hosting solution for patching applications, so we would either have to rely on people configuring their Web servers accordingly, or we would have to create integrations for proprietary third-party services, or we would have to create our own bespoke solution. Hosting patches is a space we are not eager to enter. Having people configure their own server leaves them open to making mistakes with potentially serious implications as explained in the previous point about security. Depending on third-party services puts Flutter in an awkward position of having to pick winners and exposes us to the risk of those projects themselves making policy changes that would affect this feature.

You started building autonomous driving software, without producing own cars. Not really an argument. That's not Google-like.

More arguments:

  • Your mantra is "...helping developers write better mobile applications, faster.". This would be a big step forward fulfilling this promise.
  • React Native, Cordova and Ionic have it and Google want's to be the market leader :).
  • It is the third most demanded feature of all issues (including closed once) with 395 upvotes.
  • It is the missing piece, to make flutter the perfect mobile framework.
  • Beeing Google means, making things possible even if they seem impossible.
  • It is really really needed.

Sorry, if you feel offended @eseidelGoogle , but this comes from my heart. I love Flutter!

@eseidelGoogle
Copy link

No offense taken :) (I will also be brief as I wish to be respectful of polluting someone else's bug tracker.)

At the end of the day we all have finite resources. :/ Code push/hot-updates is very exciting, but also high cost and not (yet) not high enough priority relative to the other things Flutter has been asked to do, hence it got bumped off our 2019 roadmap. 🤷‍♂ We get a ton of requests for code push/hot-updates/ephemeral-code-delivery/etc. and although Flutter for web can be used to answer some of those concerns there is a lot more I would like to see us do there over time.

@marceloiavenissi
Copy link

marceloiavenissi commented Feb 6, 2020

https://pub.dev/packages/dartins

cordova( FlutterForWebProject() )

@chgibb
Copy link

chgibb commented Jul 16, 2021

Hydro-SDK now supports codepush for Flutter apps https://hydro-sdk.io/blog/fluttering-over-the-air

@ghost
Copy link

ghost commented Jan 18, 2022

This issue will now be closed because it hasn't had any activity for 15 days after stale. Please feel free to open a new issue if you still have a question/issue or suggestion.

@ghost ghost closed this as completed Jan 18, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants