WebMatrix jQuery Mobile Web

Keynote covering what Progressive Web Apps mean to the market and what issues of native apps they need to fix.

1. The document discusses the rise of HTML5 and its adoption in China, noting that older versions of Internet Explorer still dominate the market but that HTML5 support is improving in newer browsers. 2. It provides statistics on browser support for HTML5 features from the HTML5 Test website and global browser usage statistics, showing Internet Explorer 6-8 make up over 80% of the Chinese market. 3. The document advocates for progressive enhancement approaches to support older browsers while taking advantage of new HTML5 features in modern browsers to provide richer experiences.

The document discusses how to recreate native mobile controls like those found in apps using jQuery, CSS, and HTML5. It provides examples of recreating controls from Windows Phone 7 like the Panorama and Jump List controls as well as a slide menu and scroll view control. Resources on mobile web development and specifications are also referenced.

Using a Joostrap template, Philip will be explaining & demoing how you wire frame a website right in your browser and why it will save you load's of time. There are no fancy plugins here! This is wire framing for your client, built directly in your browser & saving you untold hours messing around in other software. It is so hard sometimes, trying to get across to a client with a few drawings how the functionality of something could work. Wire framing directly in the browser gives your client a working wireframe/prototype where they can interact with links, pages & concepts. Not only that, but after client approval, you just have to style your working wireframe/prototype or switch to the template that is using the same module positions... It's a win win situation!

The document discusses the evolution of the web from progressive web apps to native mobile apps and back again to progressive web apps. It notes that early mobile web faced issues like small screens, poor connectivity and unreliable browsers, leading to the rise of native apps. However, app distribution issues like slow updates and the "walled garden" approach of app stores have led to a renewed interest in progressive web apps that work offline but do not require app stores, allowing for more open distribution like the original web.

The document discusses the challenges facing the progressive web and introduces progressive web apps (PWAs) as a solution. PWAs are built using modern web standards to provide native app-like experiences through features like push notifications, offline support, and app installation. They address issues with native apps like high installation friction, lack of control for publishers, and app store policies. PWAs are gaining adoption from companies like Alibaba and Housing.com who saw increases in user engagement metrics after implementing PWAs. The document outlines the core components of PWAs and provides an overview of browser and platform support.

1) The document discusses how to make web applications accessible to users with JavaScript disabled or who are using older browsers or mobile devices. 2) It recommends coding the basic page structure for the "lowest common denominator" and then using DOM scripting and JavaScript libraries to enhance the experience for newer browsers and devices. 3) The document provides tips on understanding your audience, adding accessibility features like links to turn off advanced options, and using techniques like yellow highlighting to help low-sighted users follow changes to the page.

Slides from my recent presentation on Progressive web apps. I showed what they are and how I believe they are the future of web/app development. I also demonstrated how to use de F12 tools in Chrome to debug the Service Worker and the Manifest.json file. I also demonstrated how, by adding and changing a few lines, a Node.js app is converted to a progressive web app.

This document provides information about the mobile-friendly features of the Collaborative Learning Annotation System (CLAS). Key points include: - CLAS now has a shorter, mobile-friendly URL structure of clas.arts.ubc.ca/name - The interface, course welcome page, and login pages are optimized for mobile usage - Users can easily record, upload, view, annotate and comment on videos from their mobile devices - Recording directly through CLAS is limited to 10 minutes on iOS devices but longer videos can be uploaded from the device camera roll - The system is supported on Safari, Chrome and IE across iPhone, iPad, Android and Windows tablets and phones.

Caridy Patiño presented on the challenges of building mobile HTML5 applications. Some key challenges include browser fragmentation across devices, network failures, and the need to optimize applications for different runtime environments and adapt them for varying screen sizes and features. Patiño advocated writing applications using a single language, JavaScript, and customizing output per runtime and context while adapting the UI per form factor and feature detection. The goal is to build flexible applications that can run on multiple platforms.

The document discusses the current state of web development and identifies several issues, including slow page loading times, large file sizes, reliance on outdated libraries and browser hacks, and an emphasis on flashy innovations over foundational web standards. It argues that as an industry, web development has gotten too complex and focuses too much on impressing other developers rather than meeting users' needs. It calls for simplifying solutions, supporting baseline functionality for all browsers, and prioritizing education and collaboration over quick fixes.

What do we mean when we talk about "web performance"? Why should you care about it? How can measure it? How do you get other people in your organization to care? In this workshop at the 2021 Chrome Dev Summit, I covered these questions – including an overview of the history of performance metrics, up to Core Web Vitals.