When I first started with B4J and Websocket solutions, I wanted to do the exact same thing ... create a GUI server so that I'd have better feedback/monitoring of the process. Also, because I was more familiar with creating GUI B4J/B4A/B4I apps and less-so with NON-GUI B4J apps.
After doing a few of those types of solutions, I went to, when creating a new B4J websocket server, doing a simple website interface to it. Even if the final solution had nothing to do with web connectivity. It's a whole lot easier/faster to refresh the display of a website after any modifications to the NON-GUI websocket Server than it is to rebuild the B4A/B4J/B4I app.
Then, several years ago I grew a brain and decided to make a universal (at least to my own projects) websocket connector and (testing) website that would pick up the new server as being there and connect to it automatically. No having to build something custom each time to connect, test, and monitor the development process from the client end. This came as an off-shoot of the universal B4J server monitor project and has greatly increased the productivity.