Understanding Android Runtime (ART) for faster apps (Google I/O'19)

Learn more about how Android Runtime, for Java or Kotlin programming languages, makes it easier to write a great Android app with improvements in debugging and profiling, install and launch times, and garbage collection.
Watch more #io19 here:
Android & Play at Google I/O 2019 Playlist → goo.gle/2GRWlQh
Google I/O 2019 All Sessions Playlist → goo.gle/io19al...
Learn more on the I/O Website → google.com/io
Subscribe to the Android Developers Channel → goo.gle/Androi...
Get started at → developer.andr...
Speaker(s): Lokesh Gidra, Mathieu Chartier, Roland Levillain, Chris Wailes
T5B2A3 event: Google I/O 2019; re_ty: Publish; product: Android - General; fullname: Lokesh Gidra, Mathieu Chartier, Roland Levillain, Chris Wailes;

[@sazidali4959]

Thanks for providing such a deep knowledge

[@DanieleSegato]

Measure how?
Large object = ?
Is a SimpleDateFormat a large object?
Conceptually, those are good recommendation, but practically they are fairly useless :-)

[@dmitrii_leonov]

13:15 - GC

[@thanglevan1626]

the video image is too poor, you need to fix it more

[@LittleFourthLee]

13’15’‘ Garbage Collection

[@RafaelUmbra]

Lokesh saved the day.

[@zungaloca]

should not have used java since the beginning

[@ulicqueldromal]

Maybe a more memory leak prone language like C would suit you more? Or a completely runtime interpreted language like Javascript?

[@wyattparo9744]

Eh, I'd say that this is less the case now more then ever given that the performance gap for the majority of Android application functions are closer then you'd think and in some cases faster. With that said, I would of preferred C++ and something like QT for UI.

[@gunasekaranrassiappan3268]

But Java was more adopted , that's why Google used Java based Runtime on top of C kernel

[@zungaloca]

Missing android 13

[@zungaloca]

Missing android 11