@LunaticMuch I agree with you on that, voyager is already too noisy for big graphs.
At the same time, the current way of switching query/mutation/subscription is not very intuitive.
Also, it is bad that you need to wait each time you switch between query and mutation.
What we can do is to make tabs on top of the graph view (only if API has Mutation or Subscription root types): https://mui.com/material-ui/react-tabs/#basic-tabs
Also, we can run multiple web workers so query/mutation is rendered in parallel.
Originally posted by @IvanGoncharov in https://github.com/IvanGoncharov/graphql-voyager/issues/206#issuecomment-1499498609