The interface looks really slick, but isn't intuitive at all. I constantly have to refer back to the video to find out how to do anything.
You build the graph from right to left (unusual but ok), but if you try to actually draw your lines from right to left they don't connect, you have to draw them left to right.
To rename something you click the element and type the name. Fairly straightforward, except that the interface gives no indication that this is possible. No blinking text cursor or anything of the sort.
The "arguments" category actually has nothing to do with arguments, it's just "use stuff you named previously". Why is that not something that's connected on the graph?
Oh, right, that's because of the way queries/mutations work. The name of the query is combined from the name of the query node and the name of the output node. But instead of a query having two connectors, one for input and one for output, it just has everything at a depth of one as outputs, and the child nodes of the output are the inputs (actually, that's how types and everything else works too). I certainly wouldn't have guessed that.
Anyone can look at a screenshot of Blender's editor and knows what's going on: labeled connectors, no magic with different layers, etc. Creating them is also straightforward. In comparison, if you show a graph from this tool to a random developer that works with GraphQL he/she likely won't understand what schema the graph is supposed to represent.
Thanks for that feedback. This is really valuable for me. I will correct everything you described here. I am not an UX designer to, so maybe this is the reason of bad UX and UI.
- I will correct drawing the lines
- I will add a blinking cursor during renaming of the node
- I will correct the query node to have input and output
So definitely there is lot of work to do. Deadline for these 3 - Thursday.
I used to work for Visual Effects industry 7 years ago. I was a TD and python scripts programmer. That's why you have spacebar menu ( similar to this in Maya - "Hotbox" ).
> I am not an UX designer to, so maybe this is the reason of bad UX and UI.
UX design is a bit like programing: if you just do stuff and never test it it's unlikely to work. The single most valuable thing you can do for UX is to grab somebody from your target group and let them use your program. If you don't explain and don't comment, you can watch how they will struggle with things you thought would be obvious. Then just change those parts and test with someone fresh until it really is obvious to someone not intimately familiar with the inner workings of the software.
Be careful not to swing too far in the other direction. Users who are unfamiliar with your tool will immediately just want something easy and obvious. You shouldn’t be afraid of having a learning curve if the user can gain fluidity and efficiency. The tricky part is that learning curves will never survive a five minute new-user review, so you have to find more invested users who are willing to do expert reviews.
User interfaces that are forever stuck in beginner mode are just as annoying as ones that are too hard for beginners to start using. This is especially true for visual programming languages.
Good advice! I definitely don't want to make another layer of abstraction as I answered to another question. Maybe I will think about some examples and on-boarding. I will transfer your response to issues tomorrow :)
Hi I resolved some issues: blinking cursor added, connection possible both ways . Those were issues of
https://github.com/slothking-online/diagram
package, right now I am going to update this dependency in graphql editor :)
You build the graph from right to left (unusual but ok), but if you try to actually draw your lines from right to left they don't connect, you have to draw them left to right.
To rename something you click the element and type the name. Fairly straightforward, except that the interface gives no indication that this is possible. No blinking text cursor or anything of the sort.
The "arguments" category actually has nothing to do with arguments, it's just "use stuff you named previously". Why is that not something that's connected on the graph?
Oh, right, that's because of the way queries/mutations work. The name of the query is combined from the name of the query node and the name of the output node. But instead of a query having two connectors, one for input and one for output, it just has everything at a depth of one as outputs, and the child nodes of the output are the inputs (actually, that's how types and everything else works too). I certainly wouldn't have guessed that.
Compare Blender's node editor: https://code.blender.org/wp-content/uploads/2012/01/node_gro...
Anyone can look at a screenshot of Blender's editor and knows what's going on: labeled connectors, no magic with different layers, etc. Creating them is also straightforward. In comparison, if you show a graph from this tool to a random developer that works with GraphQL he/she likely won't understand what schema the graph is supposed to represent.