A GraphQL Primer: The Evolution Of API Design (Part 2)

January 31, 2018

In Part 1 we looked at how APIs have evolved over the last few decades and how each one gave way to the next. We also talked about some of the particular drawbacks of using REST for mobile client development. In this article, I want to look at where mobile client API design appears to be headed — with a particular emphasis on GraphQL. There are, of course, lots of people, companies, and projects that have tried to address RESTs shortcomings over the years: HAL, Swagger/OpenAPI, OData JSON API and dozens of other smaller or internal projects have all sought to bring order to the spec-less world of REST.

Previous Article
A Comprehensive Guide To Product Design
A Comprehensive Guide To Product Design

(This is a sponsored article.) What is a product? Until recently, the term was used only in relation to som...

Next Article
Styling empty cells with Generated Content and CSS Grid Layout
Styling empty cells with Generated Content and CSS Grid Layout

A common Grid Layout gotcha, is when a newcomer to the layout method wonders how to style a grid cell which...