Google tests ART foundation in KitKat for faster Android apps

The software, designed to load apps faster than the current Dalvik virtual machine, is built into Android 4.4 and could arrive in the next version of Google's mobile OS.

Dave Burke, engineering director for Android, speaking at Google I/O 2013.
Dave Burke, engineering director for Android, speaking at Google I/O 2013. Stephen Shankland/CNET

Android 4.4, aka KitKat, comes with an experimental technology called ART designed to speed up Android apps.

ART is a replacement for Dalvik, the "runtime" software that has the job of executing Android apps. Dalvik is a virtual machine -- essentially a software version of a computer that lets Android apps run on a variety of hardware -- that's closely related to Oracle's Java technology.

ART is geared to speed things up by reworking a core part of the process. Developers write apps in high-level languages such as Java, and when they build them, the programming tools don't actually create software that runs natively on device hardware. Instead, the tools produce an intermediate version in what's called bytecode. When you run an app, a Dalvik process called just-in-time (JIT) compilation turns that into the native code a device actually executes.

With the ART approach, that software is compiled during installation so it can load faster, according to an Android Police report. That makes Android apps more like native apps, such as those that run on Windows or iOS, but that doesn't require developers to change what they do.

KitKat includes an option to enable ART. But Google's ART introductory page warns that "Dalvik must remain the default runtime or you risk breaking your Android implementations and third-party applications."

ART could arrive in the next version of Android, engineering director Dave Burke told ReadWrite.

"I don't want to make promises but I imagine next release it could be ready. Maybe. We will switch over when it is ready. It is actually quite fast now, and now we are just really optimizing it, and assuming those optimizations go well I assume that we will be ready to switch over at the next opportunity," Burke said. "We could have made tweaks to Dalvik and we decided that actually it was better to start clean. Because Dalvik is pretty old now. It started when Android started and we hadn't worked on it actively."

(Via Android Police)

About the author

Stephen Shankland has been a reporter at CNET since 1998 and covers browsers, Web development, digital photography and new technology. In the past he has been CNET's beat reporter for Google, Yahoo, Linux, open-source software, servers and supercomputers. He has a soft spot in his heart for standards groups and I/O interfaces.

 

Join the discussion

Conversation powered by Livefyre

Don't Miss
Hot Products
Trending on CNET

CNET's Christmas Gift Guide

'Tis the season for a gadget upgrade

Check out these 8 tablets you'll want to bring home for the holidays.