MycroftAI / skill-homeassistant

Mycroft Skill/Integration for Homeassistant
GNU Lesser General Public License v3.0
115 stars 62 forks source link

Add a native QML UI interface #93

Open AIIX opened 2 years ago

AIIX commented 2 years ago

Add a native QML UI interface instead of webviews as being used in https://github.com/MycroftAI/skill-homeassistant/pull/84 A native QML UI provides more controls over the UI integration than a web interface, For example, a basic QML UI can be implemented for a group of devices and each individual device within a group itself (just to be clear the below is just an example of what it can look like from my pov as a community dev)

devices-ui-1 devices-ui-2

Some of the cons of using a web interface instead of a native interface:

NeonDaniel commented 2 years ago

A few comments in favor of the Web UI:

I think both approaches are useful; I think showing a default QML when you match a voice intent makes sense since that intent should specify an item or group. For something like a home page or control panel (or an intent to 'show {x} dashboard'), I think it makes more sense to use the Lovelace UI.

pfefferle commented 2 years ago

I made a PR for loading the Lovelace UI, if you want to give it a try: https://github.com/MycroftAI/skill-homeassistant/pull/91