Do you want to leverage HTML, CSS and JavaScripts APIs to deliver rich user experiences that outlive the framework du jour? Do You want to understand good front-end application architecture and performance principles. Then you want to build applications in Vanilla JS. Despite popular belief Vanilla JS is not as difficult to master and implement as you might think. In this tutorial Chris Love will demonstrate how to apply many common web performance optimization, good architecture and tricks to build a fast, native-like application user experience customers desire without dependency on large, fast food frameworks. This tutorial will demonstrate the following concepts: - Applying the 14kb Rule for Instant Loading - Markup Management - Eliminating Excess AJAX Calls - Working With and Around Application Cache - Applying Service Workers and HTTP/2 For Even Better User Experiences - Leveraging common browser APIs & good architecture
The document discusses the growing prevalence and performance issues of JavaScript-heavy websites. It argues that much of the client-side logic in JavaScript libraries can be moved to the server by sharing code between server and client. Several companies that have done this, like Twitter and Airbnb, are cited as seeing significant improvements to initial page load times and a better user experience. The document also advocates for a progressive enhancement approach to JavaScript, loading scripts intelligently based on user needs and minimizing unused code.
This document discusses HTML5 and provides an overview of its key features. It explains that HTML5 is not just the HTML language, but also includes related APIs that allow richer functionality. Some of the major areas covered include semantics and accessibility, rich internet applications using new APIs, and specific technologies like canvas, video/audio, web storage, and web workers. The document emphasizes that HTML5 is still evolving and aims to unify web development across browsers.
Client or Server Rendering Showing the newest trend of hybrid rendering polymorphic like react.js phantom.js, single page application, David Amend
The document discusses optimizing web performance for mobile devices. It covers mobile web platforms and browsers, the importance of performance on mobile, tools for measuring performance, optimizing initial loading and above-the-fold content within 1 second, and maintaining responsiveness. The key recommendations are to measure on real devices, avoid redirects, reduce requests, load above-the-fold content quickly and defer the rest, and prioritize simplicity over complex designs and frameworks.
Tips on developing self-contained JavaScript applications that can be added to a page; especially useful in content management systems
Peter Lubbers from Kaazing gave a presentation on HTML5 features such as Web Workers, Geolocation, and WebSockets. He discussed how these new technologies allow for asynchronous background processing, location detection, and bi-directional real-time communications without polling. Browser support for HTML5 features was also reviewed.
Overview of the new frontend architecture used for the New Profile at LinkedIn. Blog version of this slidedeck: https://engineering.linkedin.com/profile/engineering-new-linkedin-profile
In this talk, I would like to share how we build a system for LitiBook that can handle (1) real-time editing, (2) offline editing, (3) synchronizing between devices and (4) conflict between different editing sessions. There are not much applications out there can do all these above things. (Evernote does not resolve conflict. Hackpad, Trello and Asana do not support offline). So the challenge is really interesting.
This document discusses server and client rendering of single page applications. It outlines a wish list tool that was built to track products, receive alerts, and share lists. The goals are to improve the UI, separate the wish list into microservices, and update the frontend using modern frameworks. Shared rendering concerns between server and client are discussed, along with an architecture using Node.js, Express, Backbone, Handlebars and other technologies. Challenges with routing, data fetching, caching and other areas are covered, as well as potential solutions like React and Rendr. Overall it was found to be worthwhile but still immature, requiring better frameworks.
Presented at Web Unleashed 2017. More info at www.fitc.ca/webu Presented by Ksenija Gogic, TWG Overview What are components? How can designers apply a component-minded approach to their workflow? How can we leverage components to improve the design handoff? Ultimately – how can designers and developers work together even better? Using React as a framework, Ksenija will discuss how to design for a component-based web application to make for a more efficient workflow, an easier design handoff, and a better understanding between roles. Objective To create a common language and understanding when working with component-based web frameworks between designers and developers. Target Audience Designers and developers looking to make their collaborative workflow even better. Five Things Audience Members Will Learn How to take a component-minded approach to building a design system How to design and create components using Sketch symbols How to assemble (compose) collections of components using Sketch symbols How to work with modifiers (props) to customize components How to ensure everyone is speaking the same language
Presented at Web Unleashed 2017. More info at www.fitc.ca/webu Presented by Simon MacDonald, Adobe Overview Progressive Web Apps are the new hotness with Google pressing hard to make them the defacto choice for building mobile applications but what’s to be done about iOS where many of the key API’s are not supported. That’s where Apache Cordova/PhoneGap comes in by polyfilling the missing functionality. In this talk Simon will show you how to create a PWA that runs on the web, Android and iOS from a single code base. Take advantage of some new tools to easily deploy and test your PWA. Beginning with a brief overview of Progressive Web Apps, what features make your web app progressive and which API’s you can take advantage of, Simon will discuss the availability of these API’s on various platforms, taking care not to completely dump on Apple for falling behind. No, that’s a lie, he will jokingly take Apple to task. He will introduce Apache Cordova/PhoneGap, explaining how you can use Apache Cordova/PhoneGap to deploy a web application to Android and iOS; explaining how Cordova plugins allow us to polyfil the missing functionality on iOS. Simon will demo a PWA running on the desktop in Chrome, Android in Chrome and as a compiled hybrid app on iOS all from the same codebase. Objective To introduce developers to building progressive web apps for all platforms. Target Audience Web application developers Five Things Audience Members Will Learn What are Progressive Web Apps How to build a progressive web app The differences between PWA’s on Chrome and Safari How to use a single code base to target web, Android and iOS How to deploy a PWA on iOS as an app
Marko Heijnen discussed several ways to extend WordPress, including hooks, drop-ins, pluggable functions, and pluggable classes. He demonstrated wpcentral.io, which collects WordPress usage data, and opensesh.org, a conference platform built with Node.js. He explained how to build extensions for the future by future-proofing code and looking at new technologies like Node.js.
Slides for the session I gave at the XPages & Beer event on July 2nd, 2014. See https://github.com/markleusink/XPagesBeerAngular for the demo files.
Vector graphics allow shapes to be mathematically represented and scaled smoothly, while raster graphics use a grid of pixels. SVG is an XML format for describing vector shapes and is supported natively by modern browsers. DojoX GFX provides a normalized API for creating vector graphics across browsers using SVG, VML, Canvas, or Silverlight depending on browser support. It implements a procedural subset of SVG for creating shapes and text programmatically similar to the canvas API.
Instead of asking people which JavaScript framework to learn, let's look back into GUI application architecture (which Web Front-end is a case). Then you will understand why people created those library & frameworks and why React became so popular.
A Lecture given in Aalto University course "Design of WWW Services". Single page app is already several years old web application paradigm that is now gaining traction due to the interest towards HTML5 and particularly cross-platform mobile (web) applications. The presentation overviews the single page application paradigm and compares it with other web app paradigms. The presentation uses Backbone.js as the sample and gives practical tips on how to best structure Backbone.js applications. It contains an extensive set of tips and links in the notes section. The reader is adviced to download the presentation for better readability of the notes.
The document discusses improving mobile web performance. It notes that mobile is different than desktop due to limitations in power, memory, battery and connections on mobile devices. Sites are growing larger in size which slows performance, and users strongly prefer faster loading sites. A variety of tools can measure performance, and waterfalls charts show where time is spent loading pages between the server and client. Optimizations discussed include enabling caching, compression, image resizing, lazy loading images, inlining images and scripts where possible, minifying assets, and delivering scripts and styles in a single HTTP request through techniques like application caching.
This document discusses developing and deploying websites with HTML5. It covers creating fluid responsive layouts, single page applications, and JavaScript libraries. It also discusses build and deployment processes using GruntJS to manage source code and optimize web applications.
This is the slide deck to introduce important topics to developer to build great, high performance Single Page Web Applications. The slide deck is used to setup a review of the code and architecture in my demonstration movie web application used in my latest book. The site is live at http://movies.spawebbook.com and the source code is available on GitHub https://github.com/docluv/movies. Single page application are a new frontier to the web development world. They require a completely different mindset than classic, server-side heavy web development. Not only do developers need to understand modular JavaScript and the DOM API they also need to understand good responsive design practices, performance optimization, touch and a mobile first approach.
This is an older slide deck I realized I never uploaded. It is a slightly longer deck than the Night at the SPA deck. This features many concepts that are forerunners to the modern progressive web application. There are slides related to web performance best practices, JavaScript architecture, responsive web design, touch and much more.
Presentation on Single Page Applications I recently gave for a client. Feel free to contact Omni Resources at http://www.omniresources.com or myself on LinkedIn at https://www.linkedin.com/in/michaelacord if you would like to learn more about builiding Single Page Apps.
Web Performance tuning presentation given at http://www.chippewavalleycodecamp.com/ Covers basic http flow, measuring performance, common changes to improve performance now, and several tools and techniques you can use now.
Sai Madisetty has over 7 years of experience as a front-end UI developer. He is proficient in HTML/HTML5, CSS/CSS3, JavaScript, jQuery, AngularJS, and responsive design. Some of Sai's responsibilities include developing user interfaces, APIs, style guides, and wireframes. He has worked on projects for clients such as Nomura America Securities, JP Morgan Chase, and United Health Care. Sai also has expertise in cross-browser compatibility, accessibility, and agile methodologies.
Un breve viaje por la concepción del Desarrollo de Aplicaciones Web desde el clásico patrón de Aplicaciones Web de Servidor con renderización en servidor e interactividad limitada en cliente a la reciente era de las Single Page Applications con renderización en cliente, foco en la interactividad y desacoplamiento del backend hasta llegar a los actuales patrones híbridos de renderización en cliente y servidor en busca de la mejor performance, la mejor experiencia de usuario y el mejor SEO.