Why You Should Use an API First Design Strategy

APIs have the exciting potential to reimagine old business models, but this doesn’t mean that everyone will find your API useful. Techradar recently featured an article by MuleSoft’s Founder and VP of Product Strategy Ross Mason to get some inside tips on what API design strategies help acquire a dedicated user base. 

API features should hone in on a very specialized segment, and be designed with consistency in mind. This means making the behavior of security, URL schemes, and API keys consistent across all iterations. This will do everyone involved a favor, and will increase the efficiency of implementing new platforms or features.

Scaling for future growth needs to be considered. According to Mason, the best way to avoid unusual spikes in usage that may affect user experience is to partner with a cloud platform hosting service, where scalability is built in. Lastly, fostering a community through promotion and gathering feedback is necessary to help the API and the business evolve to meet the needs of consumers.

Original Article

When crafting your API strategy, put design first

Bill Doerrfeld I am a consultant that specializes in API economy research & content creation for developer-centric programs. I study Application Programming Interfaces (APIs) and related tech and develop content [eBooks, blogs, whitepapers, graphic design] paired with high-impact publishing strategies. I live and work in Seattle, and spend most of my time as Editor in Chief for Nordic APIs, a blog and knowledge center for API providers. For a time I was a Directory Manager & Associate Editor at ProgrammableWeb, and still add new APIs to the directory every now and then. Drop me a line at bill@doerrfeld.io. Let's connect on Twitter at @DoerrfeldBill, or follow me on LinkedIn.

Comments