But some questions still remain:<\/p>\n In this post, we’ll explore these questions and try to answer them.<\/p>\n Steve Jobs’ original vision for the iPhone in 2007 was that applications were actually web applications: You already have everything you need if you want to know how to develop applications for the iPhone today: just use modern web standards.<\/p>\n But that original view has changed, in 2008 the big app boom started when Apple first introduced us to the App Store. There is only one problem with this story: this boom is ending.<\/p>\n In the United States, for example, the number of app downloads has been decreasing by 20% each year.<\/p>\n Other studies also point out that 60% of all apps have never even been downloaded. In addition, more than 65% of smartphone users do not download apps every month.<\/p>\n Another interesting fact is that of the 1.5 million apps on the Google Play Store, only a few thousand have any engagement<\/a>.<\/p>\n Finally, smartphone users spend 80% of their time using only 5 apps<\/a>.<\/p>\n All of this data makes us worried. But even with all this information, apps certainly still have their place, and for many companies they still make a lot of sense.<\/p>\n My point is, building a native app can be a very expensive solution for some companies, and for some products it just doesn’t make sense to have a native app.<\/p>\n But what can we do then?<\/p>\n To be on the same page, let’s start with the definitions:<\/p>\n Progressive Web Apps are a set of techniques for developing web applications, progressively adding features that were previously only possible in native apps.<\/p>\n The following characteristics, created by Google<\/a>, accurately define what is expected of a PWA:<\/p>\n That is, if before only native applications had: push notifications, offline operation, geolocation and an icon on the home screen, now we can enjoy all these benefits using a 100% web application.<\/p>\n The community is very excited about these new technologies.<\/p>\n Christian Heilmann, for example, said this<\/a>.<\/p>\n I am convinced that PWAs are necessary to move in the right direction and are a very important change to the status quo.<\/p>\n We can already see one of the most obvious benefits of PWAs: retention<\/strong>.<\/p>\n A user who wants to try an application needs to go through several steps:<\/p>\n It is common to have a loss of 20% of users for each of these steps. The same is not true on the web. Just access a link and a few seconds later we are already testing the product.<\/p>\n That is, the user does not need to commit, and waste time, to install an app so that they can evaluate whether that particular app was worth it or not.<\/p>\n If you really need a native app, the necessary expense of hiring a specialized team of iOS\/Android developers will certainly be worth the cost\/effort.<\/p>\n However, as we’ve already seen, in many cases it is simply no longer necessary to build an app. A PWA may well meet your business requirements. If that is the case, the savings generated by this decision will be immense.<\/p>\n One of the most famous success stories of Progressive Web Apps is that of Flipkart<\/a>.<\/p>\n Flipkart is India’s largest e-commerce site. The experience in building the Flipkart Lite (which is the PWA version of the app) resulted in a 70% increase in sales conversions<\/a>.<\/p>\n In addition, Flipkart Lite had other impressive numbers:<\/p>\n The video below shows a summary of the Flipkart case:<\/p>\n![\"image](\"https:\/\/www.htmlgoodies.com\/wp-content\/uploads\/2021\/04\/Figure01-1.jpg\")
Figure 1<\/strong>. Progressive Web Apps<\/p>\n\n
The Application Crisis<\/h2>\n
Progressive Web Apps<\/h2>\n
\n
Retention<\/h3>\n
\n
Economy<\/h3>\n
User Cases<\/h3>\n
\n