the topic was discussed in 2-3 threads on the side already but I still think there is some clarification needed.
With PaperUI we can discover things and these will be stored in a system-side database. I’m puzzled about the next step at this point.
Is the user supposed to manage all his items solely inside of PaperUI, a fresh and restrictive webapp?
Will there be any way to edit the items more directly in parallel to rules etc.? How are we able to manage items which are not discoverable (e.g. helper items)? What is the intended emergency strategy?
OH1 had the amazing key concept that all of the user-provided data got (defined and) stored in config files. Config files are clear and unambitious and can be backed up, versioned or mass-edited. They should be the corner stone of a nice graphical tool like PaperUI, not their predecessors.
Edit: After reconsideration, the important thing is not to restrict the user. Moving on from configuration files for items in favor of a more powerful system is acceptable under certain circumstances, please read my later comment about my opinion and ideas.
What are your thoughts, how do you think should the ideal setup look like?