Just tried it and it works really well. I just discovered Yaak and seriously like its minimalist UX. Keep it up!
To that end, I thought I’d share I found myself searching for the button to close the websocket connection for like 15 seconds — might be nice to have a “stop” button or something like that next to the button to send a new message instead of the “clear connection” button burried in the dropdown. This is not critical, so feel free to ignore.
Also, it looks like params don’t get added to the query for websockets. Feels like a bug.
Thanks for all the great work, Greg!
Gregory SchierOP·a year ago
Thanks for the feedback!
The close WS button is next to the send message button. Is it not showing for you?
I just fixed the URL param bug (and a couple others), which is live in Beta 13.
Hm, I could swear I clicked on that x button and it did nothing. I assumed it was a button to clear the textfield on the left, and that it didn’t work. Anyway, I just tried it again and it worked — user error I bet.
I confirm Beta 13 fixes the params bug. Thanks!
Gregory SchierOP·a year ago
https://yaak.app/blog/2025.1.1
Robert Hurst·a year ago
Very happy to see this feature land @Greg Schier.
My only gripe is that, I cannot share a connection with multiple saved messages. Often web socket connections are stateful. It would be helpful to be able to open a connection, then be able to send one of many messages down the connection. For example, our product uses a websocket for almost all communication with our backend, and before any messages can be sent, an auth message is sent first. Once this is done, subsequent messages are sent on the same connection. It would be nice if there was a way to share the connection for a web socket request between several saved messages if, for example the http url is the same.
None the less, I would like to thank you all for landing this.
Gregory SchierOP·a year ago
Great feedback! I do want to add the ability to swap messages to both gRPC and WebSockets but haven’t quite refined the design. Keep an eye out for this in the future!
Robert Hurst·a year ago
Fantastic! Will do 🍻
Paul Jefferson·a year ago
@Greg Schier firstly, thanks very much - really enjoying Yaak. Secondly, will the above request be tracked here:
I can’t switch to Yaak unless websocket apis support is added. Can’t wait for this feature to be added.
Please add this feature guys, it’s the most wanted one by far
Have patience! There’s only one of me working on Yaak. The current big project is data sync, then this will likely be started after that
Thank you for being so transparent with it!
I’m finally able to start work on this so please let me know what you need! 🙏🏼
Introductory WebSocket support has been added to the current beta. Give it a try and let me know what you think! https://yaak.app/blog/2025.1.0-beta.12
Just tried it and it works really well. I just discovered Yaak and seriously like its minimalist UX. Keep it up!
To that end, I thought I’d share I found myself searching for the button to close the websocket connection for like 15 seconds — might be nice to have a “stop” button or something like that next to the button to send a new message instead of the “clear connection” button burried in the dropdown. This is not critical, so feel free to ignore.
Also, it looks like params don’t get added to the query for websockets. Feels like a bug.
Thanks for all the great work, Greg!
Thanks for the feedback!
The close WS button is next to the send message button. Is it not showing for you?
I just fixed the URL param bug (and a couple others), which is live in Beta 13.
https://yaak.app/blog/2025.1.0-beta.13
Hm, I could swear I clicked on that x button and it did nothing. I assumed it was a button to clear the textfield on the left, and that it didn’t work. Anyway, I just tried it again and it worked — user error I bet.
I confirm Beta 13 fixes the params bug. Thanks!
https://yaak.app/blog/2025.1.1
Very happy to see this feature land @Greg Schier.
My only gripe is that, I cannot share a connection with multiple saved messages. Often web socket connections are stateful. It would be helpful to be able to open a connection, then be able to send one of many messages down the connection. For example, our product uses a websocket for almost all communication with our backend, and before any messages can be sent, an auth message is sent first. Once this is done, subsequent messages are sent on the same connection. It would be nice if there was a way to share the connection for a web socket request between several saved messages if, for example the http url is the same.
None the less, I would like to thank you all for landing this.
Great feedback! I do want to add the ability to swap messages to both gRPC and WebSockets but haven’t quite refined the design. Keep an eye out for this in the future!
Fantastic! Will do 🍻
@Greg Schier firstly, thanks very much - really enjoying Yaak. Secondly, will the above request be tracked here:
https://feedback.yaak.app/p/saved-websocket-messages
Or somewhere else?
Yes, that’s the one to follow as this one is now closed 👍🏼