Re: [media-and-entertainment] Interest in TV App Performance (#79)


First, I want to emphasize this topic will be focused on application performance (navigating on screen UI and different pages) and will NOT cover video playback. The goal of this meeting is to figure out best practices for new developers / companies in the TV space. I’m looking to get information on how difficult it is to create a high end experience on an embedded device. Is it possible to create a great experience in a browser using DOM rendering? Canvas (WebGL) in a browser? I see the following:

Best Performance for rendering (Memory + CPU)

DOM < Cobalt < Canvas (WebGL) < WebAssembly < Native

Ease of Development (# of devs + documentation + experience)

DOM > Canvas > WebAssembly ~ Cobalt ~ Native

While the larger companies are developing Native apps for the best possible experience, is there a middle ground? Can the browser be used as an application platform? What can we do to standardize an approach to building TV apps? Are there quick wins that can be accomplished through new Javascript APIs? Should we all be using WebAssembly or MiniApps? Can we improve the DOM or use a subset of DOM for greater performance? Other thoughts?

GitHub Notification of comment by chiefcll
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Thursday, 21 October 2021 17:08:28 UTC