Could we create a web-based version?
Feature RequestImprovementQuestion
I would like to build a web-based version, because I want to consolidate our existing API tests and make them a shared asset for the team.
I would like to build a web-based version, because I want to consolidate our existing API tests and make them a shared asset for the team.
Sign in to leave a comment.
Unfortunately a full web version is extremely difficult because of Yaak’s core architecture relying so heavily on Rust + a NodeJS plugin system.
Do you actually need full Yaak functionality or more of a read-only browser? I’d love to hear more about how you’re using a browser based client currently.
APIs can sometimes be regarded as assets. If I can use Yaak via the web, I can keep those assets on the web side, which makes it convenient to open a browser and use them at any time. Moreover, in the future, I can smoothly hand over my API assets to team members. Team members can also directly use this web‑based Yaak without needing to install additional software on their computers.
k, so it sounds like you do want the full Yaak experience in the browser. I might take another look at how hard this would for Yaak’s current feature set. Degrading/removing hard-to-support things like grpc and websockets might make it easier
Thanks for looking into this! I totally understand that supporting every protocol in the browser is a heavy lift. For our team, the core need is actually HTTP/HTTPS API testing plus team sharing and handover – those are the real assets. If gRPC and WebSocket are dropped initially, that’s completely fine with us. We’d love to have a usable web version first, and we can always extend later. Please let us know if we can help with testing or feedback.
👀
Great! Looking forward to it.