Skip to content

Development Roadmap

hipersayanX edited this page Feb 17, 2026 · 24 revisions

This is a list of what is considered more or less high priority in the project, and things that are in progress right now. The numbers of features in each release are intended to comply with short (or shortest as possible) development cycles.
NOTE: The road map may change in between, so not all features are guaranteed to be implemented, or all bugs to be fixed, take this just as a wish list.

Webcamoid 9.3.0

  • Upload Webcamoid to Google Play Store. (In progress)

Webcamoid 9.4.0

  • Move graphics pipeline to OpenGL/Vulkan.
  • Support simple virtual avatars (PngTuvers like).
  • Support scene modes.
  • Support streaming.
  • Stream only a Window, or special region from the screen. (issue #381)
  • Virtual backgrounds (issue #635)

Webcamoid 10.0.0

WebApp UI

I don't promise anything, I'm just putting this option on the board. Thoughts?

Scripted plugins (aka Add-ons)

Current plugin model is ok for high performance frame process and low level system access in case you want to add support for some hardware device, but is a pain in the ass if you want to distribute your own plugins outside Webcamoid's tree, and target multiple platforms. So, the best way to solve this issue is to allow developers to create platform independent plugins using an scripting language, in this case using Qml and JavaScript duo. It could be modeled after WebExtensions (but without the web, obviously).

Plugin repository support

Once the developer has completed writing the their Add-ons, the next step is distributing it. One way will be distributing it through compressed packages, and it's ok and will be possible to do so, but this leads to a big problem: upstream syncing and security updates, that's why a plugin repository is needed. The repository will be designed to be decentralized, including repositories index, and using a VCS infrastructure, so developers will be able to create and distribute their Add-ons, create repositories and repositories index, through their Github, Gitlab, Bitbucket, other VCS instance, or their own VCS instance. The VCS infrastructure will be implemented in git first, other VCS systems could be added later. You have a good example of this design here.

Clone this wiki locally