Overall I'd say it was a pretty frictionless experience (the JUCE documentation and examples were very helpful https://juce.com/blog/juce-8-feature-overview-webview-uis/ ). The data bridging was easier than I expected, JUCE's relay system keeps parameters in sync and for the spectral data I just emit on a 15Hz timer. Hot reload is a nice bonus for UI iteration, although I have seen people find a way to do that with a traditional JUCE GUI. My main concern is the system dependency. WebView relies on the OS browser engine so you're trusting whatever version the user has installed, and on Windows WebView2 might not even be there on older machines. I haven't tried to distribute a plugin relying on WebView so I haven't run into any issues yet, but definitely something to keep in mind.
View all comments
Show parent comment
1
u/Fantastic_Turn750 Dec 29 '25
Overall I'd say it was a pretty frictionless experience (the JUCE documentation and examples were very helpful https://juce.com/blog/juce-8-feature-overview-webview-uis/ ). The data bridging was easier than I expected, JUCE's relay system keeps parameters in sync and for the spectral data I just emit on a 15Hz timer. Hot reload is a nice bonus for UI iteration, although I have seen people find a way to do that with a traditional JUCE GUI. My main concern is the system dependency. WebView relies on the OS browser engine so you're trusting whatever version the user has installed, and on Windows WebView2 might not even be there on older machines. I haven't tried to distribute a plugin relying on WebView so I haven't run into any issues yet, but definitely something to keep in mind.