The problem
People watch tutorials and talks while they work. They follow a coding walkthrough while writing code, or keep a lecture running while they take notes in another tab.
Switching tabs back and forth breaks focus, and each switch means finding the right tab, pausing, and finding your place again. YouTube's own mini-player is limited.
The goal was a player that stays on top of whatever you are doing, that you can move out of the way and resize to fit the screen, and that starts with one click instead of a menu.
For anyone learning a tool or following a talk, the video is the reference, and losing sight of it is the problem.
What we built
YT Float pops any YouTube video out into an overlay with one click.
- Resizable, draggable picture-in-picture window, so it can sit wherever it does not block your work
- Stays on top across all tabs, so the video follows you between tabs
- One-click activation, so using it costs no more effort than opening the video
Picture-in-picture is a browser capability, and an extension is the practical way to connect it to YouTube pages and give it controls that suit this use. The design effort went into the small details of a floating window: where it appears, how it is moved and how it is resized, because a floating player that gets in the way is worse than none.
It is built on Chrome APIs and Manifest V3, and we handled the store listing, privacy policy and submission. For a similar idea, see our Chrome extension development service.
A floating window also has to behave on different screen sizes, so being able to drag and resize it was part of the design from the start rather than an afterthought.
The result
YT Float is live on the Chrome Web Store. Anyone who watches while they work can keep the video in view and stay in the document or tool they are using.
It is a Medkon product, built and published by us, and a good example of a narrow idea done well as an extension.
It also shows how a very small feature set can still be a complete product when the one job is done properly, with a clear listing and a privacy policy.
Frequently asked questions
How do you build and publish a Chrome extension?
We scope the single job the extension should do, build it on Manifest V3 with the Chrome APIs it needs, test it across the browsers your users run, then prepare the store listing, screenshots and privacy policy and submit it. We handle the submission for you.
Can you build a private extension just for our team?
Yes. An extension does not have to be public. We can build one for internal workflows and agree with you how it is distributed. Tell us the repetitive browser task and we will say if an extension is the right tool.
How long does Chrome Web Store review take?
It varies, and it is controlled by Google rather than by us. Clear permissions, an honest description and a privacy policy help it go smoothly. We handle the submission and any follow-up questions from the reviewers.
How much does a custom Chrome extension cost?
Pricing is project-based. A fixed quote follows a free discovery call, once we know what the extension needs to do. A fix or plugin-sized job is usually 1-2 weeks, and a full store, app or platform is 4-8 weeks.