The original concept of the iPhone didn’t include an app store.
Steve Jobs’s idea of apps for the iPhone was to use websites as apps. This didn’t take off. Instead, they built the app store specific for the iPhone. The App Store ended up being a huge revenue stream for Apple.
The idea of website apps for iPhone wasn’t pursued.
Fast forward to 2015.
The advancement of web-based technology changed the way we interact with webpages. The idea of Progressive Web Apps (PWA) started as an idea to replace App Stores.
Google’s Chrome OS is a good example of an ecosystem based off progressive web apps.
I could see a future where you pay for web storage and all of your apps connect to the storage.
Requirements for a Progressive Web App
There are 3 things required for these web apps to function.
1. Secured using HTTPS
2. A service worker
3. Web App manifest
The HTTPS means the data going from the site to the server is secured. This is present almost every website now.
Service worker allows the developers to tell the app which files need to be cached. This is what makes the web apps fast.
The Web App manifest is a JSON file to give a description of the app to the browser. It has the name, author, logo, description, and resources needed for the app. This is what make sure the app is discoverable.
How the apps work
PWAs, traditionally, aren’t installed from an app store.
They install straight from a tab. Chrome, Edge, Firefox, Opera, and iOS Safari allow you to install apps from websites. Once you install a PWA they look like every other app.
(Microsoft and Google have started adding them to their App Stores. But only in the last couple of years.)
When you’re on a website with the 3 requirements above, you’ll get a pop up saying, “Install to Home Screen”.
You click on this pop up and the browser installs the web app to your device. This can…