Roku Says No To Wheeler When Asked About Having HTML5 As A De Facto Standard
Roku is not in a mood to have HTML5 as the De Facto standard because if Roku accepts it, then the platform would become bulky. Moreover, having HTML5 will cost Roku a lot of money, since it is very expensive.
The debate as to whether HTML5 should be a De Facto standard in the Roku streaming player or not has been steaming up. The makers of Roku players called it heavy for its platform, and not to forget, it is quite expensive as well. Roku players if equipped with HTML5 would become slow, therefore, it needs to stay out from the platform.
There is another thing as well, which is bothering Roku, i.e., the plan of FCC to unlock the set-top boxes, and besides that, there has been problems as the cable companies are not interested in having plans based on boxes and apps.
There has been a number of meetings that took place between the makers of Roku and FCC in which the proposal made by the National Cable & Telecommunications Association has been discussed. The Roku is still in a belief that the commission that has been setup to boost the sales of the set-top boxes available on the market these days could turn out to be counterproductive. There is also a huge concern that the cable companies are going to create HTML5 as a standard for distributing videos.
The company is not very optimistic about the issue as they believe that this approach is not going to work because the customers have clearly shown their interests about the devices they want to use and what would provide them with different user experience. There is nothing bad about HTML5 provided it is used by the developers who create apps to provide access to the digital content.
Roku has not fully lashed out on HTML5, as the company doesn’t have major issues with HTML5. The only concern that company has regarding HTML5 is that it is heavy for their platform and a bit expensive. By expensive, the company means, the architecture of HTML5 is something that they can’t afford because they will have to take the help of 3rd party device manufacturers even when it is about the lowest priced devices to include more processing power and memory in order to support it. Roku says that whatever the decision of FCC is about marketing a highly competitive market for 3rd party video access devices, there are a few features that it is supposed to give, which are given below:
Multiple applications.
No 3rd party in-app development.
Metadata.
Direct delivery.
Disputes.
Non-discrimination.
But, it is not just HTML5 issue that Roku is facing, but there are several other issues, which are needed to be addressed. These are:
Roku error code 011.
Roku error code 014.
Roku error code 001.
Roku error code 003.
Roku is not able to connect to the Wi-Fi network.
The problem of Roku not connecting despite all the correct settings has become quite common. There are many things that could result in a non-functional Roku. For any issue, it is better for a person to take the help of the help and support providers working at Roku. It is not just the official company that provides support for Roku, but various third-party companies as well. Roku has to deal with a number of issues before it could reach at the top of the table. The competition in the streaming devices world is getting tougher and tougher, so if the technical support is not appropriate, then things may go otherwise.
