Stremio shell using WebView2/mpv, written in Rust
Find a file
Vladimir Borisov 385259b6d5
Fix libmpv
2025-11-27 18:12:02 +02:00
.cargo Windows no ARM build 2025-11-12 18:02:41 +02:00
.github/workflows 64 bit build 2025-06-30 12:39:12 +03:00
bin Us correct DLLs 2025-08-05 13:49:03 +03:00
images Installer fixes 2024-04-17 11:28:23 +03:00
mpv-arm64 Windows no ARM build 2025-11-12 18:02:41 +02:00
mpv-x64 Windows no ARM build 2025-11-12 18:02:41 +02:00
setup Update the code dependencies script 2025-08-05 13:49:22 +03:00
src Check for architecture specific updates 2025-11-27 16:35:40 +02:00
.gitignore 64 bit build 2025-06-30 12:39:12 +03:00
build.ps1 64 bit build 2025-06-30 12:39:12 +03:00
build.rs Check for architecture specific updates 2025-11-27 16:35:40 +02:00
Cargo.lock Version bump to 5.0.14 2025-11-27 16:57:14 +02:00
Cargo.toml Version bump to 5.0.14 2025-11-27 16:57:14 +02:00
generate_descriptor.js fix logging 2024-12-23 16:10:39 +02:00
libmpv-2_arm64.zip Windows no ARM build 2025-11-12 18:02:41 +02:00
libmpv-2_x64.zip Fix libmpv 2025-11-27 18:12:02 +02:00
README.md fix typo 2025-02-05 09:14:50 +02:00
rust-toolchain.toml Windows no ARM build 2025-11-12 18:02:41 +02:00
server.js Update server.js to v4.20.15 2025-11-27 15:50:34 +02:00
upload.ps1 Remove old certificate and replace the automatic build script with manual scripts 2024-11-19 17:10:42 +02:00

Stremio shell: new gen

A Windows-only shell using WebView2 and MPV

Goals:

  • Performance
  • Reliability
  • Easy to ship

In all three, this architecture excels the Qt-based shell: it is about 2-5x more efficient depending on the use case, as it allows MPV to render directly in the window through it's optimal video output rather than using libmpv to integrate with Qt.

This is due to Qt having a complex rendering pipeline involving ANGLE and multiple levels of composing and drawing to textures, which inhibits full HW acceleration.

Meanwhile in this setup MPV uses whichever pipeline it considers to be optimal (like the mpv desktop app), which is normally d3d11, allowing full HW acceleration.

For web rendering, we use the native WebView2, which is Chromium based but shipped as a part of Windows 10: therefore we do not need to ship our own "distribution" of Chromium.

Finally, this should be a lot more reliable as it uses a much simpler and more native overall architecture.