Problems resolved for creating multiple users. I still encounter some obstacles, but I'm learning to work around them until they are resolved. I still can't offer this to customers after I don't feel confident in 2.0, but I know I will be able to in a short time.
I use it daily and develop components daily according to the needs of clients, hotels, hospitals here in Brazil. I'm still not able to deal with the problems enough to be able to switch from 1.0 to 2.0. These are simple things that can be confused by me as problems and just a lack of knowledge on how to use them. I try to throw everything here so that the developers mainly see it. We still have a panel dedicated to printing data when my work is 90% limited to activations. I rarely make a graph because in automation, in the line I work in, graphs are useless for almost anything other than monitoring energy consumption. I understand that this must be the main use of node-red, but I would like to make this observation. This may help to expand the use of the panel in node-red, thinking in the same proportion in terms of weighting in graphs. Here's a basic example of an interview I have... I'm not managing to align things properly in 2.0 to the point where it handles responsiveness in a memorable way like 1.0 does.
I have experimented with various approaches, but currently, I am using GRID. However, I still do not fully understand how to position the elements; I feel that this skill is no longer under my control as it was in version 1.0. I believe this gap in my understanding to be the cause of my difficulties. The combination of writing the code for the element along with configuring the groups and pages is not clear to me. Nevertheless, this was never an issue before.
It's worth noting though that the layout I'm seeing on that left-side doesn't look right. There is little consistency in the alignment which is surprising
All my elements follow a 1x1 or 2x1 grid, rarely deviating from this pattern, just as it was in version 1.0. Your work, when applied within its operational guidelines, fulfills its intended purpose. It is I who attempt to flexibilize things in order to implement updates without alarming clients with abrupt changes. In the examples below, we see the same 6x1 concept in 1x1 elements, yet they appear drastically different both on desktop and mobile. This is another challenge I am grappling with.
Back to roots. DB1 didn't provide option to design the page. You can only design card content. What you did is just adopted your things to have something . This is same for DB2 with exception, you can make page as you wish if you don't use ready made (grid, fixed) layout. Make it then as you wish and you are on control. Don't fight with options if they don't bring any goodies for you.
And if you ask if to create your own layout is easy or complicated task then there is no straight answer.
The thing starts with pen and paper and only after seeing sketches the one can say anything about the complexity. The strategy of layout depends entirely on input of designer and product owner.