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.
- 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" ).
Your feedback is so constructive, THANK YOU Man.
I'm glad you take criticism so well :)
> 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.
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.
Also, that's the sexiest README I've ever seen.
I wouldn't make the claim that this is usable by business managers; if one of the goals of this tool is to make it business-focused then you might want to add an abstraction and front-end it with BPMN as that's the general language understood by most folks familiar with process mapping. Check out Camunda's modeler for an example (https://camunda.com/products/modeler/). I have quite a bit of experience in this space as working with business-focused modeling tools and then building the full solution has been my career for the last 5+ years.
Either set it up in your application, or you can use the hosted version passing in the URL of your API (you might need to configure CORS): https://apis.guru/graphql-voyager/?url=%20https://dog-graphq...