So... this is really a cool project and I'd love to contribute...
One really interesting idea that came to mind: Once the web portion is loaded in your browser, you don't need an 'active' connection with your mister running a web server...
As such, turning the web piece into a PWA might be really cool. In theory - this would make it so you could configure the app outside of your mister (then you could just add the 'web api' piece to enable this for the MiSTer on boot).
This would enable you to almost develop these two pieces independently (the APIs on the MiSTer and the web app interface)...
So... this is really a cool project and I'd love to contribute...
One really interesting idea that came to mind: Once the web portion is loaded in your browser, you don't need an 'active' connection with your mister running a web server...
As such, turning the web piece into a PWA might be really cool. In theory - this would make it so you could configure the app outside of your mister (then you could just add the 'web api' piece to enable this for the MiSTer on boot).
This would enable you to almost develop these two pieces independently (the APIs on the MiSTer and the web app interface)...
Just a thought!