# 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:** [September 29, 2015, 11:25pm 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:** 5

<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: [September 29, 2015, 11:44pm UTC](https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889/5 "2015-09-29T23:44:06Z")

</div>

Hard to say, some of it would possibly be under “let’s present a better minimal rendered experience for ancient devices”. Dedicated native Android app is far beyond our current staff and budget and resource levels. Plus, two code bases, two sets of bugs, two sets of support, etc.

One mitigation I should have mentioned – **we already send down half the content to Android devices** and have for a year now, so we effectively cut that 5× Android JavaScript performance penalty in half. Which means it is still 2.5× slower ☹ but more tolerable.

---

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