Skip to content

<= 3s edit/refresh cycle on iOS device #790

Closed

Description

@sethladd

If a developer makes a change in their editor, it should take 3 seconds or less to see the effect of that change on their iOS device.

(assuming they already have their device connected, and configured.)

Activity

  1. added this to the Hackathon milestone on Dec 7, 2015
  2. sethladd commented on Dec 7, 2015

    @sethladd
    ContributorAuthor
  3. changed the title [-]<= 5s edit/refresh cycle on iOS device[/-] [+]<= 3s edit/refresh cycle on iOS device[/+] on Dec 10, 2015
  4. added
    c: performanceRelates to speed or footprint issues (see "perf:" labels)
    on Dec 11, 2015
  5. modified the milestones: , Hackathon on Jan 26, 2016
  6. eseidelGoogle commented on Jan 26, 2016

    @eseidelGoogle
    Contributor

    iOS devices are not in scope for the hackathon.

  7. eseidelGoogle commented on May 13, 2016

    @eseidelGoogle
    Contributor

    This should be possible once @chinmaygarde turns on the DBC by default for --debug builds.

  8. sethladd commented on Jul 7, 2016

    @sethladd
    ContributorAuthor

    Just tried this. I made a change to line 36 of gallery's app.dart and then pressed the Run button in Atom. It took 25 seconds to see the gallery app display the homescreen on my device.

    cc @devoncarew

  9. eseidelGoogle commented on Jul 7, 2016

    @eseidelGoogle
    Contributor

    To confirm @sethladd: that's using the Debug build on device? 36s sounds about right for Release, but Debug should be much much faster.

  10. sethladd commented on Jul 7, 2016

    @sethladd
    ContributorAuthor

    Here's what I see in Atom:

    screen shot 2016-07-07 at 8 57 18 am
    screen shot 2016-07-07 at 8 57 12 am

    I think I'm running debug. At least, that's my intention.

  11. sethladd commented on Jul 7, 2016

    @sethladd
    ContributorAuthor

    Ah, so I don't see the Slow Mode banner when I launch the app from Atom, even with the "debug" option selected.

    cc @devoncarew

  12. devoncarew commented on Jul 7, 2016

    @devoncarew
    Contributor

    Do you see it when run from the command line?

  13. devoncarew commented on Jul 7, 2016

    @devoncarew
    Contributor

    (just flutter run; --debug is the default)

  14. sethladd commented on Jul 7, 2016

    @sethladd
    ContributorAuthor

    Do you see it when run from the command line?

    Yup! From the CLI, I can see the banner.

  15. sethladd commented on Sep 14, 2016

    @sethladd
    ContributorAuthor

    With hot reload, I'm going to call this done.

    cc @johnmccutchan

  16. github-actions commented on Aug 16, 2021

    @github-actions

    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 -v and a minimal reproduction of the issue.

  17. locked as resolved and limited conversation to collaborators on Aug 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    c: performanceRelates to speed or footprint issues (see "perf:" labels)platform-iosiOS applications specifically

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions