I’ve just finished building out a demo page for a new Bubble plugin I’ve been working on: Picture-in-Picture (Desktop).
Picture in Picture (Desktop) Demo
As this is my first paid plugin, I wouldn’t ask anyone to subscribe unless it’s genuinely useful for your app, but I’d really appreciate some developer eyes on the demo.
I’ve tried to make it comprehensive enough that you can properly experiment with Document Picture-in-Picture before ever needing to install anything, including demos for:
• Vimeo
• YouTube
• Custom HTML
• External URLs
There are different examples/use cases within the demos, as Document PiP can do quite a bit more than just floating video.
My main question: is anything missing? Is there a use case you’d want to test that I haven’t covered? Something that isn’t clear in the Setup Guide? Or anything you’d expect from a Bubble plugin demo that you can’t currently do?
Very happy for people to poke around and be critical. I’ve been looking at it for far too long to reliably spot the gaps myself.
Thank you in advance!
This looks like a really useful plugin, especially being able to test different PiP use cases without installing anything first. I’d love to see examples of how it handles mobile responsiveness and what happens when users navigate between pages or switch tabs, as those are the kinds of things that can make a big difference in real-world apps. Great work putting the demo together!
Thank you so much for taking a look - the feedback is much appreciated! 
Unfortunately, mobile support is currently limited by the browsers themselves rather than the plugin. Document PiP (which powers the HTML, URL and YouTube examples) isn’t currently supported in mainstream mobile browsers, including Chrome on Android, so I’ve positioned the plugin as desktop-only for now.
On desktop, you can test tab switching directly in the demo! Open any example in PiP, then switch to another browser tab or another application: the PiP window should remain floating and interactive. You can also resize the window to see how the content responds.
You’ve raised a really interesting point about demonstrating these behaviours more explicitly though - I’ll look at how I might optimise that on the demo page. Thank you again for taking the time!
