I totally agree !

It seems like a nice framing of the deviceInformations to be displayed. Good job on that.

Instead of hard-coding values in the QML file, I would rather bind it to properties (i.e.: property string deviceName: "UNKNOWN") and then use the main.swap(_paths.[...], deviceInformations).

Then, you can "mock" deviceInformations with hard-coded string values from somewhere, and fix it up for real deviceInformation once ready.

Keep in mind that deviceSummary is a direct exemple of what I mean. You may refer to it at your convenience.