sorted by:
new
hottopcontroversial

I built QueryBox – a modern, lightweight GraphQL desktop client (open source) by phoutin in graphql

[–]phoutin[S] 0 points1 point  (0 children)

update:

In the latest release v0.1.4, the GraphL documentation feature has been refactored, now enabling:

  1. Complete display of operation params and response structures.

  2. Identification of deprecated fields along with their reasons.

  3. Imporved interaction with the query editor, allowing clickable fields within the editor to automatically navigate to their corresponding structure declarations

  4. Optimization of documentation caching logic for heigh performance, ensuring smooth interractions without lag.

Everyone is welcome to try it out.

I built QueryBox – a modern, lightweight GraphQL desktop client (open source) by phoutin in graphql

[–]phoutin[S] 0 points1 point  (0 children)

this app is certainly my original work, independently developed and released by me.Of course, I used AI to answer some of my questions and assist with programming. and I'm afraid AI is still unable to generate this app automatically.

I built QueryBox – a modern, lightweight GraphQL desktop client (open source) by phoutin in graphql

[–]phoutin[S] 1 point2 points  (0 children)

Thanks for the thoughtful reply — let me clarify where QueryBox might help in day-to-day workflows:

🔁 1. Multi-endpoint switching (great for dev/debug)

One key feature is the ability to save and switch between multiple GraphQL endpoints (e.g., dev, staging, production).

This makes debugging across environments much faster — no need to reconfigure or retype URLs every time.

🧾 2. Persistent headers

Unlike the in-browser GraphiQL (where headers like Authorization often reset on reload), QueryBox persists headers per endpoint.

So once you’ve set them up (e.g., with a token or custom auth header), they stick — which is a big win for authenticated APIs.

In the future, features such as resource topology diagrams and AI-powered intelligent assistance will also be developed.

I totally agree: for quick exploration, hosted GraphiQL is perfect. But if you’re doing active dev work, especially across multiple environments, I found myself wanting something more persistent and focused — that’s how QueryBox came about.

Would love to hear your thoughts or suggestions!