This began as an intellectual exercise to challenge the developer community to think out of the box and to create demnonstration models to help flesh out ideas and spur innovation. (See: https://community.hubitat.com/t/lets-model-the-change/162063.) As these things tend to do, there was a little scope creep as I kept fleshing out the model and I ended up with an app that could act as a UI shell for the hub. It allows multiple active regions (think windows) that can be dragged, resized, maximized, minimized and closed. Open regions will persist across sessions so if there is a set of applications, devices, etc. that you always want to look at you could set it up and it will be the order you left the next time you open the app.
For me, it works better on a larger screen, but I've run it on an iPhone and iPad also.
Interesting that you released this app when Hubitat has a new version. I believe that your app has much more significance as an improved user interface.
Thank you for the compliment. Timing on the release of this app and the HE version release is purely coincidental, and, other than the HE release adding plumbing for the apps/automations/integrations split, unrelated (I actually borrowed their idea on that). I had intended on finishing this work a month or so back, but had to spend some time away from the keyboard that I wasn't planning on, and then had to wrap may head around where I was going with this code again.
UI is a tricky animal as you need to juggle a variety of screen sizes and resolutions, with system resources, responsiveness and supportability. Much of the plumbing for this app has only been in place since the last UI overhaul by the HE staff, so without their work this app isn't possible. I did purposefully choose a different UI paradigm from the current HE direction, but only because I believe that by doing so I can spur conversation among the community that may influence future development by HE staff and other developers in the community.
