OpenBeken Web Application (also called "secondary web panel") is a VUE/Javascript page that provides an alternate graphical interface, commands, pins, logging system, file system etc access for OpenBeken devices. OBK Web Application is hosted on external server and not on OBK device, so the flash memory cost of it's javascript code is virtually free (it takes no space in BK7231 flash memory). Of course, the REST interface used by our app still is in BK flash, but it's not taking that much memory.
The Web App works by BK (or W600/W800/BL602, etc etc) device plugging it's IP address to the external javascript application and that javascript application sends REST queries to that IP.
By default, our WebApp will not obviously work without the internet and that's the main drawback of such approach, but the URL of the WebApp field allows you to change the WebApp VUE location to any server you want - for example, to one in your local network.
Just check out our WebApp code:
https://github.com/OpenBekenIOT/webapp and host in your server and set the URL of the WebApp to point to your server - and then you can even modify WebApp however you want.
In future, it should be possible to add free in terms of flash memory graphical interfaces of many features to the WebApp, for example, the calibration commands of energy metering sockets could be ran entirely from WebApp and we already have interfaces for that (so there will be no extra usage penalty in terms of device flash memory).
There are just lots of possibilities with that Web App.
The code is in gh-pages, as we are using their deployment system. (Well, to be honest, I think it's possible to change git to deploy from main, but that's the way it was setup in the past)