Yes! I plan to maintain it long-term! I will be rolling out some feature improvements and updates these few weeks.
I still think Kong did a good job in crafting the product. I started using Insomnia in my previous company 3 years ago and our team loved it.
What happened recently felt a little bit like the Unity fiasco (of course, in a much much smaller scale). Though as a user I would say Kong had taken a bad turn, as a dev I'm still grateful to them for open-sourcing such a fantastic product.
One of the reasons I forked Insomnia was because it uses React & Electron, both of which I'm quite familiar with. And I think many parts of Insomnia are quite nicely written overall (but unfortunately things like nedb that was used is no longer maintained https://github.com/louischatriot/nedb so it's probably wise to swap out at some point)
I think their model is acceptable and sustainable. It's MIT licensed, and they make money on the self-hosted enterprise edition that gives you SSO, permissions, audits, etc.
Recently switched to it after going through most of the alternatives, because it has a clean UX, works on every OS without install, and has all of the features I need.
I'm gonna be a cynic here. Maybe they have a sustainable model _now_, but there is no telling for how long the VCs will be happy with the revenue this model generates.
Somewhere down the line they might want to see a better ROI that involves converting Hoppscotch to a cloud-only app just like Postman and Insomnia
I still think Kong did a good job in crafting the product. I started using Insomnia in my previous company 3 years ago and our team loved it.
What happened recently felt a little bit like the Unity fiasco (of course, in a much much smaller scale). Though as a user I would say Kong had taken a bad turn, as a dev I'm still grateful to them for open-sourcing such a fantastic product.
One of the reasons I forked Insomnia was because it uses React & Electron, both of which I'm quite familiar with. And I think many parts of Insomnia are quite nicely written overall (but unfortunately things like nedb that was used is no longer maintained https://github.com/louischatriot/nedb so it's probably wise to swap out at some point)