Apologies if this is the wrong forum to post a topic like this - I saw several other add-on/app questions here, so I hope this is the right place.
I am building a metadata manager for Home Assistant, but I'm struggling to create the UI.
All the core functionality for this app (add-on) is created in Python and is working. The purpose is to manage metadata (no surprise there) - keep track of the metadata, support operations on individual metadata items as well as groups, track and manage dependencies (e.g., automations to helpers and entities and devices), discover new metadata (e.g., new devices), allow for documentation beyond the basic metadata supported in HA (e.g., backlog, purpose, instructions), versioning, policies/governance, and other operations. It also supports exporting and importing metadata, allowing for off-line editing. And converting between various representations/schemas (e.g., "native HA CSV," native HA JSON, Matter-JSON). And sorting/filtering/discovering/editing. And deploying (taking edited metadata stored in the metadata manager and updating the system's internal metadata with edits made in the metadata manager (e.g., changing properties of devices or entities). And cleaning up "orphaned" metadata no longer needed (e.g., helpers no longer used). It runs as an app (including the UI) on HA, so you don't have to install anything anywhere else to run it. And other stuff folks recommend.
My problem is I am not at all a web developer. I tried to build the UI as a single-page app in Svelte. I got it to run, but I keep running into bugs that are almost impossible to track down, and seemingly impossible to quash all at the same time (e.g., interactions between 'effects'). My core functionality took me maybe a 100-200 hours to build and thoroughly test. The UI is taking me multiples of that and I still don't have something that covers all the backend capabilities or even a decent fraction of them without bugs due to interactions (e.g., change to another tab and automatically adjust the paging, show anything that has been edited offline or in the UI before applying/deploying the changes).
Any suggestions for how I should build the UI? Is there a better approach than an SPA in Svelte? Alternatively, anyone want to volunteer to work on a UI for this? I have extensively documented the user experience, use cases, layouts, etc.
Thanks for any suggestions or offers!