We recently sat down with GraphQL co-creator Lee Byron to learn about the history and future of GraphQL. Hope you enjoy! The Origins and Future of GraphQL
Ten years ago Lee Byron was a graphics engineer designing interactive news graphics at the New York Times when a friend approached him to join a small social media startup based in San Francisco, California. Read more
Build it and they will come. That might work for ghosts and baseball fields but, sadly, it’s not true for APIs. There’s nothing worse than spending months developing an API, or any other product for that matter, only to see it flounder after launch. Read more
While most organizations have matured in developing the glue between their information and application systems via APIs, many often overlook how to deliver and expose those APIs to their respective consumers.
Reusability and adoption are the driving factors for a healthy ROI from an API, but they are harder to obtain than you may think. Read more
Adding new layers of complexity within a digital service without sacrificing user experience is a difficult endeavor. Especially for platforms that accept online payments and subscription formats, maintaining support for an increasing number of payment methods is deceptively complex.
Users don’t want to think too much about the payment process. Read more
APIs are as vast and varied as the systems that depend on them; while some systems may handle client data, payments, and collaborative research, other APIs may handle less important data such as social media and image sharing.
Due to the variations in application and usage, APIs face a unique set of considerations and issues arising from their availability that no other system faces – the difference between having an API for public consumption or one intended for internal use, in certain circumstances, can mean the difference between megalithic success and catastrophic failure. Read more