FlowDiscuss Integrates Various APIs for Powerful Content Aggregation

Most developers these days are aware of the benefits of using APIs to build web and mobile applications; APIs allow developers to quickly build applications that are feature packed, aggregate data from multiple sources, provide users engaging app experiences, and much more.

This article takes a detailed look at FlowDiscuss, a web app built with a variety of APIs that allow the app to automatically aggregate content data from multiple sources. We reached out to the developer and creator of FlowDiscuss, who provided ProgrammableWeb most of the information included in this article.

flowdiscuss

Screenshot of the FlowDiscuss app displayed on a desktop computer.

FlowDiscuss is a content aggregator that focuses specifically on television programs and internet streaming media. The application gathers episode information from a variety of sources then combines the content so that it can be displayed on a single web page. Every piece of information within a page is analyzed to automatically hide any videos, reviews, podcasts, memes, etc. that would be targeted to a different episode. The app also analyzes the titles as well as the time they were uploaded to the web.

The content that is displayed when a user first views an episode page depends on whether or not they have watched that specific episode. For example, someone that has not watched an episode will most likely be interested in trailers and how to stream it. On the other hand, someone that has already watched an episode will most likely be interested in reviews and behind the scene videos. The FlowDiscuss web app is fairly new (it was launched in November 2014) and has a modest amount of traffic, most of which are returning users.

The developer and creator of FlowDiscuss explained to ProgrammableWeb the reasons for creating the FlowDiscuss web app.

"I watch most of my shows using Netflix and really enjoy reading comments, watching reviews, and trying to get feedback from other viewers about the episode that I just watched, right after I watched it. The problem is that if you are a few seasons late on a show, search engines are really bad about not displaying spoilers; the search results will spoil you with a big revelation, will display spoiling images, etc."

"Even worse, dedicated TV websites always tailor their series portal to display the latest information about a given show. For shows that are really heavy and have potentially devastating spoilers (like a beloved character dying on Game of Thrones), it is impossible to open a web page without taking the risk of learning something we did not want to. Even seeing a character within the cast of season 3, tells you that he will be just fine for the first two seasons!"

Web vs Mobile

flowdiscuss

Screenshots of the FlowDiscuss app displayed on an Android smartphone.

Building a web app allows for better integration into different devices. As a web app, FlowDiscuss is available on all ecosystems and looks great on mobile too. FlowDiscuss was built with Twitter Bootstrap and AngularJS frameworks, jQuery JavaScript library, Google App Engine, and other software.

Be sure to read the next Application Development article: How API Description Languages Enable API IDEs

 

Comments (0)