This course guides you through the long and winding road of building web frontends that can be comfortably displayed and enjoyed on a variety of devices. The course lists core issues you must be ready to face and explores a range of solutions at different levels of cost and effort.
Gone are the days when one could write a site for a single family of devices — mostly desktop browsers. Today, desktop browsers are just one type of device to be concerned about. A multi-device website is critical for any type and size of business. Even more critical for any business is avoiding poor-quality websites that don't distinguish the underlying devices, whether they be smart phones, tablets, mini-tablets, smart TVs, wearable devices, or whatever else the industry may produce. This course explores the pros and cons of Responsive Web Design - using CSS media queries - and a much more sophisticated and powerful server-side approach based on WURFL, the same technology used by Facebook and Google. Through WURFL, you can gain knowledge about the effective capabilities of the device, and can implement appropriate use-cases for different classes of mobile and legacy devices.
Author of many popular books that helped the professional growth of thousands of .NET developers, Dino serves as the CTO of Crionet and focuses on web and mobile solutions for sport events. He’s also a JetBrains technical evangelist and member of the team that manages WURFL.
The WURFL Framework Hi everybody. Dino Esposito here. Welcome back to Pluralsight and Architecting Device Driven Web Solutions. This module of the class is about WURFL and provides a comprehensive view of the framework and it's ecosystem of tools. Although it is not the only framework for server-side device detection, WURFL is probably one of the most widely used DDRs today, as a large organizations such as Facebook and even Google use it for their mobile websites. Unlike other similar frameworks, WURFL is also free for open source projects. In this module you will learn about the internal structure of the WURFL DDR and the design of the public API. You'll also learn about the supported platforms and the Cloud and on-premise services.
ASP.NET MVC and WURFL Welcome to Pluralsight. Dino Esposito here. And welcome to the fifth module of the class Architecting Device Driven Web Solutions. The present module shows how to use the WURFL framework along with ASP. NET MVC. This module is split in two major parts. In the first part I'll wrap up what it means to create an HTTP endpoint or a Web page if you like this word better, that on top of a single code base a URL can provide multiple views, intelligently adapting content to the requesting device. In the second part I'll go through a demo using ASP. NET MVC in Visual Studio 2013 and the WURFL framework. So the key points being covered in this module are display modes in ASP. NET MVC. Display modes are the built-in technical contrivance that makes it so easy to route device-specific views in ASP. NET MVC. The WURFL Nuget package is the fastest and simplest way to have the WURFL framework, the on-site framework, fully configured in your Visual Studio project. And finally, we'll go through a full demo of the WURFL on-site API and the WURFL. js API.
Packaging a WURFL-Based Solution Welcome to Pluralsight. Dino Esposito here. This is the final module of the Architecting Device Driven Web Solutions class and here I'll summarize the steps that brought the creation of the WURFL DDR, Device Description Repository, and also explain what's required to package a WURFL-based solution and its licensing terms. So the key points covered in this module are therefore licensing terms of the WURFL framework, packaging options, and also a closer look at the WURFL Cloud API, an aspect segment of the WURFL ecosystem that we touched on several times during the past modules, but never expanded in any good level of detail. This is going to happen just in this final module.