Repository navigation
<= 3s edit/refresh cycle on iOS simulator #873
Description
If a developer makes a change to Dart code in their editor, it should take 3 seconds or less to see the effect of that change on their iOS simulator.
(assuming they already have their device connected, and configured.)
Activity
appsforartists commentedon Dec 12, 2015
@chinmaygarde The current Atom experience is Cmd+R to send the new app.
I still think Hot Module Replacement is table stakes, but it would be good for Cmd+R to work in the mean time.
sethladd commentedon Feb 9, 2016
@chinmaygarde @devoncarew how are we looking here?
sethladd commentedon Feb 25, 2016
Just tried this, and edit/refresh was 11 seconds.
chinmaygarde commentedon Feb 26, 2016
I timed this again right now. On my setup,
flutter startfrom the command line is about 6.4s and 8.5s from Atom. https://gist.github.com/chinmaygarde/4a502796d0b5a3eefe6cBy far, the most expensive step is the FLX packager. I am going to add another target to the engine that tries to pick up the assets from disk directly (on the simulator) and avoid the FLX altogether. Since we don't run the precompiler on the simulator, we can get rid of that entire build phase.
sethladd commentedon Feb 26, 2016
Thanks for checking!
sethladd commentedon Feb 27, 2016
With Feb 27 8:35am master branch, I'm seeing 7s from command line (
flutter -d CBC62802-2CBE-4643-BD1A-AE017EBD04C8 -v run) to simulator, and 10-11s via Atom.Looks like it takes many seconds for this step:
github-actions commentedon Aug 16, 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.