[Feature]: web ui for managing settings in quickbars app

[Gizmopower1]

Short Feature Title

Remote admin

What area does this affect?

User Interface (UI/UX)

The Problem

User able to manage setting in quickbars thrue web browser on local pc

The Proposed Solution

Open webrowser from pc, connect to quickbars with url, modify settings in quickbars

Screenshots or Video

No response

Visuals / Mockups

No response

Additional Information

Eks. Fully kiosk has this feature: https://www.fully-kiosk.com/en/#remoteadmin

Home Assistant Context (Optional)

No response

Readiness Check

• I have confirmed this isn't already a feature/setting in the app by also searching the guide.
• I understand that this is an open-source project managed alongside a full-time job and B.Sc. studies by Omri, and PRs and Issues may take some time.
• I am willing to help provide more information upon request, and test beta builds of this feature.

[Trooped]

Hey,
first of all - I can say for a fact that it's possible with QuickBars, since I implemented a mostly working solution with an actual HA integration, that allowed to edit entities, change settings, etc. - all from Home Assistant.
Unfortunately, it wasn't approved at the earlier stage (even for HACS) due to unrelated reasons, so I abandoned it.

In order to achieve what you described here (with a browser), there are 2 approaches I can think of that are possible:

1. Similarly to the token transfer server (during initial onboarding and setup), we can embed a (quite large) webpage into the QuickBars code itself, which will be mostly HTML, and will run as a server from the app itself (so, the Android TV device). This approach is quite limited, both in look and functionality.
2. Building an API (http requests) inside the QuickBars app, which will allow a client to retrieve information (such as entities, settings etc.) and also set information back.
   This will also require to build a client with a UI, which will be open source (and on another repo) and will communicate with this API.

Now, both approaches are limited in the sense that you will need to be inside some screen in the app to use them (for both security and performance concerns). And it's probably better if we could use some sort of authentication for this.

This is off the top of my head.
If anyone else has suggestions, comments, other ideas - or to contribute to this idea, please reply to me here.