[GH-ISSUE #69] Comparison with Postman is missing #30

New issue

Closed

opened 2026-03-16 12:51:50 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 12:51:50 +03:00

Owner

Originally created by @nskazki on GitHub (Aug 27, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/69

Originally assigned to: @liyasthomas on GitHub.

A comparison with the obvious competitor is must-have for this repository, especially taking into account that you're referencing to it in the name of your app :)

Originally created by @nskazki on GitHub (Aug 27, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/69 Originally assigned to: @liyasthomas on GitHub. A comparison with the obvious competitor is must-have for this repository, especially taking into account that you're referencing to it in the name of your app :)

kerem

2026-03-16 12:51:50 +03:00

closed this issue
added the
documentation
label

kerem commented

2026-03-16 12:52:06 +03:00

Author

Owner

@liyasthomas commented on GitHub (Aug 27, 2019):

Let me make this clear once and for all.

The reason why Postwoman has born is because my 7 year old PC won't run Postman. I asked my friends who've used Postman and they made it clear that it had high CPU usage, high RAM consumption and had annoying popups. It used to take 7-30 seconds to initiate the app. It has even crashed some systems. I won't wonder because I've prior experience in developing and using Electron apps and had same situations by myself.

But at the end of the day, I had to test my APIs. That's why I made Postwoman. I don't see Postman as a competitor since Postman is a totally different kind of product. Even though both does the same thing, the implementations are totally different.

Postwoman is a PWA. It's lightweight, faster, efficient and runs on any platform, any device, along with other tones of features. Moreover it's an open sourced, fully transparent, free service. Unlike Postman, there are several things only Postwoman can do. Developers can suggest, contribute and make things better in Postwoman.

(I'll be updating this thread later with links, proofs and testimonials from real users of both apps)

All are welcome to share their thoughts on Postwoman on this thread

@liyasthomas commented on GitHub (Aug 27, 2019): Let me make this clear once and for all. The reason why Postwoman has born is because my 7 year old PC won't run Postman. I asked my friends who've used Postman and they made it clear that it had [high CPU usage, high RAM consumption](https://www.google.com/search?q=postman+high+cpu+usage) and had annoying popups. It used to take 7-30 seconds to initiate the app. It has even crashed some systems. I won't wonder because I've prior experience in developing and using Electron apps and had same situations by myself. But at the end of the day, I had to test my APIs. That's why I made Postwoman. I don't see Postman as a competitor since Postman is a totally different kind of product. Even though both does the same thing, the implementations are totally different. Postwoman is a [PWA](https://developers.google.com/web/progressive-web-apps). It's lightweight, faster, efficient and runs on any platform, any device, along with other tones of features. Moreover it's an open sourced, fully transparent, free service. Unlike Postman, there are several things only Postwoman can do. Developers can suggest, contribute and make things better in Postwoman. (I'll be updating this thread later with links, proofs and testimonials from real users of both apps) All are welcome to share their thoughts on Postwoman on this thread

kerem commented

2026-03-16 12:52:11 +03:00

Author

Owner

@NBTX commented on GitHub (Aug 27, 2019):

@liyasthomas Perhaps it is worth adding that to the README?
(I mean what you just said, not a comparison with Postman)

@NBTX commented on GitHub (Aug 27, 2019): @liyasthomas Perhaps it is worth adding that to the README? (I mean what you just said, not a comparison with Postman)

kerem referenced this issue

2026-03-17 00:05:14 +03:00

[PR #34] [CLOSED] Copy Response Button #2378