API Design: Begin With the End in Mind

March 09, 2017 by Lee Robb
Topics:   SkyWise | Developers |

At WDT, we currently have around ten different APIs for accessing a variety of precision weather data. Each API was designed and built with specific use cases in mind. Why do we do that? It’s because accessibility matters a lot. You can have the most technically sound API ever developed, but if it’s not usable or worse, incomplete, you’ve wasted time and energy. You cannot build just one API and have it be right for everyone. At least not in the weather space.

Before building an API, we have to understand who the user is and why they need it. There are three different developer personas and it is important to know exactly who you are trying to reach. An API designer needs to be aware of this before they can build a product that works the right way. You can read more about my thoughts on this at the link below.

Software Quote API

API Design: Begin With the End in Mind

Whether it’s a mobile or web application, ESRI platform, or your own Common Operating Picture, SkyWise APIs' weather data is ready to work for you.

Check out SkyWise

Lee Robb

Lee is responsible for the strategy, roadmap, and feature definition of the SkyWise product line. As part of this role he leads the teams responsible for all of WDT’s SkyWise components. With vast experience building complex distributed systems and delivering solutions that delight users, Lee is considered a pivotal part of the WDT management team. He also leads WDT in establishing and executing software engineering best practices. Over the last 5 years at WDT, Lee has modernized WDT’s software development process, increasing both development velocity and quality. He has been a software engineering leader for 20 years, including shipping commercial products with millions of users.