# The State of JavaScript on Android in 2015 is... poor

**URL:** https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889
**Category:** General
**Created:** [9월 29, 2015, 11:25오후 UTC](https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889 "2015-09-29T23:25:14Z")
**Posts on this page:** 1
**Showing post:** 240

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [7월 12, 2016, 8:20오후 UTC](https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889/240 "2016-07-12T20:20:36Z")

</div>

Android JS perf is somewhat less relevant since we switched to a raw vdom renderer in 1.5 final for the topic page and the header, which provides 6x-8x the performance on slower Android devices over Ember.

The OnePlus 3 is a great device! Still, it will be nice to see if Android can close the considerable JS performance gap in 2017, with whatever new CPUs are coming out, perhaps Snapdragon 830?

---

_[View the full topic](https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889)._