Is the portal made to manage the complexity of consumably exposing a large API portfolio?
An excellent unified enterprise developer portal makes it possible to organize vast sets of integration information in a single platform portal, one that allows this enterprise to get observability across their API landscape. It is the antithesis of an uninvolved byzantine listing.
Once a company decides to fully manage and document their APIs, put emphasis on an API-first strategy, and streamline digital governance, they start looking for a developer portal that can support a unified developer experience. They might need to share certain documentation only with partners or customers, and styling needs to always be on-brand.
Especially larger organizations are invited into this nomination category, ones that need to deal with a fragmented API landscape due to organic growth, mergers and acquisitions, or any number of other reasons, and yet they've created a unified developer experience for the (external) assessment of their API integration offerings.
In this category, we are only looking to spotlight portals that were created to serve as the one unified platform for the extensive API portfolios of large and complex corporations; portals that expose their integration affordances in a way that makes it easier for users to form a mental model of an organization’s IT architecture through one comprehensive system.
Want to submit an entry?
Award Criteria
Questions to ask:
- Is the portal made to expose a complicated, a large API portfolio? Is this portfolio the result of combined enterprise units and alliances?
- Is there a smooth, unified user experience for the many integration interfaces?
- Does the portal serve the user with a semantics, are the domains clearly modelled?
- Is the portal well conceptualized and executed?
- Is it a fully operating and well designed solution for the whole enterprise?
- Is the portal supported by higher management? Is there long term maintenance and support ensured?
To allow the jurors to reasonably understand what architectural and business complexities the portal federates into one amazing end user experience, we ask that you give them a short explanation on this, as well as the short history, operational context and corporate purpose of the portal.
To relieve some of the pressure in this category, and as word of caution if you are working for such amazing results, we recommend reading an article just on the opposite.
