and built Android Nougat. Ask us Anything! https://www.reddit.com/r/androiddev/comments/4tm8i6/were_on_the_andr oid_engineering_team_and_built/?sort=qa
officially support a new language in Android, so we’d encourage folks to continue to use Java:) That said, you should continue to use what works for you. Anwar Ghuloum Engineering Director for Android Core Platform
more concise. JetBrains has done a nice job supporting this on android. But no plans to officially support anything new. Anwar Ghuloum Engineering Director for Android Core Platform
to break what already works there, but we don’t have plans to have a second, idiomatic-Kotlin version of the whole framework API surface area either. That would be a big duplication of effort when Kotlin already interacts with the existing framework setup well. Adam Powell TLM on UI toolkit/framework
at runtime • Low memory footprint • Poor performance • Unsophisticated GC • Long two pauses and janky app experience • Ahead-of-time compilation at install-time • Plenty of optimizations • Much better performance • Better GC algorithms • Just one short pause Dalvik ART
• Back to JIT ◦ No need to compile whole app at install-time ◦ No need to recompile when system changes • Hybrid JIT/AOT ◦ Apps start with JIT ◦ Will be profile-guided compiled later on when phone is idle