Leave No One Behind with HTML5 - FFWD.PRO, Croatia

Lightning talk I did at the second #JSMeetup in Paris. #Parisjs It kickstarted the project http://github.com/sylvinus/node-crawler

This document summarizes various JavaScript APIs available for building web applications. It discusses APIs for files, images, video, fullscreen, camera, WebRTC, pointer lock, web storage, IndexedDB, battery status, telephony, SMS, vibration, and more. The goal is to provide developers capabilities for building rich applications that interact with the user's device.

HTML5 is all the rage with the cool kids, and although there’s a lot of focus on the new language, there’s plenty for web app developers with new JavaScript APIs both in the HTML5 spec and separated out as their own W3C specifications. This session will take you through demos and code and show off some of the outright crazy bleeding edge demos that are being produced today using the new JavaScript APIs. But it’s not all pie in the sky – plenty is useful today, some even in Internet Explorer!

The document discusses various HTML5 APIs and their capabilities including web storage, geolocation, canvas, video, and web sockets. It provides code examples for how to use sessionStorage, localStorage, get geolocation data, draw on canvases, and open web sockets. The document is an introduction to exploring HTML5 capabilities on mobile and how no area has been untouched by new possibilities through these emerging APIs.

The document discusses developing for mobile web. It covers several topics including physical properties of mobile devices, their network usage and power constraints. It also discusses different versions of Gmail optimized for different devices. The document recommends inlining content, deferring non-essential work, and being creative with JavaScript libraries and debugging to improve performance for mobile. It highlights the ability of web technologies to build cross-device applications quickly without native restrictions. The conclusion is that native languages may be better if writing many device plugins, but web technologies can be effective otherwise.

This document discusses how to build iPhone apps using only web technologies like HTML5, CSS3, and JavaScript without relying on native iOS frameworks or the App Store. Key points covered include how to create offline-capable apps using the cache manifest, emulate touch events with JavaScript, make the app feel native through CSS transforms and meta tags, and detect device capabilities. The example rubiks cube app demonstrates these techniques to create an offline-capable puzzle game experience on iPhone similar to a native app.

This document discusses building a JavaScript widget that provides messaging functionality across different platforms and browsers. It outlines requirements such as being cross-browser compatible, supporting customization, and allowing for updates without relying on third parties. It then describes the proposed architecture, which includes abstracting the API, developing the widget component, handling customizations, and enabling updates and A/B testing through a service called FAAST. The document emphasizes testing, continuous delivery, and automation to streamline the release process.

A talk given at Node.js Cambridge about SocketStream, a realtime framework for single page apps. https://socketstream.com

jQuery is an open source JavaScript library that simplifies HTML and JavaScript interaction by providing methods for selecting elements, handling events, performing animations and AJAX calls. It has a large community of users and developers, numerous plugins that extend its functionality, and is used by many large companies and websites. Major releases of jQuery have continued to improve performance, add new features, and expand cross-browser compatibility.

This document discusses optimizing Meetup's performance by reducing page load times. It recommends reducing JavaScript, image, DOM, and CSS files. Specific techniques include externalizing and concatenating JavaScript, lazy loading images and scripts, minimizing DOM elements, writing efficient CSS selectors, and profiling code to optimize loops and DOM manipulation. Reducing page weight through these techniques can improve the user experience by speeding up load times and drop in member activity.

