Postman 2.0 with Sync • Hacker News Board

Re: Postman 2.0 with Sync

#11

Post by Zombieball » Mon, Mar 09, 2015, 8:22 AM UTC

rayshan wrote: post #8

Loved Postman as well, but I've switched to PAW [0] with a very polished and powerful native OS X experience. [0] https://luckymarmot.com/paw

Could you elaborate (or perhaps you already have a write up) as to why you made the change?

Just started using postman myself. This is the first I have heard of PAW.

Re: Postman 2.0 with Sync

#12

Post by nanoman » Mon, Mar 09, 2015, 8:34 AM UTC

We've been using the Sync Beta for a few months now and I can confirm this is the smoothest way to have the client/server teams working together.

We use the collections as both day-to-day development tools, as well as API documentation and a quick test layer.

Kudos to the Postman team!

Re: Postman 2.0 with Sync

#13

Post by nanoman » Mon, Mar 09, 2015, 8:36 AM UTC

rayshan wrote: post #8

Loved Postman as well, but I've switched to PAW [0] with a very polished and powerful native OS X experience. [0] https://luckymarmot.com/paw

Paw is great, full-featured and polished - but it doesn't allow collaboration in a team, what Postman Sync is all about.

Re: Postman 2.0 with Sync

#14

Post by madeofpalk » Mon, Mar 09, 2015, 11:10 AM UTC

Zombieball wrote: post #11

rayshan wrote: post #8

Loved Postman as well, but I've switched to PAW [0] with a very polished and powerful native OS X experience. [0] https://luckymarmot.com/paw

Could you elaborate (or perhaps you already have a write up) as to why you made the change? Just started using postman myself. This is the first I have heard of PAW.

It just has the level polish that's difficult to get in a HTML web app like Postman.

In terms of actual features, I can't live without 'dynamic values' - being able to copy response body values (almost like a pointer) and paste into the header of another request.

http://i.imgur.com/aY8A0NJ.png

It means that things like auth headers and 'current user ID' are always in sync and current.

Re: Postman 2.0 with Sync

#15

Post by eddieroger » Mon, Mar 09, 2015, 1:43 PM UTC

Zombieball wrote: post #11

rayshan wrote: post #8

Loved Postman as well, but I've switched to PAW [0] with a very polished and powerful native OS X experience. [0] https://luckymarmot.com/paw

Could you elaborate (or perhaps you already have a write up) as to why you made the change? Just started using postman myself. This is the first I have heard of PAW.

I ended up trying Paw when I ran in to some issues with Chrome mucking with my headers (forget the details now, but my whole team was running in to this issue a year or so ago), and haven't looked back. Paw's developer has been incredibly great at responding to emails when I had questions or needed support, and is adding great features like a plugin system. My absolute favorite feature, other than saving requests, is the ability to generate code in multiple languages, but most relevant at the time for me was AFNetworking-specific calls. It's not perfect, but saved me a lot of time when modeling new services.

Re: Postman 2.0 with Sync

#16

Post by jasonlotito » Mon, Mar 09, 2015, 2:47 PM UTC

nanoman wrote: post #13

rayshan wrote: post #8

Loved Postman as well, but I've switched to PAW [0] with a very polished and powerful native OS X experience. [0] https://luckymarmot.com/paw

Paw is great, full-featured and polished - but it doesn't allow collaboration in a team, what Postman Sync is all about.

I haven't tried sharing, but Paw saves everything to normal files, so it seems like not only can it be shared, but since it's just text, can easily be stored in something like git for easy management.

Re: Postman 2.0 with Sync

#17

Post by toomuchtodo » Wed, Mar 11, 2015, 7:45 PM UTC

jasonlotito wrote: post #16

nanoman wrote: post #13

Earlier quoted context omitted.

Paw is great, full-featured and polished - but it doesn't allow collaboration in a team, what Postman Sync is all about.

I haven't tried sharing, but Paw saves everything to normal files, so it seems like not only can it be shared, but since it's just text, can easily be stored in something like git for easy management.

Paw output files + Dropbox team folders = collaboration

Although, I would like to see the ability to share Paw data within a team. I use it daily, sharing Paw data with team members.