It sounds like you are the creator/a team member, so I just wanted to give you a data point.
My team used insomnia for a while. We were on the paid tier. My boss had us bail because of pain points we were having with syncing environments. People were overwriting changes on accident, and it was hard to coordinate.
I like Insomnia more than what we have now, but I wanted to let you know that was the pain point that lost you some customers so you can hopefully address that to avoid losing future customers. :-/
I think something like a "locking" feature or the ability to prevent certain users from modifying certain shared environments would have helped.
Personally I think it's a lost opportunity that you're still not allowing people to save the configuration in the project they're working on.
We switched to first vscode rest client and now the intellij embedded one at this point, as having the calls saved in clear text makes it possible to just have a request directory directly in the Repository... With transparent reviews etc.
My team used insomnia for a while. We were on the paid tier. My boss had us bail because of pain points we were having with syncing environments. People were overwriting changes on accident, and it was hard to coordinate.
I like Insomnia more than what we have now, but I wanted to let you know that was the pain point that lost you some customers so you can hopefully address that to avoid losing future customers. :-/
I think something like a "locking" feature or the ability to prevent certain users from modifying certain shared environments would have helped.