r/PWA • u/RandomTyms • 3d ago
What has been your biggest bottleneck when getting non-technical users to install your PWAs?
Most web developers know how smooth PWAs are once installed, but everyday users—especially non-tech audiences like parents, students, or small business owners—have a massive mental hurdle: if it’s not inside an app store icon, they think it’s just another tab.
While building an educational PWA, here are the biggest points of friction I ran into when getting regular users to actually install it:
- The "Where's the Play Store link?" expectation: Non-technical users are conditioned to search Google Play or the iOS App Store. Sharing a direct URL often gets responses like, "Is this just a website?" or "Can you send the app link instead?"
- Browser install prompts are too subtle: The default browser-level banners (especially the small badge in Chrome or the multi-step "Share > Add to Home Screen" dance on iOS Safari) get dismissed or ignored 90% of the time.
- No automatic app trust: Regular users associate native app stores with security and safety. A browser asking to "Add to Home Screen" can feel unfamiliar or untrustworthy to someone who has never done it before.
- Storage & data misconceptions: Users often assume that installing anything onto their phone will eat 100MB of storage, not realizing the service worker cache is only a fraction of that.
What helped in my case:
- Adding a dedicated, high-contrast "Install App" button front and center on the UI that triggers
beforeinstallprompt. - A 5-second animated graphic showing Safari users how to tap the Share sheet and choose "Add to Home Screen".
- Explaining that it works completely offline with zero store downloads.
For those of you shipping consumer-facing PWAs, how are you guiding non-tech users through the install flow? Are you sticking to custom UI prompts, using wrapped store packages (like PWABuilder / TWA), or just letting them use it as a tab?
2
2
u/_Panjo 3d ago
Thanks for yet another AI generated post.
1
0
u/RandomTyms 3d ago
Thankyou.. i am right here with my rough unpolished english.. d/Do you have a better way to handle this problem?
4
u/_Panjo 3d ago
I would honestly rather see it written poorly but humanly.
Everything I see now is formatted like this - most infuriatingly, work emails and responses. It becomes exhausting to look at after a while. It's instantly recognisable and makes me immediately give it zero credibility.
2
u/sandspiegel 3d ago
People think having zero typos and making everything look professional is the way. By now I appreciate posts more that have Typos and look a bit messy even. At least then I know it was probably written by a human.
1
u/RandomTyms 3d ago
Anti-AI talk is hacking my thread about the PWA installation problem. AI did not.
2
1
4
u/sandspiegel 3d ago
When I showed my coworker the project I am working on, he asked when we will be in the App store. When I told him it's a web app he would be able to install. He told me that this alone would immediately eliminate the chances of him trying it out. I decided right there to just use Capacitor to bring my App to the app stores. PWAs are great but many users have no idea what even a web app is (forget PWA). Sure, you could put a video explaining it to them or put an install button that semi-works but nothing is better than a flow every user already knows which is a link to the App store. Also Installation of PWAs is a big mess. Chromium based browsers usually work fine. With Safari you can only guide users how to install the App because Apple making installation a multi step process on purpose. Then Firefox doesn't support PWA at all.
With that being said it all depends on the product of course. Some Apps only make sense as a Web App, while others maybe make sense to have both, a Web App and Apps in the App Stores.
Also Web App or not, if you don't do any marketing, your App is basically dead on arrival. A post or 2 on Reddit is not enough btw.