3 ms·

We're extremely aware of what has made Insomnia successful over the last five years and we want to keep applying the same principles going forward. This is a bi

We're extremely aware of what has made Insomnia successful over the last five years and we want to keep applying the same principles going forward. This is a big reason why we're keeping the existing Insomnia application (now named Core) as a separate, standalone app. Simplicity, focus, and usability are key.

littlecranky67 6y ago
Thank you so much for that attitude and I have to add: I'd definetely spend money on a license if there a pro/everyday-user features that make it worth it, while having a free version so that others in the team can still collaborate and use my output/exports. I'd often find it hard to convince teams or new users with which I collaborate to convince to spend money on a tool upfront just so they can collab with me. But if its only additional/pro features, that won't be an issue. I gave the designer a quick try and it seems there are issues with importing OAS 3/yaml APIs making heavy use of $ref and multiple files, but I will dig deeper into this in the next days and open a bug report if needed.
- gschier 6y ago
  We're tracking that on GitHub. Feel free to follow along or submit additional details :) https://github.com/Kong/insomnia/issues/2082 https://github.com/Kong/insomnia/issues/2082
PaulStatezny 6y ago
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.
- gschier 6y ago
  We currently have a new sync system in beta that works more like Git, making it easier to control what is shared and when. https://support.insomnia.rest/article/67-version-control https://support.insomnia.rest/article/67-version-control
  - 411111111111111 6y ago
    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. Exporting/importing is just way too troublesome.
- dyu 6y ago
  Can it use an exportable/importable file as source of truth which you can then check into git?
  - gschier 6y ago
    Yes, many teams use the import/export feature to do exactly this.

littlecranky67 6y ago

Thank you so much for that attitude and I have to add: I'd definetely spend money on a license if there a pro/everyday-user features that make it worth it, while having a free version so that others in the team can still collaborate and use my output/exports. I'd often find it hard to convince teams or new users with which I collaborate to convince to spend money on a tool upfront just so they can collab with me. But if its only additional/pro features, that won't be an issue. I gave the designer a quick try and it seems there are issues with importing OAS 3/yaml APIs making heavy use of $ref and multiple files, but I will dig deeper into this in the next days and open a bug report if needed.

gschier 6y ago
We're tracking that on GitHub. Feel free to follow along or submit additional details :) https://github.com/Kong/insomnia/issues/2082 https://github.com/Kong/insomnia/issues/2082

PaulStatezny 6y ago

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.

gschier 6y ago
We currently have a new sync system in beta that works more like Git, making it easier to control what is shared and when. https://support.insomnia.rest/article/67-version-control https://support.insomnia.rest/article/67-version-control
- 411111111111111 6y ago
  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. Exporting/importing is just way too troublesome.
dyu 6y ago
Can it use an exportable/importable file as source of truth which you can then check into git?
- gschier 6y ago
  Yes, many teams use the import/export feature to do exactly this.