The BenchVue team is looking to make some enhancements to our user on-boarding process. i.e. the process by which a new user becomes familiar with all parts of BenchVue when they first download it - the app tab, the apps, test flow, data manager, demo mode, library etc.
Hi Sid,
From what I remember when I first used BenchVue, the on-boarding was difficult. Being greeted by the empty Bench and a message that nothing was detected along with the need to launch IO Libraries was not friendly. If the software already knows where I need to be, then it should take me there. The old software design mantra, "Don't make me click," applies.
I don't know about the latest BenchVue (I'm currently at 3.7), but having to find various disparate tools in order to accomplish tasks on the same instrument took some time to get your head around. For example, if I'm looking at the DMM app to set up some logging and decide I want to send some SCPI commands, I'd prefer to just hit a button in the DMM app to get a SCPI console rather than open IO Libraries in order to find the Connection Expert.
Once you figured out how to add and interact with instruments, it was also strange when sometimes devices would be detected automatically at the next startup, but other times you'd have to open the apps or the IO Libraries to get them to be recognized again. That might just be a bug.
Another issue that comes to mind is when using logging. After stopping a log (or it stops itself), if you change the setup, a modal dialog pops up to warn you that the log will be lost, but only when you've already partially changed a configuration value, rather than when clicking on the field. As a result, some values such as start/stop times are auto-zeroed when the interruption prevents you from entering a valid value.
Anyway, those are some things that come to mind.