|
As the founder of Paw, I'm certainly biased, so I'll stick to the facts. Paw has "dynamic values" which lets you inline computed components in any field of your request: useful for pointing to values from other requests, previous responses (parsing is done on the fly, no need to refresh), which is useful if you want to send back an auth token returned by a previous request. Dynamic values can do also stuff like MD5/SHA hashes, HMAC, URL/hex/base64 encode, timestamps, randomizers (Chance.js, JSON schema faker) with no code required (you can write custom JS snippets too if ever needed). For example, we once demo'ed the Algolia guys that their custom HMAC-based signature for client-side search was doable with no code. So, if you have the need, you can do custom stuff easily. Also, extensions (many are built by users) are bringing lots of extra features we would have not thought about ourselves: https://paw.cloud/extensions/ Environment variables in Paw can be nested or computed (with "dynamic values" described above). It can be useful, for example, to have an "Auth" variable that contains a pointer that accesses the "user.access_token" JSON path from inside the latest Login request, so you can later simply point to the "Auth" variable everywhere else. One other thing about envs, is that you can have independent groups of environments: a typical example is you have a "Server" group with envs called "Prod", "Staging", "Local" and independently a setup with user credentials or variables that are more like static globals (AWS Keys, etc.)… Now regarding to the team syncing service, "Paw for Teams". It has branches, snapshots and full history. In a dev team, it means one dev can experiment stuff on the schema for API v2 while others are fixing bugs on API v1, and when API v2 is ready they can seamlessly merge the new updates back to the v1 branch. Also, we've made the choice not to be real-time synced, because it doesn't fit well to software development: when I'm experimenting stuff with an API I don't want others to be polluted by my temporary garbage. So instead you "commit" changes only when ready. More about Teams here: https://paw.cloud/teams Last but not least, Paw locally encrypts with a randomly generated symmetric passphrase all credentials you enter in your projects, that means your server keys, access tokens, etc. are a lot safer. And now that you can (optionally) sync with Paw's backend, we certainly don't want to have your secrets in cleartext on our infra. As passphrases are never uploaded (obviously! but by default stored in OS X Keychain), it's the users responsibility to safeguard them and share them with their team (on 1Password or similar). |
I find dynamic value really useful, but in most of my use, it's dynamic integer values that I need, and so the feature is much less useful than it could be. Could you please comment on when you plan on implementing dynamic integer values into Paw?
Also, it appears that you have changed which versions of OS X you support, but I had to overwrite my old version of Paw with the new one to find this out. I strongly suggest making it clear which version of OS X the new version of Paw requires before someone installs it.