Make mobile web apps rock

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.

Presentation about: Why do we need WebSocket? How does it work? Practical use cases How we can implement in iOS

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.

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.

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.

This document discusses the importance of web page speed and provides tips to optimize performance. It emphasizes that speed is important for user experience and engagement. Slow pages can lead to high bounce rates and negatively impact SEO. It then provides the "golden rules" of optimization, which include reducing HTTP requests, minimizing file sizes, caching assets, and using techniques like lazy loading. Specific tools are recommended for measuring performance, including PageSpeed, Speed Tracer, and Dynatrace Ajax. Browser limitations and upcoming technologies that may improve speed are also briefly covered. The goal is to make the web faster by optimizing code, images, assets and more.

This document discusses progressive web apps (PWAs). It notes that PWAs aim to make web apps feel like native mobile apps by being discoverable, installable, linkable, safe, responsive and progressive. The document outlines some key characteristics of PWAs, including that they need to be served from secure origins and have app manifests. It also discusses some common misconceptions around PWAs and notes that as PWAs improve, they will continue to blur the line between web apps and native mobile apps.

This was one of my presentations made for BSc. IT students. A simple introduction to Web development and Web 2.0

This document discusses the differences between CSS and JavaScript and when each is most appropriate to use. It argues that CSS is often underestimated in favor of JavaScript solutions. CSS has advanced significantly with features like calc(), media queries, animations/transitions, flexbox, grid, variables and more. These powerful features allow many tasks to be accomplished with CSS alone without needing JavaScript. The document encourages embracing the "squishiness" of the web and considering CSS more when building interfaces.

Progressive Web Apps aim to bring the benefits of native mobile apps to the web. They use newer web capabilities like app manifests and service workers to deliver app-like experiences through the browser. App manifests allow web apps to be installed on home screens and launched full screen like native apps. Service workers enable features like offline access and push notifications. Early adopters are seeing increased user engagement through Progressive Web Apps, with metrics like conversions and time spent improving. While browser support is still evolving, Progressive Web Apps provide a promising approach for delivering high-quality mobile experiences through the web.

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

The document discusses optimizing client-side delivery of web resources for performance. It notes that generation time accounts for 10-20% of performance, while delivery time accounts for 80-90%. Faster load times improve the customer experience and can increase revenue. Various techniques are presented for reducing load times, such as minimizing HTTP requests, optimizing caching, using content delivery networks, browser-based compression, and minimizing file sizes.

The document provides tips for optimizing websites for mobile search engines. It discusses the differences between mobile and desktop search, including that mobile has carrier search engines that are often white-labeled versions of other engines. It also outlines strategies for mobile search engine optimization, including appropriate site architecture, clean code, relevant mobile content, and submitting the site to various mobile directories and search engines.

This document contains the transcript of a presentation by Chris Heilmann on web development. Some of the key points discussed include: - The benefits of progressive enhancement and using HTML, CSS, and JavaScript together to build robust and accessible websites. - How limitations in early design can foster creativity. - The importance of error handling and defensive coding practices. - Embracing new technologies like Service Workers and Manifests to build Progressive Web Apps. - Rethinking the idea that JavaScript is unreliable and should not be depended on, as modern browsers have made it a capable tool.

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.

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.

This document provides 10 tips to make you a great mobile web developer: 1) Understand the mobile landscape and technologies; 2) Determine optimal content and user flows for mobile; 3) Set the viewport meta tag correctly; 4) Use progressive enhancement; 5) Leverage HTML5 semantics; 6) Understand CSS3 features; 7) Use AJAX and mobile frameworks; 8) Account for touch gestures; 9) Optimize images; and 10) Support offline usage.

This document provides 10 tips to make you a great mobile web developer: 1) Understand the mobile landscape and technologies; 2) Determine optimal content and user flows for mobile; 3) Set the viewport meta tag correctly; 4) Use progressive enhancement; 5) Leverage HTML5 semantics; 6) Understand CSS3 features; 7) Use AJAX and mobile frameworks; 8) Account for touch gestures; 9) Optimize images; and 10) Support offline usage.

This document discusses mobile web and app development. It begins with an introduction and background about the author. It then covers early web development using basic HTML. It discusses the evolution to responsive design and content-first approaches. The document surveys different mobile platforms and compares native apps, hybrid apps, and web apps. It recommends using responsive design and frameworks like Bootstrap to build mobile-friendly websites.

This document discusses approaches to web development for mobile devices. It begins by noting the increasing importance of the mobile web. It then examines three approaches: 1) Doing nothing and hoping modern mobile browsers can handle desktop sites, 2) Creating a separate mobile site, and 3) Having a single adaptive site that refactors content for different screens using fluid layouts, progressive enhancement and media queries. The document dives into techniques for adaptive design like viewport meta tags, touch events, and responsive images. It also notes remaining challenges like viewport interpretation and high-DPI screens lying about resolution.

