GitHub user eugenegujing created a discussion: Making Texera easier for researchers to get started with
Hi all, I've been thinking about Texera's usability for a while and wanted to open a discussion before filing issues. ## The problem The platform has become more powerful than ever, but for a first-time researcher it has also become harder to get started with. A new user in an empty workspace is already looking at around 55 buttons, panels and tabs before touching a single operator, and the operator menu has 165 operators (64 ML, 50 visualization). A lot of what's on screen is infrastructure rather than research, for example the warehouse and Python environment options. These are all useful, but for a researcher who just wants to get an analysis going, figuring out what they are and whether they matter can take a lot of time and energy. I think while we keep adding features, we also need to subtract on the UI and experience side, so a researcher can get to what they actually want to do without getting blocked by things that are obscure to them. This doesn't mean removing anything. It means changing what shows up by default and how the platform explains itself. ## A few directions These are rough ideas, roughly in order of cost. I'd like to hear which ones people think are worth pursuing before writing anything more detailed. **1. Make the operator menu teach instead of just list.** Search over operator descriptions, not only names, so "remove duplicates" finds Distinct. Hover cards with a one-line explanation and an example, pulled from the operator reference pages being generated in #9031. "Typically next" suggestions based on what's selected on the canvas, computed from how operators are actually chained in existing workflows. And separately, a lot of the advanced features could be hidden by default and turned on or off by the user later once they need them, similar to what #6102 did for the computing unit modal. **2. Hands-on onboarding.** Instead of a "Next, Next, Next" overlay tour, a short guided flow inside the real workspace on a sample workflow: change one operator, run it, see the result, with each step advancing when the user actually does it. This would largely follow what #5104 prototyped (credit to @xuang7 for the idea), plus #9151 for the tutorial workflow that new users get. **3. A platform-wide AI assistant.** Grow the current workspace agent into one assistant reachable from anywhere. First just grounded Q&A about Texera's own features and docs, later dashboard actions like uploading a dataset or cloning a workflow, with confirmation, reusing the existing REST endpoints as the agent's tools. ## What I'm asking - Does this direction make sense for the project? - Any suggestions on these ideas, or better ideas for reaching the same goal? Feedback and any other ideas are welcome. GitHub link: https://github.com/apache/texera/discussions/9246 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
