Video is becoming increasingly important to a growing number of businesses. Whether it’s an internally produced video showing off your wares or the integration of customer videos in the context of social networking, video has become a key business tool. YouTube has become pretty much synonymous with video, and YouTube APIs let you bring the YouTube experience to your webpage, application or device. In this post, we will explore how to perform queries on videos stored on the video-hosting website and retrieve feeds according to different criteria.
Online shopping is easy, fast and convenient, but sometimes only the brick-and-mortar experience will do—like when you need modeling clay for your child’s science project due … tomorrow! Luckily, our mobile devices can still serve us well in the physical world, helping us compare prices and find inventory at the closest store.
The Web is based on a rather simple notion: There are Web servers and there are clients, such as browsers. It’s an asymmetric kind of a connection: Clients connect to servers to request stuff. This breaks when what we need is more interactivity–for example, when our online webmail service notifies us of a new email, an update to a stock tick or news item, or the ring of our virtual phone. To achieve that, we hack our way with things like XHR, SSE and, recently, WebSockets.
Almost 12 years ago, Roy Fielding introduced Representational State Transfer (REST) in his dissertation on Architectural Styles and the Design of Network-based Software Architectures. Since then, APIs adopting the REST architectural style (so-called “RESTful” APIs) have gradually increased in popularity. Nonetheless, a key constraint that Fielding proposed has yet to be adopted as a mainstream feature of RESTful APIs. This feature is known as Hypermedia as the Engine of Application State, or HATEOAS. APIs that enforce this constraint are referred to as HATEOAS-compliant APIs. More generally, APIs that adopt the characteristics of HATEOAS are called “Hypermedia APIs.”
Email is one of the oldest mediums of communication on the Internet, and, for many companies, it’s still one of the most important. Delivering email and tracking email campaigns reliably is crucial to success for countless businesses today.
Developing complex, interactive web applications can be a significant undertaking fraught with potential pitfalls and challenges. Fortunately, developers have a significant number of tools to help them avoid many pitfalls and address common challenges. From robust IDEs and web application frameworks to unit testing libraries and continuous integration software, just about every step of the development lifecycle is covered.
Twitter for Websites enables you to integrate individual tweets and timelines right in your website or application. These tweets and timelines can display media, including photos, videos and article summaries. They are also fully interactive, allowing your readers to interact with them just as they would on Twitter.com.
The explosive growth of social media, cloud computing and mobile devices is making Web APIs the primary interface for technology-driven products and services, and placing more and more attention on the emerging “API economy.” And with 50 percent of B2B collaboration predicted to take place through APIs by 2016, we are only seeing the tip of the iceberg.
Sustaining an effective engagement campaign can take a surprising amount of work. You could limit yourself to following the leads from the data you collect, but following without interacting first will get you a very low follow-back ratio. More importantly, if you follow and then forget people, they may follow back, but they’ll soon forget you. A high number of followers who don’t reply to, mention or retweet your account are of no value. True engagement is long-term and repetitive.