Skip to content

Add a native QML UI interface #93

@AIIX

Description

@AIIX

Add a native QML UI interface instead of webviews as being used in #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:

  • Using a web interface means one would assume one is always required to remain connected to the internet and devices that can be controlled over LAN when no internet access is available will not be accessible
  • Website availability and blocking can cause the skill UI to be unusable in environments with restricted web access
  • Using a browser is more performance degrading as its using a higher number of physical resources of the hardware, The Qt Webengineview is an entire chromium stack running on the device
  • At 480x800 you would probably require zooming into a screen to just be able to toggle controls on a web interface
  • You likely are to lose the ability to control dials and toggles via voice interface when using webpages, will the dial on the webpage switch to 4% if I have the web page open and ask Mycroft to turn the brightness of my smart bulb down to 4 from 50 via voice"

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions