Progressive Web Apps Will Replace Native Apps?
&quot;Before users can use your app you need to get them to download it first. So you will need them to:
- go to the App Store&#x2F;Play Store
- search for your app
- click to install
- accept permissions
- wait for it to download
In each of these steps you can lose 20% of your potential users.&quot;<p>True.<p>Then again, when users have installed the app they need to:<p>1) Open it by a single tap<p>&lt;Automatic face id authentication&gt;<p>2) Enjoy<p>With a web app:<p>1) Open Browser<p>2) Type in the URL or...<p>2) Open settings&#x2F;options menu of the browser<p>3) Select favorites<p>4) Scroll through the list until you find your web site<p>5) Open the website<p>6) Realize you are not authenticated<p>7) Tap login<p>8) enter username<p>9) WTF was the password<p>10) Close the browser<p>11) Open lastpass etc<p>&lt;Automatic face id authentication&gt;<p>12) Search for the website and open it in lastpass<p>13) Copy password<p>14) Close lastpass<p>15) Open browser again<p>16) Paste password<p>17) Tap login<p>18) Enjoy...?<p>Not to even mention high performance 1:1 user experience vs laggy and slowly loading websites, safety of app store, privacy protection by &quot;Sign in with Apple&quot; etc.<p>From developers&#x27; perspective:<p>Mobile apps:<p>- High performance<p>- 100% access to local SDKs, features, hardware (not exactly 100%, but only limited by the OS)<p>- Elegant, fast and safe languages with static typing such Swift and Kotlin<p>Web apps:<p>- Slow<p>- Limited access or no access<p>- JS<p>Of course if you are developing software for media outlet etc. (app for reading news) then it&#x27;s probably not worth the effort to build native app vs mobile first website.