Presentation on how Meetup tackles web performance. Given on: - Nov 17th, 2009 for the NY Web Performance Group (http://www.meetup.com/Web-Performance-NY/) - Jan 26th, 2010 for NYC Tech Talks Meetup Group (http://www.meetup.com/NYC-Tech-Talks/)

The document discusses using Socket.io to add real-time capabilities to web applications. It provides an overview of Socket.io and how to install and use it with Node.js. Examples are given of emitting and receiving events, broadcasting to all connections, and setting up Socket.io with Express.

This document discusses JavascriptMVC, an alternative Javascript MVC framework to BackboneJS. It provides an overview of JavascriptMVC's features such as MIT licensing, clear documentation, and providing an almost total solution for building web applications. Potential pros include the licensing, documentation, and comprehensive features. Potential cons include it being less well known and having fewer online resources than BackboneJS in Taiwan. Examples of how it handles classes, CSS, data loading/validation, and views are also provided.

RSVP Node.js class at www.nycdatascience.com NYC data science academy's free workshop, given at NYC Open Data Meetup, http://www.meetup.com/NYC-Open-Data/events/163300552/

Vue.js is a JavaScript framework that provides two-way binding between DOM and JavaScript, a template language for declarative rendering, and supports installation via npm, direct download, or a script tag. It allows defining where rendering will occur, setting up data, and rendering data to the DOM. Components provide reusability through templates, logic, and styles. Additional features include routing, state management with Vuex, and use of the Vue CLI for scaffolding single file components.

jQuery is a JavaScript library that simplifies HTML and JavaScript interaction. It allows developers to select elements, perform actions on them such as adding/removing classes or triggering events, and chaining multiple actions together. jQuery supports CSS selectors, DOM manipulation, event handling, effects/animations, and AJAX operations. It is widely used by major websites for interactive prototypes and applications due to its small size, extensive documentation, plugins, and cross-browser compatibility.

jQuery is an open source JavaScript library that simplifies HTML and JavaScript interaction. It allows selecting elements, performing actions on them such as adding/removing classes or showing/hiding, and handling events. jQuery is widely used by major companies and projects due to its small size, cross-browser compatibility, and large plugin ecosystem that extends its functionality.

HTML 5 is the latest version of the HTML standard. It includes several new elements and features to improve structure and behavior. Some key changes include new semantic elements like <article>, <aside>, <header>, and <footer>; built-in support for audio and video; the <canvas> element for drawing graphics; and forms with new input types. HTML 5 aims to simplify HTML and separate structure and presentation, making code cleaner and pages more accessible. It is developed jointly by the WHATWG and W3C organizations.

The document discusses the evolution of web video and its increasing impact on mobile from 2010 to 2012. Key developments include the rise of smartphones, video formats supported in different browsers, tools for format conversion, and libraries like Video.js that provide consistent video playback across devices. WebRTC was also introduced, allowing real-time video chat in browsers. Overall mobile traffic and use of mobile video grew dramatically in this period.

In this lecture, I provide an overview of what it takes to create amazing Web Apps : rich media, the Canvas API, local storage and offline persistence are covered.

This document provides an overview of various HTML5 APIs for multimedia, including native <video> and <audio> elements, the <canvas> element for scriptable graphics, and geolocation APIs. It discusses key considerations around supporting different media formats in <video> and <audio> and controlling media playback via JavaScript. The document also briefly introduces other HTML5 APIs for offline applications, local storage, and databases. It emphasizes the importance of feature detection over browser sniffing for progressive enhancement.

The document provides an overview of HTML5 including: - New tags such as article, aside, audio, canvas, and video - The structure of an HTML5 page including the doctype, meta charset, and link types - Forms with new input types and validation attributes - Playing audio and video with HTML5 tags and controlling them with JavaScript - Drawing graphics on a canvas using JavaScript - Web workers for running scripts in background threads - Options for data storage including web storage, web SQL, and IndexedDB

HTML5 provides new semantic elements that help improve accessibility and SEO. These include <header>, <nav>, <article>, <aside>, <footer>, <time>, <video>, <audio>, and more. HTML5 also introduces new features like local storage, offline caching, and geolocation that enhance the mobile web experience.

The document provides an introduction and overview of HTML5. It discusses the structure of an HTML5 page, including updates to the doctype, removal of xmlns, and addition of the meta charset tag. New HTML5 elements like article, aside, audio, canvas, and video are presented. Updates to HTML5 forms, including new input types and attributes, are covered. The use of video and audio elements is explained. Finally, the canvas element is introduced and basic drawing using the canvas context is demonstrated.

Bruce Lawson demos HTML5, especially forms and video element at Sheffield Speak The Web, 8 February 2010

The document discusses HTML5 and its APIs. It provides an overview of several HTML5 APIs including the geolocation API, web storage API, web workers API, and WebSocket API. It also discusses how these new HTML5 features allow for more advanced web applications compared to older technologies like Flash. Finally, it mentions some libraries and tools for testing HTML5 browser support.

This document discusses HTML5 and related web technologies. It introduces HTML5 semantics like header, nav, article, section, aside, and figure. It demonstrates using these elements to mark up a simple web page. It also covers HTML5 features like video, canvas, and SVG for rich media, as well as JavaScript APIs and libraries for manipulating these elements. Finally, it addresses questions around browser support for HTML5 and ensuring websites will work across browsers.

The document discusses HTML5 APIs and new features available for video and canvas elements. It provides code examples for using the <video> element to embed video with controls and multiple sources, and for drawing shapes and images onto a <canvas> element using its 2D context.

The document discusses HTML5 APIs and new features available for video and canvas elements. It provides code examples for using the <video> element to embed video with controls and multiple sources, and for drawing shapes and images onto a <canvas> element using its 2D context.

This document provides an overview of HTML5 and what's new in the latest version. It discusses new semantic elements like <header>, <nav>, and <article> that improve document outlining. It also covers new multimedia features like native audio and video playback without Flash, as well as 2D/3D graphics using <canvas>. Other additions include new form controls, multiple file uploading, and geolocation. While HTML5 brings many new features, it is an ongoing evolution of HTML rather than a completely new language.

21 September 2011 presentation to Accessibility London (#a11yldn) unconference on HTML5 and accessibility by Bruce Lawson of Opera.

Part II of the standards-next.org workshop on HTML5 with Bruce Lawson, concentrating on audio, video and canvas (plus hints of additional HTML5 API niceness)

The document discusses HTML5 multimedia capabilities for playing audio and video natively in browsers without plugins like Flash. It covers the <video> and <audio> tags, supported formats like MP4, WebM, Ogg Theora, and browser support. It also discusses the media playback API and features like controls, sources for different formats, and responsive design.

This document provides an overview of HTML5 and discusses whether it should be used today. It notes that while HTML5 is exciting, there are still interoperability issues that make it premature to deploy for most sites. The document then covers the history and development of HTML5, new semantic elements, forms, multimedia capabilities like video and canvas, geolocation, offline detection and more. It emphasizes using feature detection and providing fallback options to support older browsers.

This document discusses new multimedia capabilities in HTML5, including browser-native <video>, <audio>, and <canvas> elements. It provides examples of how to use these elements to embed video and audio with controls and different formats, access camera feeds, and manipulate image data in the <canvas>. It also addresses concerns about browser support and recommends feature detection rather than browser sniffing for progressive enhancement.

This document discusses HTML5 and related topics. It provides code examples of new HTML5 elements like <header>, <article>, and <canvas>. It demonstrates how to add semantics, draw shapes, and load images onto a canvas. It also mentions new APIs for video, custom data attributes, and live regions for accessibility. The goal is to introduce HTML5 and showcase its capabilities for building engaging web content.

In this, my talk for Webinale in Berlin, June 1st 2011, I give an overview of HTML5 history and main features, relating it all back to how possible it is use develop with these new features today. Thanks to Patrick Lauke for allowing me to steal a lot of his slides ;-)

The document discusses Robert Nyman's career in developer relations, including the different personas in the field, common activities like speaking at events and using social media, and challenges around measuring the impact of the work. It provides tips for those in developer relations such as figuring out your strengths, getting feedback, acknowledging people, and having passion for the work of connecting with developers.

New internet users are coming online around the world and are facing very different constraints to accessing the internet. In this talk, we'll cover what we've learned from building experiences for new internet users and walk through how you can build great experiences that work well for billions of users around the world. This is a presentation from Google I/O 2017, the video is available at https://www.youtube.com/watch?v=wD3rpdiLMyY Speakers: Tal Oppenheimer, Mariya Moeva, Robert Nyman https://twitter.com/taloppenheimer https://twitter.com/marrrr https://twitter.com/robertnyman

Daydream is a VR platform from Google that aims to make VR experiences more accessible and approachable through mobile. The document discusses how VR challenges traditional design expectations around visuals, presence, immersion, interfaces, attention, and timing. It emphasizes experimenting with bite-sized VR experiences that tempt user curiosity on mobile through Daydream.

This document discusses improving predictability for web developers. It describes challenges like cross-browser inconsistencies that make development difficult. The authors outline efforts by Chrome to address these issues, such as collaborating with other browsers, listening to developers, and minimizing breaking changes. Developers are encouraged to test new browser features, file bugs, and provide feedback to help continue enhancing predictability.

The document discusses the future of the web, covering topics like user identification, payments, connecting with hardware, virtual reality, and more. It notes that user identification will improve with autofill and smart lock passwords. Payments will be simplified through the Payment Request API. Connecting with hardware like Bluetooth devices and NFC will allow interaction with physical objects. Virtual reality on the web is progressing with the WebVR API landing in browsers. Overall, the web continues advancing in powerful ways.

A presentation about the Future of the Web at the Cold Front conference in Copenhagen, Denmark, Sep 1 2016.

Presentation about the Future of Progressive Web Apps at the Google for Indonesia event in Jakarta, August 2016.

This document discusses trends in web and mobile usage and Google announcements from Google I/O. It notes that while native mobile apps saw more usage time than browsers in the past, the web has grown significantly with over 1 billion users on browsers. Google announced several new products at I/O including Instant Apps for Android, apps on Chromebooks, Google Home, Google Assistant improvements, Allo with smart replies and Google Assistant integration, Duo video calling with a Knock Knock feature, Daydream VR platform, and projects from ATAP like Jacquard and Soli.

This document provides an introduction to progressive web apps (PWAs). It discusses the history of web technologies from HTML and HTTP in the early 1990s to more recent developments like service workers, push notifications, and web app manifests that enable PWAs. Features of PWAs are described like reliability, performance, engagement, and integration with the operating system. Case studies are presented showing the benefits some companies have seen from implementing PWAs.

This document provides a history of the development of the web from 1991 to the present. It discusses technologies like HTML, HTTP, XMLHttpRequest, AJAX, and mobile web development. It then introduces progressive web apps, which are web applications that are reliable, fast and engaging like native apps through the use of technologies like service workers, web app manifests and push notifications. Examples are given of companies like Flipkart that have seen success adopting progressive web apps.

The document discusses the current state and future of the web. It notes that while native apps have gained popularity, especially on mobile, the web still accounts for a large portion of usage. It outlines tools from Google like service workers, push notifications, and app install banners that aim to close capabilities gaps between the web and native apps. The document advocates for progressive web apps that are accessible like websites but also feel like native apps to users. The future of the web, it argues, depends on continuing to match and surpass native platforms while keeping the web open, accessible, and long-lasting.

The document discusses the current state and future of the web. It notes that while native apps have gained popularity, especially on mobile, the web remains strong with over 1 billion active users. It outlines tools from Google like Service Workers that help the web compete with capabilities previously only available to native apps like push notifications, offline access, and background processing. The document advocates for continued progress to simplify the web development process and ensure the longevity of technologies, arguing this will help the web remain diverse and accessible across all platforms.

The document discusses the current state and future of the web. It describes how the web currently lacks capabilities that native mobile apps have like push notifications, background processing, and offline access. However, new web features being developed like Service Workers, Push Notifications, and Background Sync aim to address these gaps. The document argues that with these new features, the divide between native and web is diminishing and the web can provide an app-like experience without requiring users to download an app. The future of the web depends on further developing these capabilities and ensuring the web remains accessible, simple to use, and continues to work across all platforms.

The document discusses the current state and future of the web. It notes that while native apps currently dominate mobile usage, the web is working to address its limitations through new features like service workers for offline access, background sync for periodic processing, and push notifications. It highlights tools from Google like Mobile-Friendly Test, Chrome DevTools, and Web Fundamentals. It argues the web needs to simplify onboarding and spread awareness of its capabilities to ensure its long-term viability against native platforms. The future of the web depends on matching and surpassing native capabilities while keeping content universally accessible across different platforms.

The document discusses various Google projects focused on the future including Google Now on Tap, Google Photos, virtual reality initiatives like Cardboard and Expeditions, self-driving cars, Project Loon for internet access, Google Lens, Project Soli, and advice to talk to everyone, listen, and show respect. It also mentions the author Robert Nyman working at Google Stockholm and projects like TEKLA, Jacquard, and Spotlight Stories.

A presentation about Google and Developer Relations in the Nordics, what the region is like and different initiatives.

Developer relations works to champion developers in different regions by removing obstacles, being responsive to their needs, and networking and lobbying on their behalf. They aim to acquire and engage users for developers' apps and games through Google services like Google Play, which has paid $7 billion to developers so far and reaches over 1 billion Android users worldwide. Developer relations representatives like Robert Nyman are available to help developers and can be contacted for additional support.

Android TV is determined to be a significant player in the connected TV market as old TV devices are being replaced by new connected TVs at a rate of 100-200 million per year. Android TV powers televisions, media players, and gaming consoles like the Nexus Player. Content and apps are delivered through Android TV, and the Cast feature allows other platforms to connect to Android TV devices. Developers are encouraged to get involved early to acquire and engage users through games and services.

New improvements for web developers - Promises, fetch, Service Workers, Push notifications, Add to Homescreen. Slides from a talk I gave at #frontendfi in Helsinki yesterday

A talk given at the frontend.fi meetup in Helsinki about Mobile phone trends, user data & developer climate .