ConclusionĮveryone is moving towards mobile and with Google promoting Progressive Web Apps and AMP (Accelerated Mobile Pages), they are trying to make the Internet faster overall. Google suggests that PWAs should load a minimal amount of JavaScript so it's fast-loading. Most JavaScript libraries are 350K or bigger. With a PWA, all of the action occurs in the and service-worker.js along with the js/app.js file.Īlso, if you notice, we aren't using any JavaScript frameworks in the project. NET Core, the directory structure provides a more client-side, open-source look-and-feel which makes developing Progressive Web Apps easier to build. I decided to use the ASP.NET MVC Core application to show that any framework can create a Progressive Web Application.Īnother benefit to this project template is the ability to later add a WebAPI to the application for use with the service workers (service-worker.js). Here's a quick glance of the project structure. Create your new project by clicking File » New Project.C:\Users\\OneDrive\Documents\Visual Studio 2015\Templates\ProjectTemplates.C:\Users\\Documents\Visual Studio 2015\My Exported Templates.
I have Windows 10 so they are placed into:
Since it's the easiest to implement and packs the most bang for the buck, I always side with the web.
It seems there's always a debate about which is better: native vs. When a consumer tries to use a native app, every step costs you 20% of your users.
These were the characteristics I was pursuing in my optimization series for building a fast web-based app.īut why is everyone so intrigued with Progressive Web Apps? Why not just create a native application?Īccording to a survey conducted in 2012, there's a downside to installing a native app.