Replies: 1 comment
|
Usability of the system is very important. My comments about those questions:
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Context
We recently built a workflow for a collaborator from a research lab and shared it with them to run themselves. They are an expert in their scientific domain, but not previously a Texera user.
The workflow itself worked, but over the course of a few days we answered questions that were "how do I do X in the UI" rather than anything about workflows, operators, or the analysis.
Sharing what came up here to gather feedback from other developers and users who have also experienced this while learning how to use Texera.
What came up
For those of us who work on the frontend, the topics below are obvious, but for users trying to learn how to use Texera for the first time, they are problems without clear guidance.
Actions that are hidden
There are many features that don't make themselves obviously known to a user. For example,
Show ResultsandExport Resultsare both discoverable only if you already know where they are: one is a button in the lower-left corner of the workspace, the other is in a context menu when right-clicking an operator. Nothing on the operator suggests either exists.Controls that block without explaining
Some dialogs can stop the user without saying what condition failed or how to satisfy it. For example, the
Selectbutton for a dataset inFile Scandoesn't make it clear that you need to click the file after selecting a dataset from the drop-down. The "Export unavailable" dialog names the blocking dataset but not the rule behind it: the dataset is marked as not downloadable, and that restriction propagates to everything downstream of it. Without knowing that, there's no way to guess the fix.Questions for discussion
All reactions