Alex gives an overview of why web apps don’t feel “appy” today, and shows how service worker is enabling a whole new world of appiness - beyond the simple goal of making web apps work offline, to building truly engaging web applications.
Making Web Apps Appy
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-08-06 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-08-06 UTC."],[],["Service worker technology is enabling a shift in web application development, moving beyond merely providing offline functionality. The current problem is that web apps lack the \"appy\" feel of native applications. Service workers allow developers to build more engaging and robust web applications, transforming them into experiences that rival native apps. This is accomplished by making web apps feel more app like, moving beyond simple offline access.\n"]]