StockTouch Blog

Big Data Visualization: Optimizing for Mobile

July 25, 2013 by Jennifer


Some good recent discussion pieces on using native code platforms for nontrivial mobile apps over javascript/HTML5 for the next 5-10 years.  Javascript-based apps are slow, so apps that require any sort of animation, high performance, and memory management – e.g. photo editing will need to be in native.

Thus, advances in big data mobile data visualization user experiences will not come from javascript platforms for at least the next 5 years.  Combining animation, data navigation, large data sets, real-time updates requires faster processing and memory management capabilities.

TechCrunch: Your App is Slow Because Our World is Ending –  Jon Evans

“I’m now pretty convinced that HTML5 is not a short- or even medium-term solution for any kind of genuinely nontrivial iOS app, and I’m pretty dubious about other platforms too.”

He sums up Drew Crawford’s piece below –  “HTML5 apps will be vastly inferior to native apps not just for the next year or two, but for the next 5-10 years, because of fundamental technical limitations inherent to mobile platforms.”

SealedAbstract: Why Mobile Web Apps are Slow – Drew Crawford

“Javascript is too slow for mobile app use in 2013 (e.g., for photo editing etc.).  It’s slower than native code by about 5.  It’s slower than x86 C/C++ by about 50. It’s slower than server-side Java/Ruby/Python/C# by a factor of about 10 if your program fits in 35MB, and it degrades exponentially from there.

The philosophy of JavaScript (to the extent that it has any philosophy) is that you should not be able to observe what is going on in system memory, full stop. This is so unbelievably out of touch with how real people write mobile applications, I can’t even find the words to express it to you.”  

Leave a Reply