# 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:** 12

<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:56pm UTC](https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889/12 "2015-09-29T23:56:00Z")

</div>

The other strategy is to double down on the coattails of Apple, since the company is clearly firing on all cylinders. But as @sam has pointed out, **Apple does not play the low cost game** , and probably never will.

This would mean Discourse is positioning itself as more of a “premium” solution (read: devices that run JavaScript at near desktop speeds) than an “everyperson” solution (read: zillions of cheap Android devices with 2012 era specs), given the worldwide share of iOS and Apple.

Not super happy with that, but it might be the only viable way forward.

---

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