In this post I want to discuss what API first technology design means and why connected cloud of devices cannot be ignored by most businesses anymore.
This post is about how every business now-days has to export / expose valuable data publicly. And about the value well productised APIs bring to the business organization.
First, let’s take a look at the history and why APIs became critical part of most technology platforms.
Apple rediscovered the smartphone with iPhone release in 2007.
Adoption skyrocketed. Digital interactions through smart apps skyrocketed. There was no turning back.
Small screen devices rapidly became part of daily routine to billions of people around the World. Various sensors and screenless devices followed the suite (Alexa, Google Home etc.)
We now call them the Internet of things.
Below graph shows the number of smartphones and IoT devices in comparison to standard desktop computers.
What one thing all these new devices have in common?
They all rely on data APIs to be present for most of their functionality.
How it was before?
What challenges did all this rapidly growing adoption brought to the businesses and technology platforms?
Let’s take a look at the average digital business company before the smartphone revolution.
Their underlying technology looked similar to this.
Before smartphone revolution, business technology stack was mainly in house. Only sharing generated HTML content / results with the user Internet browsers.
Large, monolithic technology architectures were working just fine. Business had full control of the data inside its data centre.
There was not much segmentation on the client side technology set.
Of course, some Internet browsers were behaving better than others. But There were 3 or 4 most popular Internet browsers available.
Frameworks like jQuery where managing cross browser look & feel for us.
What exactly has changed?
With smartphones rapidly gaining consumer adoption, the way digital companies interact with their customers has suddenly changed.
In the new, smartphone powered world – mobile applications needed the business data.
Generating and sending only HTML views was not enough anymore.
Mobile applications took the control over the customer journey because smartphones became such an integral part of customers everyday life.
Businesses had to make their data publicly accessible (even if secured, encrypted etc.) for their own smartphone applications.
Customer listings, checkout flows, payment flows, notifications and other functionality was now performed outside of business controlled datacenter. On the customers smartphone.
Suddenly, existing technology stack had to securely share much more than HTML representation markup – it had to share business data as well.
And share this data for many different smartphones – the fragmentation of smartphones used by customers has grown exponentially as well.
What about APIs?
The most convenient way to expose all this data to applications was via publicly facing APIs or Application Programming Interfaces.
REST APIs became de facto technology standard for sharing underlying platform data with external 3rd party apps.
Enterprise technology stack has accumulated yet another layer – API Management.
What is API first technology design?
API first technology design comes from small screen first necessity.
Sometime around 2017, the number of consumers navigating online via smartphones has surpass the number of consumers using desktop computers.
Which means that most of business technology platforms have to focus on the small screen devices first.
Likewise, any business technology platform should be built with API first technology design mindset for business data sharing.
Otherwise it would be very challenging to fulfil customer demands to served via small-screen devices.
To sum up, API first technology design is aimed at building platforms which allow business to server customers using small screens. And allow efficient management of data sharing and integrations.