I’d like to add some things that came in my mind.
Number of UIs
I like the Idea of having a combined UI for users and admins, but controlled with a right management system. And a special one for tablets seems reasonable to me. At the end I think, that the discussion about one, two or three is a bit unnecessary. Why?
- If I change the configuration in an administrative view, I want to reach the result without entering another URL. I think most people would agree. But whats the difference between a link to the user-view in the same or a different UI? There is none in my opinion.
- If an end user does not see the admin-gear-wheel-icon, whats the difference? None.
I like the idea of having a rights management. I would expect it to allow different sitemaps for different users or hiding parts of a sitemap. I would like that a lot! And…
Having an integrated rights management and user authentication would make things easier without doing that reverse-proxy-magic stuff, that no normal non-it user would be able to implement.
Ease of use: UI widgets
Why the hell do we all need to fiddle for hours to get the functionality running everyone likes to use? There are some approaches with Habpanel’s widgets and the Paper UI control part. But in my opinion it is not enough. Why?
- There is no default widget for most used things, like SONOS.
- The design differs, if different people start building those widgets with a lot of HTML/CSS code.
Taking Sonos as an example: Today the basic functionality is done by combining sliders, music-control, text fields and images for the cover art. Takes time and may be acceptable. But did you try to make multi-room audio work? This is a huge task to do with loads of items and rules. If we talk about the common user (non IT programmer guy), in my opinion a binding should provide a nice looking widget, well designed by using the standard style guide, with all needed basic controls and - in this example ideally - multiroom support.
That could mean that a binding should have a further way to define the standard widget for specific things and a way to include necessary rules and how channels have to be linked to the widget and rules to work.
I would really love to have an on-premise (non-cloud) voice recognition integrated with ease of use as the future UI…