For QML development it is current necessary to install and start Kube, log in, and navigate to the wanted UI.
For complex new UI's its possible to simply start the UI standalone allowing for quicker iterations, but that is not a usable approach in the long run.

Ideally it would be possible to be able to edit QML files and get a live update of the effects, that is however not straightforward because:

• Install and sourcedir differ and we normally load all qml files from the install dir
• We don't get live reloading for free (needs to be implemented)
• We have to deal with application state and dependencies

The following ideas could improve the workflow:

• Ensure we have appropriate individual components that can be started standalone. i.e. the composer. This should be achievable but it's important to also somehow make sure we can supply the UI with a suitable application state to work on whatever needs working on.
• Support scripting of the UI that would i.e. allow us to automatically enter the password and navigate to the composer. If possible this could also help in testing.
• Support live reloading of qml files in the normal application. This would mean we still use manual navigation to get to the state we want, but then support live editing the qml files.