# Build an extensionĭepending on the user experience you want to provide, it might make sense to convert your entire app into an extension. Building a web app is typically preferable to this, because this approach forces users to install an extension that is only useful on your site and can cause increased friction.Īs Chrome extensions can't be run on other browsers, you should detect when required functionality isn't available and provide explanatory text for users on these other browsers. In this case, you use a progressive web app together with an externally connectable extension your web app can send messages to. If there is a capability that your Chrome App has that the regular web platform can't provide, it might be available as an extension API. Users who choose to install your PWA can launch it via icons and shortcuts, similar to the way that Chrome Apps can be installed today. PWAs are installable on both desktop and mobile platforms. If there are gaps in the web platform for your application, let us know. If there are web platform features you need that are only available in select browsers, you can use feature detection to gracefully degrade or include explanatory text when your app is run in a browser that doesn't support a particular API. As part of our Web Capabilities (codename: Fugu) efforts, we are investigating ways to improve the migration path to the web for developers that depend on exclusive Chrome App APIs-in particular the Sockets, HID, File System, and Serial APIs. # Build a Progressive Web Appīuilding a Progressive Web App (PWA) is the ideal way to reach users across all operating systems. Recommended migration options for packaged apps are listed in order from simplest to most complicated. To transition away from a Chrome packaged or hosted app, the following options are available. Read the announcement and learn more about migrating your app.
Chrome browser and the Chrome Web Store will continue to support extensions. Important: Chrome will be removing support for Chrome Apps on all platforms.
0 kommentar(er)
