Making API Experience a Project Priority WRIT TEN BY: DANNY BAGGETT,
LEAD ENGINEER, BOTTLE ROCKET
In a past article, we gave a best practices breakdown
on
flipping
API
development
upside down for top-down development with quality API design that delivers functionality consumers
truly
need.
We
believe
API-
fueled mobile and web applications are a representation of the underlying APIs, so it’s critical to get the design right from the onset.
API Gateways in general act as a proxy between consumers
(mobile
or
web
applications)
However, not all projects can justify completely
and upstream APIs. Users of API Gateway
overhauling APIs just to go top-down for a
products oftentimes have pre-built or custom
change. In fact, many projects start off in pretty
policies at their disposal which can augment
good shape where the underlying enablement
the underlying APIs to create something that
APIs are performing just fine and providing all
may appear much different and hopefully
the key functionality that the mobile or web
richer. One such API Gateway is Azure’s
experience needs. You don’t have to reinvent
API Management product which we used
the wheel or implement some unnecessary
recently for a client’s native Android and iOS
abstraction API to start thinking about the
applications.
experience given to your consumers.
78
An API Gateway is a great way to start adopting the experience mindset in APIs without doing a full rebuild.
