[kasperl]

Flutter (http://flutter.io) strikes an interesting balance here by (1) allowing just-in-time compiled, state-preserving "hot-reloading" during interactive development and (2) supporting optimized deployment using classical ahead-of-time compilation to native code.

Disclaimer: I work on the team at Google that builds the underlying language platform for Flutter.

[Jhsto]

Thank you for your work on Flutter! I tinker with it during weekends like this and despite it being my first go at mobile development, I feel productive programming in it.

[mmirate]

Hmm, looks interesting, but it's quite unfortunate that making the compilation process be useful at runtime-error-removal is merely optional ("strong mode"). So one wonders how many shops write enough "prototype" code in "weak mode" that they decide to leave it in its Python-like mess instead of rewriting for "strong mode"...

[kasperl]

Don't worry; strong mode will be the only mode going forward and it already is the only mode for Flutter. Not merely optional.

[matt2000]

I have been trying out Flutter over the past week or so and so far it really has delivered on high speed build-edit loops. I've already gotten in the habit of improving layouts while the app is running, it's really a great experience.

Android build times have improved a lot over the past few years but this is a whole next level experience.