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.
2021 Chrome Dev Summit: Web Performance 101Tammy Everts
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.
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 progressive web apps (PWAs) and outlines key considerations for creating a PWA. It addresses questions around what a PWA is, how to make a website feel like an app, offline functionality, push notifications, and creating a roadmap. Examples from companies that implemented PWAs successfully are provided. The conclusion recommends developing a progressive roadmap that starts with baseline PWA features and builds out functionality over time based on priorities and initiatives.
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.
How slow load times hurt UX (and what you can do about it) [FluentConf 2016]Tammy Everts
This document discusses how slow load times can hurt the user experience on websites and provides suggestions for improving performance. It notes that users expect pages to load within 2 seconds and cites studies showing that even small improvements in load time (1 second or less) can significantly increase conversion rates and other metrics. Common causes of poor performance are discussed, such as inefficient stylesheets, unoptimized JavaScript, and large images. The document provides many suggestions for optimizing front-end and back-end performance, such as creating a performance budget, minimizing page weight, deferring scripts, optimizing third-party content, and continuous monitoring.
In 2016, mobile internet usage exceeded desktop for the first time! With over 50% of users on mobile, is your web app optimized for them?
Let’s learn about Accelerated Mobile Pages, how AMP address mobile user challenges and build a valid AMP app together!
http://nodevember.org/speaker/Lisa%20Huang
The document discusses the rise of post-modern web applications (PMWAs), which resemble desktop applications more than traditional web pages. PMWAs have asynchronous communication with backends, complex client-side logic, and must scale to large numbers of users. While new technologies like HTML5 enable PMWAs, traditional techniques may not apply, and new paradigms are needed. However, not everything requires new approaches. The talk outlines features of PMWAs and examples like Google apps, then discusses enabling technologies like JavaScript improvements, component frameworks, and local storage.
How to fix the design issues that matter on the pages that matter [2016 Smash...Tammy Everts
How do you know what consumers expect from your site? Every shopper is different and every visit is different. Industry stats tell only part of the story. You need to crack the hood and analyze your own real user data. This talk covers how and why to gather real user data and connect the dots between the metrics that matter most -- IT, UX, and business -- in order to create better shopper experiences and improve your business.
Chris Heilmann gave a talk celebrating beautiful web sites but noted that many sites could be more optimized. He highlighted that the average site is over 2 MB in size, with images making up over 1 MB of that. Many sites use unnecessary libraries, send high resolution images to all devices, and include autoplay videos without checking connection speed. However, newer browser capabilities like Flexbox, Service Workers, and camera/microphone access provide opportunities. Sites should cut unnecessary code, optimize images, and leverage new technologies to create accessible experiences for all types of users on today's capable browsers.
How To Be an HTML5 Mobile Cloud ChampionChris Love
Chris Love is a Chief Mobility Officer who focuses on mobile cloud technologies. He advocates for mobile-first design and HTML5 web applications to reach large consumer markets on personal mobile devices. Some key points he discusses include using meta tags and viewports to optimize the mobile experience, leveraging new HTML5 form inputs and CSS3 features, and considering touch and mobile usability in design. He also discusses options for enterprise mobility including managing devices and data in the cloud.
This is an introduction to Developing Mobile Web sites using Microsoft Webmatrix and jQuery to create rich, enganging mobile web sites. You can view the demo site http://m.movie.extremewebworks.com
That's crazy! how to build single page web appsChris Love
The document discusses building single page web apps and provides tips for doing so efficiently. It recommends using templating to build markup on demand, destroying and rebuilding elements, and managing data through tombstoning, on-demand loading, and purging stale data. It also recommends libraries like Backbone.js, Upshot.js, Navigation.js, and Knockout.js and discusses using local storage and deferred loading of content to improve performance of single page apps.
Stapling and patching the web of now - ForwardJS3, San FranciscoChristian Heilmann
This document summarizes a talk given by Chris Heilmann at ForwardJS in 2015. Heilmann discusses the state of web development technologies and how developers have focused too much on experimental features that are not ready for production use. This has led to a fragmented web where browsers implement features differently. He argues developers should focus on standardizing and improving existing web standards rather than constantly introducing new technologies. ES6 is highlighted as a priority for improving existing JavaScript.
The document discusses developing mobile web experiences. It covers topics like understanding the mobile landscape with different phones and browsers. It recommends a single responsive site over separate mobile and desktop sites. It also discusses techniques like progressive enhancement, touch patterns, and frameworks like jQuery Mobile. The goal is to provide an accessible and optimized experience across all mobile devices.
This document provides guidance on how to build effective mobile web apps. It discusses understanding the mobile landscape and user needs, designing for a mobile-first approach, leveraging HTML5 features, optimizing for touch interfaces, and using technologies like CSS3, JavaScript, and device APIs. The key recommendations are to focus on the most common user tasks, reduce content, and make all functionality accessible within 3 taps or clicks.
Presentation to:
Madison Web Design & Development Meetup - February 11, 2013.
Web Content Mavens, Washington, DC - January 8, 2013.
NYC Web Design Meetup -January 24, 2013.
The UX of DATA: Responsive Datenvisualisierung mit jQueryPeter Rozek
This document discusses the importance of responsive data visualization using JavaScript libraries like D3.js, Chart.js, and Chartist.js. It notes that visuals are processed much faster by the brain than text, and that data visualizations can emphasize key points, provide context, and engage audiences. The document recommends prioritizing the story and message over detail, and making visuals memorable to enrich the human elements of any story involving data.
Is the buzz around Progressive Web Apps real or are they simply the latest fad? In this talk, you’ll learn exactly what Progressive Web Apps are, what problems they solve, and what new design challenges they present. Jason will show how organizations are using Progressive Web Apps to provide better and faster user experiences.
Why Progressive Web Apps will transform your websiteJason Grigsby
Progressive web apps (PWAs) can transform websites by making them more like native apps through the use of service workers, web app manifests, and other modern web capabilities. Some key benefits of PWAs include providing fast and reliable experiences even on slow mobile networks, working regardless of a network connection, and engaging users through web app banners and push notifications. Early results show that PWAs can significantly reduce data usage and increase user engagement, conversion rates, and sales compared to mobile websites. While PWAs work across browsers, including on iOS, their full capabilities are still progressively being adopted.
This document discusses progressing web development and applications. It talks about some common criticisms of the web, including that browsers differ too much and the web is too flexible. However, it argues that browser differences allow for innovation and flexibility is one of the web's strengths. It promotes an approach of focusing on capabilities rather than browsers. The document also discusses progressing technologies like service workers and progressive web apps that can make applications work offline and feel more like native apps while still being web-based. It concludes by arguing the web is not going away and is a great platform to build upon.
Presented at Web Directions Code, Melbourne
If you have a website—particularly one that generates revenue for your organization—you need a Progressive Web App. So where do you begin? How do you decide which features of a Progressive Web App make sense for your users? What tools can make the process easier (or harder)? In this practical session, Jason will guide you through the key design decisions you’ll need to make about your Progressive Web App and how those decisions impact the scope of your project. He'll also teach you how to avoid common pitfalls and help you take full advantage of Progressive Web App technology.
This document discusses the future of web apps and why mobile apps should eventually be replaced by web apps. It argues that web apps have improved and now can offer many of the same capabilities as mobile apps, such as working offline, push notifications, and adding to the home screen. New technologies like service workers and WebAssembly will continue enhancing web apps and make them even faster. While mobile apps still dominate usage today, the document predicts web apps will eventually surpass them as improvements are made and users realize the advantages of web apps over native mobile apps.
Decide if PhoneGap is for you as your mobile platform selectionSalim M Bhonhariya
The document discusses strategies for developing a mobile application. It compares web applications, hybrid applications, and native applications. Hybrid applications like PhoneGap allow developing using HTML5/JavaScript while accessing device features, providing a compromise between web and native. The document suggests PhoneGap is best if performance and user experience are not primary concerns and a shorter timeline is needed, as it allows building once and releasing across platforms quickly. Otherwise, native may be preferable for the best performance, experience, and access to device features.
A short presentation answering 3 main questions. Why we need Progressive Web Apps(PWA)? What is a progressive web app & it's features? and how a PWA works?
The Secrets of Succesful Front End Engineering
In this AE Foyer Glenn Dejaeger and Thomas Anciaux will focus on Trends and Aspects of front end engineering. When do you choose a native front end, when should you go web? What is a good front end architecture? How do you cover the design, development, test and lifecycle aspects of a professional front end? How to survive in the jungle of frameworks? What are the current insights and future directions in front end engineering? How do you deal with offline mobile? Do you need front end engineers?
This seminar report provides an introduction to progressive web apps (PWAs). It defines PWAs as websites that are reliable, fast and engaging like native mobile apps. The report discusses the key features of PWAs including being responsive, working offline, and being installable on home screens. It also covers the benefits of building PWAs such as improving user experience and increasing engagement. Specific examples of companies that created successful PWAs are provided, including Flipkart, Housing, and AliExpress. Service workers and application shells are explained as important technologies that enable the core functionality of PWAs. Finally, the advantages and disadvantages of the PWA approach are summarized.
Basic Understanding of Progressive Web AppsAnjaliTanpure1
The document provides an overview of progressive web apps (PWAs). It discusses the history and idea behind PWAs, defining them as websites that are built using common web technologies but adopt features that make them feel like native mobile applications. The key pillars that transform websites into PWAs are listed as being reliable, fast, engaging, and integrated. Core building blocks like service workers and web app manifests are explained. Example case studies are given that demonstrate performance improvements from adopting PWAs. Limitations are also outlined.
Go for Progressive Web Apps. Get a Better, Low Cost, Mobile PresenceMagic Software
Progressive web app may look like a buzz word around improved web standards and few mobile friendly web design patterns. But it brings positive impact on businesses and users. Let’s learn more about it here.
Let's focus on the Mobile Web and talk about the keys to a building a great mobile experience.
From AMP (=Accelerated Mobile Pages) as a starting point up to PWA (=Progressive Web Apps). I will cover the steps through some of the key features we see as core to the modern web experience. As a bonus, we will close with new APIs that expending the web even farther.
Alan Semenov, Development Lead at Enonic discusses progressive web aps and understanding the value from a business perspective on top of a dev perspective
How to Build a Nonprofit Mobile App To Engage SupportersTechSoup
Now more than ever, it's important to be in the palm of your supporter’s hands. Join the Tapp Network team for a discussion on how nonprofits can expand their digital marketing reach with mobile apps. They'll talk about how to choose the best type of app for your organization's mission and budget. From fundraising, engaging volunteers or executing a unique event experience, learn how apps can transform your nonprofit’s marketing strategy.
We’ll cover how to:
> Choose the right type of app builder
> Create an app for fundraising
> Build an app for virtual events and engagement
> Measure analytics for funders, and more!
Progressive Web Applications are a new way to think about using the web to provide great user experiences using the best web platform features.
The education market has many opportunities to benefit their communities using PWAs to deliver information and application experiences across all devices and platforms.
What are Progressive Web Apps and should you build one? This presentation looks at the problems PWA is aiming to solve and shows you how to get started.
IBM Digital Experience 2015 - APPLICATION MODERNIZATION IN THE DIGITAL EXPERI...John Head
Application Modernization is the hottest buzzword in the IT world today. For many, it means the migration and
transformation of an old application to a modern platform and emerging technologies. With Digital Experience solutions, means much more. Application Modernization is about taking what consumers expect from cutting edge mobile experiences, websites and applications – Slick User Experience, Modern Workflow, Mobile Support, Social and Cloud, and applying it to the enterprise space. This session will look at these five areas and apply them to WebSphere Portal and the
IBM Digital Experience solutions. Examples will highlight how and why focusing each of these areas can have a positive impact and upside inside your organization and recommendations on how to apply Application Modernization.
IRJET-Garbage Monitoring and Management using Internet of thingsIRJET Journal
This document discusses building a progressive web app for an educational system. It begins by explaining the limitations of native mobile apps and regular web browsing. Progressive web apps aim to provide the rich experience of native apps while avoiding downloads through the use of service workers, responsive design, and app-like interfaces. The document then reviews related work on improving the mobile web experience. It presents the architecture of progressive web apps, including the application shell model and role of service workers. Finally, it proposes a system architecture for a progressive web app for education and concludes that these apps reduce burdens on users compared to native apps or regular web browsing.
We are obsessed with coding and creating automated workflows and optimisations. And yet our final products aren't making it easy for people to use them. Somewhere, we lost empathy for our end users and other developers. Maybe it is time to change that. Here are some ideas.
This document discusses ways to improve how web developers learn best practices through browser and tooling improvements. It suggests that linting and inline insights directly in code editors could help prevent mistakes by flagging issues early. A tool called webhint is highlighted that provides one-stop checking and explanations of hints related to performance, accessibility, security and more. The document advocates for customizing hints based on a project's specific needs and environment. Overall, it argues for accelerated learning through context-sensitive, customizable best practices integrated into development workflows.
This document discusses privilege in the context of social media and the internet. It acknowledges privileges like internet access, the ability to communicate, and supportive online communities. It warns that machine learning and algorithms risk creating echo chambers and guided messaging if they are not kept in check by human curation. The document advocates taking back the web for decent, thinking and loving humans and using privileges to help others gain access to learning, communication, and communities.
This document discusses artificial intelligence and how it can help humans. It covers that AI is not new, having originated in the 1950s, and is now more advanced due to increased computing power. It also discusses how AI utilizes pattern recognition and machine learning. The document then covers several applications of AI including computer vision, natural language processing, sentiment analysis, speech recognition/conversion and moderation. It notes both the benefits of AI in automating tasks and preventing errors, as well as the responsibilities of ensuring transparency and allowing people to opt-in to algorithms.
Killing the golden calf of coding - We are Developers keynoteChristian Heilmann
The document discusses concerns about the perception and realities of coding careers. It expresses worry that coding is seen solely as a way to get a job rather than as a means of problem-solving. While coding can provide fulfilling work, the document cautions that the need for coders may decrease with automation and that the role may evolve from coding to engineering. It suggests a future where machines assist with repetitive coding tasks and people focus on delivering maintainable, secure products with attention to privacy and user experience.
PWA are a hot topic and it is important to understand that they are a different approach to apps than the traditional way of packaging something and letting the user install it. In this keynote you'll see some of the differences.
This document discusses privilege in technology and perceptions of technology workers. It acknowledges the privileges that tech workers enjoy, such as access to resources and high demand in the job market. However, it also notes problems like peer pressure, lack of work-life balance, and imposter syndrome. Both tech workers and the public have skewed perceptions of each other - tech workers feel others do not appreciate or understand their work, while the public sees tech workers as antisocial or caring only about profit. The document encourages taking small steps to improve the situation, such as being kind to oneself, considering others, sharing knowledge, and focusing on quality over quantity of work.
The document provides five ways for JavaScript developers to be happier:
1) Concentrate on the present and focus on creating rather than worrying about the past or future.
2) Limit distractions by streamlining your development environment and using an editor like VS Code that consolidates features.
3) Make mistakes less likely by using linters to catch errors as you code.
4) Get to know your tools better like debuggers to avoid console.log and gain insights to build better solutions.
5) Give back to others in the community by being helpful rather than causing drama.
The document discusses progressive web apps (PWAs) and provides suggestions for improving them. It notes that while PWAs aim to have engaging, fast, integrated, and reliable experiences like native apps, they still have room for improvement in areas like speed, integration, and reliability. It emphasizes that PWAs should adhere to web best practices and provide actually useful experiences rather than just focusing on technical features. The document encourages helping the PWA effort by providing feedback, using and contributing to tools, keeping messaging up-to-date, and promoting high-quality examples.
Chris Heilmann gave a talk at BTConf in Munich in January 2018 about machine learning, automation worries, and coding. He discussed how coding used to refer to creative programming within technical limitations but now often refers to programming for work. He addressed common worries about new technologies and dependencies, and argued that abstractions are not inherently bad and help more people build products together through consensus. The talk focused on using tools to be more productive and enabling rather than seeing them as dangers, and creating solutions for users rather than fighting old approaches.
The document provides advice and encouragement for someone starting out with JavaScript development. It discusses how JavaScript can be used in many environments like browsers, apps, and servers. It recommends resources like MDN and tools like linting to help avoid mistakes. It emphasizes that this is an exciting time for JavaScript and advises setting priorities and standards, being involved in the community, and bringing new voices and perspectives.
Keynote at halfstackconf 2017 discussing the falsehood of the idea that in order to survive the automation evolution everybody needs to learn how to code. Machines can code, too.
Progressive Web Apps - Covering the best of both worlds - DevReachChristian Heilmann
Progressive Web Apps (PWAs) can provide app-like experiences through the web by making web content fast, reliable and engaging. While PWAs may not be necessary for all projects, they can help clean up and speed up current web-based projects. PWAs leverage new web capabilities like service workers to work offline, load fast, and improve the user experience without having to meet all the requirements of native apps.
Progressive Web Apps - Covering the best of both worldsChristian Heilmann
This document discusses progressive web applications (PWAs) and their advantages over traditional native mobile applications. PWAs use modern web capabilities like Service Workers to deliver native-like experiences to users. Some key benefits of PWAs include their ability to work across platforms, have smaller file sizes for faster loading, support offline use, and provide simple update mechanisms compared to native apps. While PWAs do not have full access to device capabilities like native apps, they allow delivering app-like web content to users in a more accessible and reliable manner than traditional web pages.
This document provides tips for becoming an effective conference presenter. It discusses finding a topic to present on, writing a proposal to submit to conferences, creating presentation materials, writing the presentation, and delivering the presentation. The key steps covered are finding an exciting topic, researching it, crafting a compelling proposal, developing slides and other visual aids to enhance the story and message, writing the presentation to have a clear structure and narrative arc, and practicing delivery techniques to engage the audience. The overall goal is to give attendees a memorable experience that leaves them feeling they learned something valuable.
Suit up, bring extra oxygen Internet space explorers needed.Christian Heilmann
The document discusses the future of computing and artificial intelligence. It notes that people are both excited and fearful about technological progress, and outlines things that are going right (e.g. advances in machine learning and computer vision) as well as things that are going wrong (e.g. lack of transparency, data privacy issues). It argues that the future of computing needs people who are not afraid of technology and who will create interfaces that are simple, human, and help people communicate better. The role of technologists is to use their skills to give people a sense of data ownership and ensure technological progress improves lives rather than just making money.
The document discusses using JavaScript like a buffet, where developers should be flexible and not try to do everything with JavaScript or force their preferences on others. It encourages sharing code openly but also being considerate of different environments and users. Developers are advised to focus on quality over quantity and consider progressive enhancement over delivering all functionality at once.
INTRODUCTION TO FISCAL ECONOMICS OR PUBLIC FINANCEDr T AASIF AHMED
The study of public finance focuses on how the government affects the economy. This area of economics evaluates the public authorities' government spending and revenue and makes adjustments to either one in order to achieve desired results and prevent undesirable ones. Speak with Dr. T. Aasif Ahmed, an Economics faculty member, for further details.
Building Trust Through Transparency Kissht's Commitment during Regulatory Cr...Kissht Reviews
Kissht, a leading India fintech company, has shown an unwavering commitment to these principles, particularly during periods of regulatory crackdowns. By prioritizing transparency and robust compliance measures, Kissht has not only built trust among its users but also established itself as a reliable and ethical player in the fintech industry.
The JD Euroway and Fritzgerald Zephir (Fritz) Financial Debacle.pptxsonalisaini008
In an astonishing series of events, Finance JD Euroway Inc. and its CEO Fritzgerald Zephir (Fritz) find themselves embroiled in a high-stakes legal battle, accused of orchestrating a fraudulent investment scheme.
Unlocking Your Dream Home Understanding Government Subsidies for House and Ho...Kathiriyasubsidyhouse
Purchasing a home is a significant milestone, but the financial commitment can be daunting. Thankfully, various government subsidies and schemes can ease the burden. In this blog post, we'll delve into the intricacies of the government subsidy for house, the benefits of a government subsidy on home loan, and the attractive housing loan interest subsidy offered by Kathiriya Subsidy House. Understanding these can help you make informed decisions and potentially save a substantial amount of money on your home purchase.
Public Expenditure & its Classifications, Canons, Causes, Effects & Theories....Dr T AASIF AHMED
The meaning, classifications, canons, theories, effects, and trends in public spending are all included in this ppt. This has been prepared to aid students in understanding and help them achieve the best grade possible. Kindly provide your insightful opinions and recommendations. For additional details, get in touch with Dr. T. Aasif Ahmed.
6. 💔 The web wasn’t ready for
the mobile form factor.
7. 😠
🌧 Mobile was a throwback to the
web of old
🌧 Small screens, bad connectivity,
unreliable browser support
🌧 Constantly changing conditions
🌧 Hardwired browser and hardware
with unpredictable upgrades
9. You’ve got everything you need if you
know how to write apps using the
most modern web standards to write
amazing apps for the iPhone today.
“
– Steve Jobs, 2007
11. App Store At 6: How Steve Jobs'
Biggest Blunder Became One Of
Apple's Greatest Strengths
http://www.forbes.com/sites/markrogowsky/2014/07/11/app-store-at-6-how-steve-jobs-biggest-
blunder-became-one-of-apples-greatest-strengths/#615411fe4874
“ – Forbes, 2014
13. 😕 902 words article
😕 9.1 MB data
😕 522 requests
😕 52.48 seconds load time
17. 🤔
💸 On the web, users are in control.
💸 Users are conditioned to not pay for
things but find ways around
💸 Somehow, you have to pay the bills…
💸 Let’s try to turn users into products to
sell to others…
The publisher’s dilemma…
20. 😍 Control over the look and feel
😍 Revenue resource (apps cost money)
😍 Control over the distribution (remove
them from the market or only offer in
certain regions)
😍 In-built obsolescence (new versions cost
more)
😍 Control the environment (iOS first,
Android maybe…)
Apps for publishers…
22. 😕 Pricing race to the bottom (99 cents)
😕 Lock-in into the marketplace with its own
rules and restrictions
😕 Revenue share with marketplace/OS
provider
😕 Updates are hard and may be delayed
by the marketplace rules
😕 Turns out, people don’t want to be
locked in…
Reality check for
publishers…
23. 94% of app revenue comes from
1% of publishers
https://sensortower.com/blog/app-store-one-percent
“
24. 80% of users who download an
app fail to become active users.
http://andrewchen.co/new-data-shows-why-losing-80-of-your-mobile-users-is-normal-and-that-the-best-apps-do-much-better/
“
25. In app purchases are where the
money is at - and these are
regulated by the platform or cost
a percentage.
marketingland.com/app-purchases-dominate-ads-app-store-lifetime-revenue-hits-71-billion-183953
“
26. 60% of apps in the Google Play
app store have never been
downloaded.
https://www.youtube.com/watch?v=EUthgV-U05w&feature=youtu.be&t=1m56s
“
27. The average user downloads less
than 3 apps per month. Half of
US smartphone users download
zero apps per month.
http://www.recode.net/2016/9/16/12933780/average-app-downloads-per-month-comscore
“
28. Users try out a lot of apps but
decide which ones they want to
‘stop using’ within the first 3-7
days.
http://andrewchen.co/new-data-shows-why-losing-80-of-your-mobile-users-is-normal-and-that-the-best-apps-do-much-better/
“
29. The average app mostly loses its
entire userbase within a few
months…
http://andrewchen.co/new-data-shows-why-losing-80-of-your-mobile-users-is-normal-and-that-the-best-apps-do-much-better/
“
30. …of the >1.5 million apps in the
Google Play store, only a few
thousand sustain meaningful
traffic.
http://andrewchen.co/new-data-shows-why-losing-80-of-your-mobile-users-is-normal-and-that-the-best-apps-do-much-better/
“
36. Native app install friction blocks
74% of your potential customers
before they ever see your app.
“
https://medium.com/javascript-scene/why-native-apps-really-are-doomed-native-apps-are-doomed-pt-2-e035b43170e9#.axf46f08l
39. ⚠ We weren’t ready to go all
out on web with mobile.
40. 💾
🌧 Instead of creating web sites that
work well on mobile, we packaged
them up and submitted them to
market places.
🌧 In a 1:1 comparison with native
apps, they looked rubbish.
🌧 That’s because they weren’t web
products, but native apps built in
web technologies.
44. ✏ Small initial payload
✏ Form factor supporting content
✏ Form factor supporting interfaces
✏ Offline/Flaky connection support
✏ Taking advantage of the power of
the end user device
✏ Avoiding interaction latency
❤📲
45. The best way to bend the retention
curve is to target the first few days of
usage, and in particular the first visit.
That way, users set up themselves up
for success.
http://andrewchen.co/new-data-shows-why-losing-80-of-your-mobile-users-is-normal-and-that-the-best-apps-do-much-better/
“
53. ✅ Intercept fetch events, respond
with cache
✅ Intercept push events
✅ Intercept sync/periodic events
The big breakthrough: Service Worker
https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API
🔧
54. ✏ Offline
✏ Push notifications
✏ Background Sync
The big breakthrough: Service Worker
https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API
🔧
55. ✅
🔧 Must be HTTPS
🔧 Have a valid manifest with all required properties
🔧 Must have a Service Worker
🔧 start_url defined in the manifest must always
load, including in an offline state
🔧 Must supply an own navigation (independent of
browser UI)
🔧 Responsive to different sizes and form factors.
A progressive web app…
57. Alibaba is the global leader in B2B trade.
Recently, they upgraded to a PWA:
✅ 76% more web conversions
✅ 30% more monthly active users on Android,
14% more on iOS
✅ 4X higher interaction rate from Add to
Homescreen
https://developers.google.com/web/showcase/2016/alibaba
58. Housing.com is one of the leading real
estate platforms in India. After
implementing their PWA:
✅ 38% more conversions
✅ 40% lower bounce rate
✅ 10% longer average session
✅ 30% faster page load
https://developers.google.com/web/showcase/2016/housing
59. PWA Stats - Case Studies
https://www.pwastats.com/
66. There is no official
timeline when or if
ServiceWorker will be in
iOS…
💔
67. iOS has 45% of the US smartphone
market, and iOS users spend $1.08
per user per app per user vs $.43 on
Android.
https://medium.com/javascript-scene/why-native-apps-really-are-doomed-native-apps-are-doomed-pt-2-e035b43170e9#.axf46f08l
“
68. Android has 86% global market share.
“
https://medium.com/javascript-scene/why-native-apps-really-are-doomed-native-apps-are-doomed-pt-2-e035b43170e9#.axf46f08l
71. The existing PWA implementations still
leave web apps as second-class to
native apps in many ways. We want to
fix that.
“
https://blogs.windows.com/msedgedev/2016/07/08/the-progress-of-web-apps/
– "The Progress of Web Apps", Jacob Rossi (2016)
72. 🔧 Runs as a Windows service
🔧 Can wake up the browser even
when the browser is closed
🔧 May spawn multiple Service
Workers at once for performance
(under debate)
Edge plans…
73. 🔧 Bing crawls web sites
🔧 Sites with a manifest go into the
Windows Store
🔧 These webapps are real apps:
Windows Desktop, Windows
Phone, XBox, Hololens,
SurfaceHub…
Windows plans…
74. “Websites that
have taken all the
right vitamins”
– Alex Russel?
https://webmasters.googleblog.com/2016/11/building-indexable-progressive-web-apps.html
75. 🆙
🔧 Any web product can become a
Progressive Web App, not all have
to be.
🔧 You’ll reap the rewards of simple
maintenance and upgrade paths
in the form factor mobile users
expect.
🔧 Apps can hibernate and wake up
on demand - no need to have the
browser open.
76. 🔗
🙂 The great thing here is that
progressive web apps bring
back the power of the link
🙂 You don’t need to play by the
rules of a closed marketplace
🙂 You can send people a link and
by the time they looked at the
app it is ready to use - it is real
try before you buy.
77. In app purchases are where the
money is at, and you can do that in
your own app without splitting costs
with Apple or Google.
http://marketingland.com/app-purchases-dominate-ads-app-store-lifetime-revenue-hits-71-billion-183953
“
78. For all intents and
purposes, PWAs are a
good opportunity to slim
down the web.
?