None that I've ever read (but I also don't work for Google, so external docs only). ART improves app load times, runtime performance, and reduces battery usage

None that I've ever read (but I also don't work for Google, so external docs only). ART improves app load times, runtime performance, and reduces battery usage. That effect is somewhat amplified by AOT-ing services/APIs that apps rely on, so instead of just seeing the improvements within a single APK, you might see a single app-load improved by three or more APKs being AOT-ed. Not that dissimilar from Ngen in the .Net/CLI world. Intel won't benefit more (or less) than other architectures. They're both doing the same work, just doing it at a different point in time. So unless Intel or someone has developed a really awesome static analysis tool which just happens to be too slow to shove into the JIT pipeline, it shouldn't make a huge amount of difference (and I've read nothing about an Intel specific dex2oat). As to legal: Most of Google's issues with Oracle have been resolved. They related to a bunch of Oracle's patents and something about the Java library. ART doesn't really change how anything works, you're still interpreting bytecode into local instructions, you're still using the same libraries, and even the whole workflow hasn't really changed. Just moved around WHEN stuff happens not WHAT happens. So while IANAL, I don't know if how ART would be a legal maneuver. If anything it exposes them to additional patent liability as the process is more complicated and third parties could claim they "own" part of it.