Last week, our Layer 7 colleague Mike Amundsen insightfully blogged about the choices product managers face when creating an API for a service, and how they strive to meet the needs of their developer audience.
Mike makes the point that PMs should remember that they own the interface, and that they can cast a service in multiple ways, for different audiences. PMs shouldn’t necessarily feel trapped into a one-size-fits-all approach, nor do they have to avoid major technologies like SOAP simply because part of a given developer audience prefers one interface style over another.
By focusing on the target audience and their preferences, PMs can set up metrics that can help choose the optimal mix of API styles and accommodations that maximize API reach and usability.
Click here to read Mike’s post in its entirety: