Slide from “ by Samsung” Progressive WebVR Apps And why they might be better than native IOS, Android and maybe even Windows apps Think about it. Most native apps don’t need all the native features of an app, such as bio-metrics, access Bluetooth and etc., so why not write an app once and be able to use it on any device? ← introducing Progressive web apps What are progressive web apps PWAs are basically normal web apps with a file and a telling the browser how to cache files, what icons to use, splash screen to use, app’s name on the home screen and etc.. A service worker can also add for your web app! manifest service worker offline support Why not just use a native app? Why would e.g. a news app need anything other than your or Guess what, your web browser can ask for permission to use both of them. Although push notifications require a secure connection ( and a it’s so much more convenient to write a for than having to rewrite and maintain code for all the different platforms. Many companies such as and are already using PWAs and they look great: location push notifications? https) service worker, single app all platforms Twitter, NASA Starbucks PWA vs Native: Features and APIs , running on chrome 63, Feb 2018 what web can do today Advantages of PWAs: developers only have to develop one code base, decreasing the cost and improving the quality of the final product Multi-platform — — almost no download time, prompted to add to home screen when viewing the website. About 60% of mobile users don’t download a single any new apps each month. Frictionless from visiting a website to an installation prompt and installation that takes less than 10 seconds Easily discoverable — — Small download size service workers allow new scripts / stylesheets to be used as soon as they are deployed to the server so the user doesn’t even need to press an update button. Instant updates — Run on any device with a browser Advantages of native apps: Fast, smooth animations Native looking UI Almost instant load Platform support for PWAs Android Google has been actively pushing the concept of PWAs and they recently started to get a lot of attention from Apple, Samsung, Firefox and even Microsoft. Android now fully supports all PWA features and has been the first platform to do so. iOS Safari already experiments with service worker support which will probably lead to PWA support later this year. Although you can’t “add to homescreen” on an iOS, you can still use push notifications. Windows Microsoft has already announced that Edge will support PWAs out of the book very soon. In fact, the most recent insiders version already supports it. However, only about 2% of users use Edge so we will need to rely on Chrome and Firefox implementing this feature. Fortunately, Chrome canary already contains a flag in chrome://flags that allows you to do this: Developer Perspective Deployment If you even produced a native app, you know that the deployment process is painful and time consuming: (production version) → create → the app → compile private key sign publish With a progressive web app, all you need to do is: the web app (npm run build)→ to server build upload Does this mean native apps will eventually die out? No, not happening. Some types of apps will always require more features or great performance so a PWA simply wouldn’t be a suitable option. Conclusion If you’re a developer and you’re planning on building a native app in 2018/2019, consider building a PWA instead of separate apps for each platform. You won’t have to maintain each version, the development version can be reduced by about 3 times and you don’t need to learn all languages. You’ll love it. I will also have a few more tutorials on building a fully featured PWA with push notifications, offline support and caching with both and so if you’d like to see this, so you don’t miss a story. angular react, follow me
