October 25, 2013, 9:59 AM — I was chatting with the CTO of tradeMONSTER yesterday, because he and I will be conducting an executive interview at a Network World Enterprise Mobility Management Roadshow November 6 in Chicago.
If you are local to Chicago, please feel free to attend our conference to learn from both your peers and industry leaders.
Anyway, CTO Sanjib Sahoo was the force behind the introduction of the industry's first browser-based streaming trading platform in February. It was a highly successful endeavor that won high ratings from the likes of Barron's, while flying in the face of moves by Facebook and LinkedIn to reverse their own client app dev strategies from HTML5 to native platform development.
tradeMONSTER, Sahoo said, wanted to replicate the real-time accuracy capabilities and "anywhere" Web experience on traders' mobile devices, which might be running any flavor of mobile operating system. Because of the cross-platform nature of those devices and trading industry regulation requiring any data received by a trader to be current, Sahoo's strategic development platform choice was HTML5.
"We can’t wait for Apple App Store [or Google Play app store approvals] to update our app as we would have to do if we had taken the native route," Sahoo explains.
Sahoo will tell the full story, from planning to execution, on November 6, and I will post a followup here afterward. For now, though, he has summarized the pros and cons of using HTML5 for creating a high-performance streaming trading system in Wired magazine as follows:
• Great long-term strategy to become standard across all devices
• Catered to agile development and can adapt to hybrid strategy
• More adaptable to enterprise strategy keeping business goals separate
• Great fit with BYOD principles
• Lower development costs
• Ability to track usage and user behavior more easily
• HTML5 is NOT a true cross-platform technology
• No standard “out of the box” framework will work
• Device fragmentation creates many difficulties
• Rendering and caching are major bottlenecks
• Catering to large volumes of streaming data is quite tricky