Microsoft Proposes a Dual-Screen Future for Web Apps

Posted on February 11, 2020 by Mehedi Hassan in Dev, Hardware, Web browsers with 2 Comments

It’s no secret Microsoft is going all-in on dual-screen devices. So far, the company has talked a lot about developing dual-screen experiences for Android, and it’s today talking about dual-screen experiences on Windows 10X.

But what about the web? This week, Microsoft is officially sharing its plans for bringing the benefits of dual-screen devices to the web.

The company is revealing how it plans to allow developers to build web apps that take full advantage of dual-screen devices. Microsoft is proposing a new JavaScript API and a CSS media query that will enable web developers to take better advantage of all the upcoming dual-screen devices.

Microsoft’s proposed system will make it easier for developers to adapt their websites to wider-screens UI patterns, and adapt to these new types of dual-screen devices without making significant changes to their existing website design. “The web platform does not yet provide the necessary primitives for building layouts that are optimized for foldable experiences. Developers may be able to solve this by taking a hard dependency on a specific device hardware parameters – an approach that is fragile, not scalable, and requires work duplication for each new device,” the proposal reads.

The company plans to contribute its implementation for these new APIs to Chromium. Microsoft is also adding the ability to remotely debug dual-screen devices from Microsoft Edge on their desktop.

Microsoft has detailed its proposal on GitHub here, where you can find out more about the technical details for these new APIs.

Tagged with , , , ,

Join the discussion!

BECOME A THURROTT MEMBER:

Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Register
Comments (2)

2 responses to “Microsoft Proposes a Dual-Screen Future for Web Apps”

  1. Avatar

    iantrem

    Another reason why Edge has taken on the Chrome engine. Microsoft proposes CSS and JavaScript changes which will then need to be baked into the Chrome engine which means Google needs to be on board. If Edge had it's own engine still, Google could just ignore it and go it's own way.

  2. Avatar

    nbplopes

    Devs will only touch this if it helps them sell more. With no customer base in dual screen products ... it will never happen. If it had 100 million it would not happens. Much more had UWP and ...


    So there MS should be proposing much more rather than throwing peanuts to monkeys. That era has passed.


    In contrast, Azure team is doing ... a great job.

Leave a Reply