This document discusses mobile web 2.0 and strategies for mobilizing ASP.NET websites. It defines mobile as being about the person rather than the device, and emphasizes context and short interactions. Key aspects of web 2.0 that apply to mobile include harnessing collective intelligence and data as the next "Intel Inside." The majority of internet usage is expected to eventually be on mobile phones. Over 17 million people in the UK use the mobile web. The document provides demonstrations of detecting mobile browsers, using CSS for small screens, optimizing images, and accounting for varying screen sizes and page structures.

This document discusses approaches to mobile-friendly web development beyond just desktop websites. It outlines three main approaches: 1) Doing nothing and hoping normal websites work okay on mobile, 2) Creating a separate mobile-optimized site, or 3) Having a single adaptive site that uses techniques like fluid layouts, responsive design, and CSS media queries to dynamically adapt to different screen sizes and devices. The document then goes into details about techniques for adaptive sites, including viewport meta tags, touch and gesture support, and using device capabilities like geolocation without plugins. It emphasizes that adaptive design is useful not just for mobile but any device.

This document discusses mobile application development options for developing applications that can run on both iOS and Android platforms using C#. It describes tools like MonoTouch and MonoDroid that allow building native iOS and Android applications using C# and .NET. It also discusses hybrid approaches like PhoneGap that use web technologies to build applications that can be deployed to both platforms. The document considers questions around enterprise deployment, security, data sharing and management of mobile applications.

This document discusses how to create websites for mobile clients using .NET 4.0. It covers key topics like content adaptation strategies, optimizing navigation and input, keeping pages small and lightweight, and minimizing network usage. Resources and tools are also provided to help test mobile websites, including validators, emulators and proxies. The goal is to design sites that are optimized for small screens and the unique constraints of mobile browsing.

This document discusses approaches to mobile-friendly web development beyond just desktop websites. It outlines three main approaches: 1) Doing nothing and relying on modern mobile browsers to render normal sites, 2) Creating a separate mobile site with a subdomain or folder, and 3) Having a single adaptive site that uses fluid layouts, responsive design, and CSS media queries to dynamically adapt to different screen sizes and devices. The document then covers various techniques for adaptive design, including viewport meta tags, touch and gesture support, multimedia without plugins, geolocation, and offline capabilities.

Extended version of my "Making your site mobile-friendly" talk, including a short look at native applications vs web apps, for the UKOLN DevCSI event "Developing for Mobile Applications in Education" in Reading http://www.ukoln.ac.uk/events/devcsi/mobile_applications/

Presented June 8, 2012 (Online) at the 'Access by Touch: Delivering Library Services Through Mobile Technologies' conference sponsored by Amigos Library Services. Description: By the end of 2012, it is expected that more than 80% of the world’s population will have access to a smartphone. Your library users will assume that your library can be accessible from anywhere, at any time, and on any device. Now is the time to be ready! During this webinar, you will: - learn what a mobile framework is. - acquire best practices in mobile Web development. - understand the various technologies (HTML, CSS, JavaScript) and how they work together to build mobile Web apps. - recognize the differences between native and web apps. - have an opportunity to continue to work with Chad after the webinar to demonstrate what you learned. - gain access after the webinar to a free Web server so you can see your mobile Web app live.

Mobile web development is important because over 6.8 billion people in the world use mobile devices. There are currently over 3.4 billion people with mobile phones, making mobile the 7th mass media. When developing for mobile, it is best to target WebKit-based browsers like those used on Android and iOS devices to ensure compatibility with newer HTML5 features. Websites should be optimized for mobile with a responsive design or separate mobile sites at m.domain.com to provide the best experience for touchscreen smartphones and limited feature phones.

This document provides an overview of mobile web development best practices. It discusses viewport settings and using media queries to optimize layout for different screen sizes. It also recommends techniques like inline images, caching, and local storage to improve performance on mobile. The document encourages front-end logic and feature detection over device detection. Overall, it offers guidance on designing responsive websites that provide a good user experience across diverse mobile platforms and browsers.

According to the International Telecommunication Union, at the end of 2011 there were more than 1 billion mobile‐broadband subscriptions worldwide! With more of your library users using mobile devices to access information they will assume that your library can be available from anywhere, at any time, and on most any device. Now is the time to be ready for this demand. In this webinar: - Explore some innovative library mobile website designs and see how they were built. - Understand how HTML, CSS, and JavaScript work together to build mobile websites. - Learn what a mobile framework is and why they are used. - Provide some existing mobile services/apps that can be included in library-created mobile websites. - Acquire best practices in mobile Web development from start to finish.