Using Hypermedia APIs to Drive Interactive Mobile Applications
At Comcast, the backbone of cross-platform Xfinity TV experience is a hypermedia API supporting both XHTML and HAL as media types. It's given us several expected benefits: self-documentation, loose coupling, and discoverability. At the same time, it also uncovered some limitations of hypermedia.
Hypermedia is designed so that the API works very similarly to a traditional web site—load a resource, follow a link, and then load the next resource. Modern, native mobile apps, on the other hand, try very hard to not present a page-oriented, wait and load experience. Users expect their apps to be responsive, fast, and not beholden to a page-like paradigm.
In this presentation, Benjamin will discuss the design of our hypermedia API and demonstrate some of the strategies we''ve come up with to address these concerns. We'll use different examples from our API to illustrate how we promoted parallel requests, improved cacheability, and minimized response sizes, all while staying true to the link- and form-driven spirit of hypermedia.
Ben has been writing software since he was in short pants. After obtaining his degree in Computer Engineering and beginning to wear long pants, he became an experienced full-stack web developer working with a variety of open source technologies.
After joining Comcast's Advanced Applications Engineering team, he began to focus on web and mobile backend platforms, especially APIs. As an Architect on the team, he designs and builds the systems that power the Xfinity TV apps for mobile, web, smart TVs, and media streaming devices.\nBen resides in Philadelphia with his wife, and too many cats.