What is POSTMAN? How to use POSTMAN? Case Study of Indian Startup Postman!! Growing globally.

#postmangalaxy #Postmanbusinessstrategies #businessstrategies #businessstartup
As Postman recently passed 15 million developers on the Postman API Platform and 50 million active Postman Collections-two milestones I would never have dreamed possible even a few years ago-I’m often asked how we got here. To answer that question, here’s the official (brief) history of Postman.
First there was a problem, and then there was an idea
In 2012, I was a coding intern at Yahoo Bangalore along with Postman future co-founder Ankit Sobti. Our job was to take APIs and convert them into a shareable format that developers could use in their projects.
Launching Postman v1 on Chrome
That’s when I had an idea to write an early version of Postman as a basic HTTP client for Chrome. It solved my own problem, and then some of my co-workers wanted to use it too. After some iterating, I put it up on the Chrome Web Store where it really started to take off. Google reached out to tell us how much they liked the Postman tool, and at one point soon thereafter, they even featured us on the home page of the Chrome store, which gave us fantastic visibility. As a result, the feedback poured in from developers every week, including some high-profile evangelists (a few of our earliest supporters have since become engineers at Postman). We also started getting serious inquiries from investors. The rapid adoption of our new tool got me thinking about the size of this problem-everyone from small startups to big companies must certainly be facing these same challenges with their APIs. This, I figured, was basically a worldwide problem, not just limited to the Indian development community. Soon, Postman had nearly half a million users-which seemed absolutely incredible at the time-and we had reached an inflection point. Clearly we had more than just a fun side project; this was a real business opportunity.
Collaborating with our early customers
As the three of us got underway with taking this tool to the next level, we agreed on a central principle. Above all else, we would fully listen to our users and focus on gathering feedback.
Loads of feedback is great
Making data-driven decisions every step of the way
At this point, we had a good product, and we had enthusiastic users. But we knew that these alone would not necessarily lead to success. Data was the critical, unblinking eye that could reveal how people were using Postman. What was working, and what wasn’t? What were the patterns that could show us where we needed to focus our attention?
We wanted to avoid the pitfall of many startups who ignore data until late in the game when it’s hard-expensive, time-consuming, and discouraging-to change the course of the product and business. Therefore, we made sure to invest in our own infrastructure early to help us leverage data in all our decisions. This included not only decisions during product development, but also decisions related to hiring, fundraising, and other areas
Keeping it simple as we grew
As our business grew, we moved away from Chrome and built a full-featured platform in PHP running on Linode servers. (Interestingly enough, one of the things that pushed us to move away from the web to an app at this time were the challenges of using cross-origin resource sharing [CORS]. In the early days of Postman, these challenges with CORS while working with APIs in the browser quickly pushed Postman from the web to the desktop, resulting in the Windows and Mac versions of the Postman app that many developers depend on today. But in 2020, we came full circle back to the web, and I’ll discuss that more below.Anyway, once the business started to scale even further, we took the next step and moved to AWS and hired a dedicated team to manage our infrastructure. We did this at a time when we knew we were ready to invest in a more powerful tech stack and take advantage of the robust capabilities of AWS.
Expanding our understanding of product-market fit
As part of our user-centric efforts, we were also looking for larger trends in our data to see what the true market fit and opportunities were for Postman. One thing we noticed was that a lot of non-developers were using our platform. That didn’t fit our original hypothesis at all, and we started looking more closely at other types of users. Although Postman is a developer-first product, it was useful to a much wider range of use cases, such as for sales, customer support, training, and other non-technical roles.
Growing the Postman community
I’ve always believed that communities don’t form around products, they form around unifying ideas, and the product should reflect those ideas. Over the past eight years, APIs have become essential to modern software development, and engineers are looking for tools like Postman that make it easier to work with APIs.

[@suraj9669]

Really well explained

[@reemakhan6444]

*well explained mam*

[@CAMeenaVermaSCM]

Thank you 🙇