Almost every remote presentation tool works the same way: it captures your screen and relays those pixels to viewers. Your slides are just whatever happens to be on screen at the time, so screen sharing carries everything, the deck, the demo, the browser tab you forgot to close.
We split those jobs. In Decklit the deck is rendered and synced as state, so when you move to slide seven, everyone's browser moves to slide seven. Nothing is captured, nothing is encoded. Screen sharing is still in the product, but it's now free to do the thing it's genuinely good at, showing a live demo, a spreadsheet, a browser, rather than being the delivery mechanism for slides. That's what Dual View is: your deck, your shared screen and your participants all visible together on one page. A demo no longer replaces your presentation, it sits next to it.
Three things fall out of separating the two:
You can present from a phone browser. Not join from one, present from one. iOS doesn't let browsers capture the screen, which is why browser-based screen-share tools show an apology popup on mobile. Slides don't need capture, so the constraint disappears.
Slides stay sharp on weak connections, because there's no bitrate to degrade, the image already arrived.
Bandwidth and battery drop a lot, since nobody is encoding and uploading video of a screen for the whole session.
@luca_simeone Outstanding launch,How does protect the security and privacy of uploaded files to ensure unauthorized viewers cannot extract raw slide assets directly from the DOM or network inspect panel?