Thanks for the answer, but the question actually goes deeper 😉
For us as developers of an app (SNAP) for the ctrlX, it is very unclear what role the ctrlX dashboard will later have for users (machine users). Will it only be a service view and apps will actually never be launched via this, because the end user will not (should not) work on it? Or is this the center of power and you should design your app to achieve the best user experience when you launch (and configure!) the app from here?
Do you imagine that users have the browser frame (back button and url line) visible when they view your web HMI? If not (would probably look more professional), the only way to jump from an app (fullscreen) back to the dashboard or an HMI is to have custom back buttons (in the apps).
But if we want to embed our app in a HMI (e.g. SmartHMI ... iFrame) not fullscreen, so that the enduser has a simple operation without jumps between app and HMI, the situation is different. Here you do not need a back button. And if the goal of an app should be to harmonize perfectly with a SmartHMI (and not the ctrlX dashboard), then the question is rather if we should concentrate on this and also design the configuration of the app so that we can do it directly in the HMI and not in the ctrlX dashboard...
I hope you see our problem... ctrlX Dashboard or SmartHMI How should an app be used (and where configured)? Are there any recommendations here?
... View more
