The API client maintains a history of API calls so you can go back to the requests you use often. It supports HTTP as well as our newest UIs for GraphQL, gRPC, and WebSocket. In place of the Scratch Pad, we are excited to launch a brand-new lightweight API client that is designed for single users who just want to make quick API calls through the Postman UI. Starting May 15, 2023, Scratch Pad mode will no longer be available in the latest version of the Postman app for new downloads. With our recently introduced capabilities-like public workspaces and universal search, Postman Live Collections (March 15), Postman Flows (March 22), and now Postbot and soon-to-be-released autosave-we’ve realized that it is now time to announce the end for offline capabilities built with the Scratch Pad mode. Building these new clients and allowing for a full-lifecycle workflow through collections in two separate architectures was increasingly just not feasible. In some cases, with feature requests like autosaving requests, the technical implications are even bigger.Īs we added support for new protocols like GraphQL, gRPC, and WebSockets, this problem became harder. However, maintaining two separate architectures-one with the Scratch Pad and the other with workspaces-for the same set of features has meant that we spend 2x-4x the amount of time in developing or improving the product. So far, we have continued to maintain offline collections through the Scratch Pad and collections through cloud-powered workspaces. Thousands of companies buy Postman for our team-collaboration features as well as our Enterprise capabilities-all powered by the cloud. the capabilities we provide locally.Įvery month, there are hundreds of thousands of users who sign up with an account on Postman and enjoy the full set of capabilities that we offer. The second problem we saw with the evolution of Postman was the split between the capabilities we provide as part of our cloud-based services vs. I wrote about how our users and customers find value in my earlier blog post. So, last month, we launched a simplified baseline workspace experience in response to feedback we heard from a section of our users who just want a simple API client. However, as we added more capabilities to the Postman API Platform, we saw that the Postman UI became confusing for beginners. Developers love the simplicity of the API client over writing code or making curl calls. Postman started as a tiny Chrome extension to send API calls. Postman is also evolving to keep pace with these trends, and we’re continuously working to power the next generation of capabilities for our products. More recently, generative AI is rapidly becoming the next evolutionary leap in the interaction between computing and humans. As a result, the flexibility and elasticity of SaaS software with low-maintenance cost is the preferred way for businesses to buy applications. Today, cloud technology is the norm for small and large organizations to deploy software. I’d pay per major version or do the IntelliJ perpetual fallback if it came to it, but I’ve never once been bait and switched (looking at you Tower2).The world has changed dramatically in the last decade. I paid them $50, probably 6 years ago now, and have never been forced to pay them another dime. I forgot to mention their license is still a lifetime license. A great combination of simple just get out of the way and advanced automation strategies. The Teams version, which requires a monthly sub kinda/sorta mimics a git style branch strategy for merging different members changes and handles the team problem pretty well.Īll in all though, it is absolutely and BY FAR the best request tool I’ve ever used. paw file is binary and doesn’t do well checked into source control if you’ve got more than one person using it. This could very well be my lack of knowledge, though I feel like I know the tool well. Each request requires the auth config, but this is solved by just copying an existing request and starting from that. I still can’t figure out how to make it “use the same auth scheme” for every single request globally. I’ve only got really a couple of nits with the stand-alone version. Most importantly, it just works, and it works well and quickly, with pretty much any auth scheme I’ve ever had to deal with. You can extract values from one response body to use as a variable in another request, the built in features go on and on- and there’s a decent extension ecosystem/write your own. It can generate code snippets and cURL requests. It can consume swagger/openapi docs and generate calls. I’ve been using it for a long time and I’d happily pay $100 for it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |