3 ms·
I guess I don’t understand the feature development part of the question. If you have enough users on the mobile or tablet web app and the specific PWA feature (
by 1123581321 5y ago
I guess I don’t understand the feature development part of the question. If you have enough users on the mobile or tablet web app and the specific PWA feature (like offline) makes the app more useful, then you would invest in it to the degree warranted and wouldn’t worry about installs, just usage. If your company is dead set on putting all effort into the native app, regardless of additional benefit relative to improving other platforms, and you’re looking at changing that priority, that’s different, of course.
We’ve found trying to drive home screen installs to be generally useless. But announcing new mobile web app features through the usual channels (“what’s new” monthly emails etc) does seem to affect usage.
- brundolf 5y agoIt's more a question of "is there a user segment whose first choice among the three would be a PWA, given the option". And then I guess also, "does the general public even know about/understand the concept of PWAs to begin with?" Mainly looking for anecdata here
- AlanYx 5y ago>is there a user segment whose first choice among the three would be a PWA, given the option One meaningful user segment is corporate workers with relatively restrictive IT departments, where you're not able to install native apps. I'm in that category, and use several PWAs.
- brundolf 5y agoInteresting, I never would have thought of that angle