Rust Developer

Why it matters: There is a common misconception that a HTML5 browser-based application can just be deployed on any browser-capable device and it will just work. In practice, browser capabilities on set-top boxes are very mixed and each new device becomes essentially a new application development cycle because of differences in browser implementation. The WASM functionality of the ADK provides the same flexibility in loading new application logic and content that HTML5 and JavaScript provide, but is even more flexible. With any approach, streaming services such as Disney+ need the ability to add in new application logic without waiting for a video distribution provider to push out firmware updates to set-top boxes. Also, because WASM is a portable binary format, meaning it can provide the same level of functionality as a compiled programming language, it is possible to push more than simple presentation to the WASM code, while keeping the compiled core focused on the task of interpreting and running the WASM code without needing to understand any specific Disney Streaming application logic. It can run multiple applications — there is nothing in the way of developing a Hulu or ESPN+ application for the ADK. It has a smaller footprint than a browser engine, since a browser by its very nature is a general-purpose interpreter for HTML and JavaScript whereas the ADK has a more focused task. And it gives Disney Streaming full control over the entire stack above the operating system, whereas in a browser-based solution there is no way for Disney Streaming engineering to fix a problem in the browser implementation. Disney+ ADK Components