PWAs vs. App Stores:
Rethinking App Updates and Distribution
I am convinced of web applications and the possibilities that this open platform offers us. I write a lot about the fact that in many cases, a PWA is in no way inferior to a native app. However, this doesn’t work without a general rethink.
It’s very clever to find everything you can install in an app store. You can find various apps, reviews and possible alternatives centrally. From a user perspective, this initially looks like an incredible win. Of course, if you look closer, it creates a monopoly position very easily. For example, even if you don’t even get your app installed due to lengthy approval processes.
But even if the ones I have installed have an update, I can see it immediately in the overview in an app store. It’s very elegant to know what’s new that I want to try out right away.
Of course we know this on the desktop: I install an application and it regularly checks for updates. Informs me via a popup or a push message that I can install an update. Sometimes it’s done completely manually or even automatically in the background.
PWAs are always up to date - online connection required. I just can’t “register” anywhere that there is an update. Of course, a push message can also inform the user here. Even if the application is not currently being used. But of course it’s no longer as elegant and central as an app store.
This will show what the user really needs. Is it really just a matter of getting used to it? What something new could even look like?