5 ms·
If push notifications are that important for your app, take the short amount of time needed to make it a "native" app. There's enough variety in frameworks that
by falcolas 6y ago
If push notifications are that important for your app, take the short amount of time needed to make it a "native" app. There's enough variety in frameworks that should make it stupidly simple to transform a web-app into a "native" app, without relying on adding yet another attention-invasive feature into the browser.
- raihansaputra 6y agoYes, a solution, but it is not the same. Ex: would you download an app for an airport, or would you rather just scan a qr, load a page, get a notification when it's tine to board, and don't have have an app on your phone again? Same with museums, festivals, concerts, etc. A balance can be struck, but Apple blocks it outright (or even just implement a subset of an API to say they 'support it' while it's unusable (ex: IndexedDb)).
- falcolas 6y ago> Ex: would you download an app for an airport, or would you rather just scan a qr, load a page, get a notification when it's tine to board, and don't have have an app on your phone again? Same with museums, festivals, concerts, etc. This is the status quo. And it works well enough for the niche usecases where push notifications may be justified. I myself have Delta and United apps installed, and have for years now. And even they don’t rely on push notifications for the important messages, they send them by SMS. As for museums, festivals, concerts - what’s push really for? “You just looked at painting 1002, want to learn more?” If I did, I’d look them up. And no, there is no balance when it comes to push notifications on the web. For every gmail, there’s hundreds of thousands of Reddits, who bug you for notifications the moment you land on their page. And even gmail is better as an app.