cc @floitschG

also see
https://groups.google.com/forum/#!msg/flutter-dev/YwzItp1pxJo/7bFGDLvxBAAJ
I would be extremely excited about this.

I would think this would be fairly important because this is might be one of the only truly distinctive features of react native, and unfortunately some companies might consider this a dealbreaker.

Use cases

• critical bugs, especially on iOS, especially for VIPs or urgent, time sensitive situations, business critical, and/or users that can't use the app at all for some reason.
• More dynamic testing of features than staged rollouts
• this would be a nice touch preparing for Fuschia, and/or Chromebooks. there could be scenarios where flutter is "competing" with web apps not just pwas/Kotlin/Swift/React/Xamarin/other-junkier-hybrid solutions

In the epic battle that is Flutter vs React Native, code push is one hell of a tool (:
As an RN dev I can't stress enough the importance of this feature. Many will pass Flutter just because the absence of hot pushes. Once you get accustomed to quickly fix bug and push new features you can't go back.

compiling to javascript path will diminish the dart advantages right?
i found some native app used to be able to have code reload using Rollout.io but it was blocked by Apple: https://news.ycombinator.com/item?id=13817557
looking at this pattern, seems like flutter will not have a seamless code push feature like what we see on react native.
would love to get more insight to this feature possibilities from core maintainers (:

compiling to javascript path will diminish the dart advantages right?

What advantages are you talking about?

Codepush is very much needed. Love to see the over-the-air upgrade release possibility on Flutter.

we just had a live use case with a production app where we were getting lots of bad reviews for a feature that appeared to be slightly edge case (related to denying location permission in a use case that not every test account had ) but really wasn't.

a codepush feature could push critical fixes for users immediately rather than waiting for them to upgrade; for some reason it seems users are slow to upgrade sometimes :(

No hot code push support is a NO GO :-(

Looks like JavascriptCore may no longer be required for interpreted code: https://www.theregister.co.uk/2017/06/07/apple_relaxes_developer_rules/?page=2

If the IOS ecosystem is a hindrance, why not implement on Android only for now? Something better than nothing and its a starting point.

Much appreciated for team to implement this feature ASAP.

We've built some basic prototypes here, but don't have anything really to share at this time. To do this really well will require some work in Dart's compiler toolchain. I would expect it to be many months before we will have much to share here. The team is currently focused on stabilization for 1.0.

All that said, we hear you. :) This is clearly a feature many people value and we're interested in providing functionality like this eventually.

"Code Push" support for Flutter could be the final nail in the coffin regarding React Native.

With all my love for RN and the RN community, being the game changer it is, it is no match for Flutter.
Flutter just nails it in any aspect (tooling, performance, language...).

After 1.0 hits and the community grows a little bit more + Code Push support = Can't see any reason to start a new mobile project with anything other the Flutter.

any progress on "Code Push" ??

How feasible would be to have a full .so replaced dynamically? The whole compiler toolchain, code shake etc shouldn't be steered to an arguably edge case that people may or may not benefit, given there will always be tickets at the top of the priority list.

I think there should be room for "sideloading" the full .so file, so the build from dart to machine code can still be exactly the same. A small but completely independent component could be assigned the following "minimum viable features": download .so and replace the originally shipped one with it, and restart app with the main launch intent.

Extra responsibilities: download assets, verify signatures and what not. Update flutter/dart/skia engines and what not.

It sounds to me like it violates iOS guidelines, but I'm really not a fan of anything interpreted anyway, or iOS in general. And I'd rather have it in Android than not having it at all, just because it's cool.

At least the download part seems doable now that we have some isolate work being allowed in the background, but it would be interesting to see how to swap the original .so with the downloaded one. Maybe an extra .so or java code could do that part, but it's going to be sitting at the code folder, not sure the app itself can modify it so probably it would need some tweaks so the flutter engine loads all app's .so from internal data?

Starting to revamp my companies app using flutter. However our key demand to have a hot update feature since we are still in beta and keep testing out new UIs and features rapidly. Would live to have this feature.

Any updates?
(I'll bet the feature is already done and will come as a suprise when 1.0 hits)
😁

up vote

There is only one reason to prevent us from using Flutter: Code push

If you guys can not support Code Push, is there a way to make a Parser to generate from some dictionaries (like json, xml...) to Flutter Widget? Is this impossible or a good idea?

I think at least the UI/View written in Dart can be downloaded via the network from the server.
For inspiration see how Qt Quick framework is doing it.

QtDD12 - Serving QML applications over the network - Jeremy Laine:

• Video
• Slides

expect it can be included in the coming 1.0 release!

Many of our customers will be using our Flutter app on a kiosk device behind strict firewalls that would prevent Google Store's app-update mechanisms. These customers will not whitelist the Play Store. We will ultimately have 100's of hardware devices with the Flutter app, and having a way to push updates to app while adhering to customer firewall restrictions would be amazing!

The other significant problem to solve is around sandboxing and security - whatever approach is used would have to make sense from that perspective, regardless of whether the stores would be ok with it.

That looks interesting (For the bytedance one, at least I cannot find any here: https://github.com/bytedance?q=dart&type=source&language=&sort=. Nor "Bytedance dart" give any result in google.)

Sorry guys, it's only available for internal. And they are going to use JS instead in the future

anybody know about this? https://codepush.dev/

anybody know about this? https://codepush.dev/

They maybe discontinue it, there is no update.

CodePush is (was?) a Microsoft product, part of Visual Studio App Center (https://appcenter.ms/); I used to be a PM on that team. Microsoft moved the team to GitHub a couple of years ago and App Center wasn't getting a lot of attention there the last time I checked. Here's the landing page: https://microsoft.github.io/code-push/

Doesn't support Flutter, of course, because Flutter can't support OTA updates.

I've stumbled across this: shorebird.dev. They seem to be working on this, apparently, it's currently in closed access. I haven't used it so I don't know how well it works, but maybe it's interesting to keep an eye on them.

Their Github: Link

Congratulations to @eseidel @felangel, for releasing shorebird for android, and iOS+others, on the roadmap,

I got to know of this, from twitter

Can the official team add an identifier when packing to enable dynamic JIT or parser functions? For example, to develop macos applications, you need to develop some functions of dynamically running plug-ins, which can be developed by users. So it cannot be written inside the application in advance.

Congratulations to @eseidel @felangel, for releasing shorebird for android, and iOS+others, on the roadmap,

I got to know of this, from twitter

I think congratulations are too early. Implementation on iOS is very doubtful. Android only implementation calls doesn't seem necessary

Is it possible to provide a set of tools to package Flutter widgets into .so files: bundle1.so, bundle2.so, where each .so corresponds to one or multiple page-level widgets, and then load the .so files at runtime to dynamically load the widgets?

This is one of the most critical factors that I consider turning to RN halfway. I can't believe that this issue has passed four years by a team that claims it pursues user experience.

This is one of the most critical factors that I consider turning to RN halfway. I can't believe that this issue has passed four years by a team that claims it pursues user experience.

Have you checked out shorebird.dev ?

It's led by @eseidelGoogle himself and it seems to be ready for production on Android and iOS. I believe they already have existing customers who've published apps with the code-push support.

Could be worth looking into.

i need it

@rutvik110 Have you used this? If yes, how's the experience so far?

CodePush is the more important factor than others When Company chooses development framework. In China development efficiency is the first question