Hoppscotch π½
Feel free to contribute on GitHub π
In case you missed it!
Story this far: I joined Zartek, which is a start-up based in Kochi, Kerala where I work as a full-stack developer.
The story behind Hoppscotch: The very first task I was assigned is an API integration of an old project. That's when I came across Postman API testing tool. Postman has separate builds targeted to each operating system made with Electron. I use a low-end PC and can't possibly afford to run another Electron app. From that moment onwards, I wanted to make an API testing platform which is:
- Open Sourced π
- Runs online
- Have multi-platform support
- Have multi-device support
- Accessible from anywhere
That's how Hoppscotch was born (this is not at all an alternative to Postman - yet, it does the job very beautifully and minimally. It needs more features and love which I hope we all can give by contributing on GitHub).
When I did a background check on API request builders, Postman offered various Plans & Pricing, there were a lot of other API request builders based on cURL, etc. But none of them seems simple, minimal, and efficient.
That's why I created my own API request builder with pure JavaScript (I used Vue.js) + HTML + CSS π
Did I mention this service is all free of charge and 100% open source? Yes, It's free and always will be.
The Hoppscotch API request builder helps you create your requests faster, saving precious time on your development.
Features π₯
- Send requests to verify your API is ready for launch GET, PUT, POST, DELETE, OPTIONS (more coming soon)
- Authentication support
- Parameters support
- Request body support
- View Response
- Progressive Web App support
- UPDATE: Added History support
- (more coming soon)
Features planned for near future for which I need your help.
- Autocomplete
- Code highlight in response body
- More methods
- ~History~ UPDATE: Added History support
π Bonus: Hoppscotch is in dark mode π
Top comments (236)
Did you know Postman has raised 58 million in venture funding? That shocked me when I found out. I always assumed it was more indy.
Perhaps this project is something you could turn into a business?
Anyway, I just sent you a Paypal donation. Keep up the great work!
Really? Someone should show these VCs
curlorwgetorab- it'll blow their minds...First things first: A huge thanks for dev.to You guys are the best π
A huge thanks for the donation. This means so much to me. You'll shine β¨
I took your advice to my heart, will work on it.
My DMs are open and I'm happy to provide more help along the way.
respect
Love the name!
Why should boys have all the fun! π
Never thought of gender when I said postman. Also didn't know postman could only be used by males. (sarcasm aside) I think a unique name would make the service stand out more instead of making a statement.
I don't want to gender-ify this service. I believe a name doesn't have that much influence on determining its scope or sucess. If you would like to suggest an alternative name, go on. I'm all hears.
I would be mildly annoyed if someone complain about postMAN, is the same with postWOMAN so keep the name, keep the good work; and if someone complains, who cares, in the web always someone is offended by something. After years in classrooms with almost 1% females still makes me happy to be able to talk nerdy and to a girl at the same time. (without sighs and eye rolls that is)
This is gold β¨
Let's not make it into a gender thing ... The only reason I would probably have gone with a different name is to avoid potential legal issues. It's directly derived from the same name as the product you took the original idea from. They might not be happy as commercial product with - I say in their eyes - a clone with a similar name trying to take away their business... That Alone is way more risky than the potential gender discussion the name might be calling for
I look forward to lawyers trying to claim copyright over making an HTTP request in the browser...
Rename to Postie? Or even Getperson... π
Let's see what future brings
I love the name Postwoman, it's awesome and really caught my attention.
That's exactly what I had in mind. Let it help you on your development period.
Me as an occasional user it's guaranteed i'll remember Postwoman. I don't like Postman because is using the gpu of my mac. But i'm wondering what are the limits, i know Postman is not web based because of some limitations.
Same here brother!
Tuppence time: I think it's a cute pun, and works well as an homage. Plus it opens the door wide for a vast array of inappropriate puns and silly jokes about Postman and Postwoman.
Like, what if there's an acquisition offer? The Register would (will?) have a field day.
And I'll just leave this here:
Only downside I can see is there might be some faffing around over copyright or people who take themselves too seriously taking the name too seriously. E.g. be prepared for the suggestions of "postwomyn" and whatnot.
NuxtJS, NextJS, NestJS.
Just saying.
I think the names are not antagonist each other, and as I understood wasn't a "political statement" I believe was more a "cachi" name, at the end, I think in the real word postman and now postwoman will complement each other in the dev world, as should be with everything
I love positive people like you.
But you've just did...
Entire companies have been born for sole purpose of inventing product branding, which includes creating an appealing name.
For many people "postwoman" is just a swing in likes of "take that, MEN" which i find, how millenials are caling it, problematic.
P.s. I believe "man" in "postman" stands for "person", not as "male"
Thanks for sharing your thoughts on this.
I foresee a name change in your near future. If Postman has received significant venture capital then theyβre obliged to protect their brand. And they could have chosen a gender neutral name like Postie so weβll done for calling them out on their name, even if not deliberate. I habit been aware that Postman uses Electron - good to know, thank you.
I don't think there's a problem with this name.
Thanks for giving us all your perspective.
great
I get the name but be the bigger person, this should be post person π
In comparison to postman, I think the idea is to be the smaller one π
No clue if that was intentional, but it definitely works lol
Minimalism and keeping things simple has been one of my prior concern.
That should be the SOAP version, why should rest APIs get all the love
I confess I have not really looked into SOAP at all... I must stink.
No lye.
π£ dad joke quality puns π€£
SOAP == π€’
ππ
Why not just change the HTTP verb?
Great
While I applaud the effort, this can't be more than just a toy until it drops browser sandbox like Postman or Insomnia did. You can't deal with CORS, browser hides cookies from you, applies HSTS and other cross-origin restrictions. Good luck!
Thanks for your concern, consider making a contribution or suggestions to make Postwoman better β€οΈ
Now hold your unicors, there, how sure are you that those restrictions aren't features?
So build a client that doesn't rely on Electron.
That's was my primary aim, but as you've noticed project Postwoman had gained momentum in GitHub and we rewrote a-z into Vue Nuxt which made it faster, lighter and efficient than any other projects in its category.
Oru kind supporters brought domains postwoman.net and postwoman.io which are currently serving GitHub pages directly and will be published to the world for free on Postwoman v1.0 stable release. We need support from guys like you for the next big thing to happen. Postwoman will be a fully transparent open source project, free of cost for all.
This is pretty cool. I like the name a lot. I'm going to be diving more into the source code, and hopefully, I'll find some time to contribute.
Also, do you only intend to keep this super minimal or looking to add some few "minimal" bells and whistles in the future?
I'm always open to suggestions. Everyone's opinion counts. Feel free to contribute and share your thoughts on improving Postwoman.
You only changed half the name. What about the first part? We don't only use it for POST. We also use it for GET and PUT (and more). Getwoman sounds too out of place. So I would suggest Putwoman. That gets you out of trouble with the the Postman people.
Renaming the platform is currently scheduled for future. After stable release. Anyway suggestions are welcomed.
i sure will, maybe you should submit this app to Product hunt to get more eyes on it.
Actually, I made a post on Product Hunt. Share some love π₯β¨
Lol I did too. Should I take mine down?
I hope you gave proper credit for me, and didn't changed any contents.
I love this! Here's a quick thought, I didn't research this but what are implications of having server side to proxy a http request? Like a free tier on zeit.co where a requests can be handled by a lambda function and results are sent back to the client side. Full disclaimer, I googled once and got this idea so it's not something I'm proud of.
Umm yeah, a proxy system is something this site might need at some point. As the client side CORS policies kinda break the app (just try sending a request to google.com).
There is an active discussion going on here.
I am really loving contributing to this project.
Will surely consider your advice. Stay tuned for future updates π±βπ»
Hi there!
Just a side question:
what driving factors made you chose Vue instead of other front end frameworks?
I ask this because Postwoman seems promising and getting traction, so that it's interesting to learn about the tech choices behind it.
Thanks in advance!
P.S. "Postwoman" is really a funny and well thought name imho
Actually, this is my first Vue project. I wanted to learn Vue. And "learn by doing a project" is my way of learning. That why I choose Vue.
** The initial prototype was built in a night. And I didnt had a second thought on naming.
Star and contribute to the project on GitHub π
UPDATE: Added History support with session storage π
UPDATE: Added URL validation π
Huge thanks to all the contributors π€
i will be glad to help in any way possible
@liyasthomas I know I'm getting to this a bit late but I have to commend you, this is awesome work and I love the name. I'm not a lawyer but I don't think you need to be too worried about any potential legal issues if this is a FOSS project and the name falls under "satire" :D
Anyway, I love that you're using Nuxt.js...curious whether you have a back-end at all, and whether I can DM you? You of all people seem to know how to implement the Authorization grant token (oauth flow using Nuxt for social login) and I'd love to pick your brain on this.
I would love have a conversation with you. You can DM me here or I'm available on Twitter @liyasthomas.
Glad you liked the project. Thanks for your suggestions on legal issues. Later, I came to know that there are thousands of projects which even sounds similar and does pretty much the same thing.
Currently, we don't have a backend at all. I made it fully transparent, we don't even do analytics, logging or accept any user/client informations. I believe in "free for all" philosophy. Currently we're focusing on its growth. Adding essential features such as workspace sharing, auth, collections etc and encouraging people to use it. Making it popular or should I say, letting people know that there exists a service that has everything for API testing and its free and open source.
I believe your contributions to the project on GitHub will be an asset for us. Please consider contributing and share the love with a text, tweet or talk. Looking forward for your response.
Thanks @liyasthomas . I just starred the project on Github...amazing that you're focused on it's growth above all else. I will definitely be using postwoman and report any issues / improvements I find.
Right now I'm focused on a problem dealing with Auth in Nuxt (Social oAuth using the Authorization Grant token, to be specific). Is this something you would know about and can help point me in the right direction on? My DMs on DEV are also open if that's easier...do you want to follow me back / send a message so we can connect and talk further?