81–90 of 143 posts
Earlier quoted context omitted.
I disagree, Reddit does well as an app (I’m of the option that HackerNews is too , that’s why in use Octal). It’s just that Reddit has a really bad app.
What capability/user experience does it gain by being an app?
Earlier quoted context omitted.
Push notifications are useful in browsers in all the same places they are useful in mobile apps. Note that browser push notifications also work on mobile, so you don't need to install an app to get real time alerts. For example: - Sites with chat can send you messages even if you don't have the tab open (or even browser in some cases) - Online game e.g. board game or chess can push to you when it's your move. - Home…
> Note that browser push notifications also work on mobile, so you don't need to install an app to get real time alerts. Push notifications in Safari are only supported on desktop for now.
I know I'm a bit tangential, but what are some actually useful examples of push notifications for browsers? Every time I've seen them in action was with spam/clickbait, after someone accidentally subscribed and couldn't remove it.
Shopping apps will ping you throughout the day with "recommended" products, ride share apps will ask you to ride with them during the holidays, social apps will ask you to checkout the newest trend.
All sad attempts to get you to open their app. The worst is when apps don't even let you opt out, so you either get useful notifications and advertisements or nothing.
Earlier quoted context omitted.
I disagree, Reddit does well as an app (I’m of the option that HackerNews is too , that’s why in use Octal). It’s just that Reddit has a really bad app.
What capability/user experience does it gain by being an app?
Earlier quoted context omitted.
Kind of a narrow view. Not all of us who want this are building messaging apps.
So what type of app are you writing that has to accept in app purchases and are push notifications the only thing stopping you from having a much worse web app than a native app?
The snark keeps me from even wanting to engage you...
Earlier quoted context omitted.
Kind of a narrow view. Not all of us who want this are building messaging apps.
So what type of app are you writing that has to accept in app purchases and are push notifications the only thing stopping you from having a much worse web app than a native app?
Earlier quoted context omitted.
Every comment suggesting it brings browsers closer to feature parity with apps is a great argument against the feature. Browsers aren't operating systems. Stop trying to make them be that. It has been a terrible disaster so far, and likely will continue to be going forward, given the lingua franca of development in browsers and all the terrible development practices that have grown up around it.
The "browsers aren't operating systems" ship has sailed long ago, exhibit a: electron apps. Think of it this way. When feature parity of browser sandbox closes on everything a desktop app might want, you no longer need to build with electron but can simply ship 5-15MB of js+css and use the stock browser instead. Similar on mobile. Which will result in: Smaller downloads. Lower memory footprint. Faster launch.
I know I'm a bit tangential, but what are some actually useful examples of push notifications for browsers? Every time I've seen them in action was with spam/clickbait, after someone accidentally subscribed and couldn't remove it.
- Home Assistant
- Discord
- Telegram
- Element
- Buienalarm (weather app)
- RSS reader
- Floatplane.com
- Several sites/forums with comment sections, to notify me of replies etc.
- Gitlab pipeline notifications
- Some smaller services I'm probably forgetting
Basically, anything but the scammy sites that try to force notifications upon you. Generally interactive stuff which I feel shouldn't have a 300MB app with access to file systems (and there's not a lot that _really_ needs an app these days).
To combat the blogspam from Google searches, HN/Reddit links, and whatever else tries to shove stuff down my throat, I have notifications disabled by default so I don't even see the prompts; I manually toggle them on, and I think that should be the default. I also close any website the second I see a popup for newsletters, notifications, or even cookie popups the second they block my reading, unless I can't find the information I need anywhere else.
Earlier quoted context omitted.
The "browsers aren't operating systems" ship has sailed long ago, exhibit a: electron apps. Think of it this way. When feature parity of browser sandbox closes on everything a desktop app might want, you no longer need to build with electron but can simply ship 5-15MB of js+css and use the stock browser instead. Similar on mobile. Which will result in: Smaller downloads. Lower memory footprint. Faster launch.
The more low-level access browsers are required to expose for application development, the worse things will be in almost every dimension, but especially security and performance.
All this functionality is already available for apps including the security model. Nothing new is happening here. App security is an issue, but it's one big tech is already dumping resources into solving.
But, frankly, browsers have some of the best management features for culling analytics, telemetry, watching the traffic and requests being made. It's many times easier for me to see what a web app is doing on the network, and write something to stop it, as compared to a native app.
I know I'm a bit tangential, but what are some actually useful examples of push notifications for browsers? Every time I've seen them in action was with spam/clickbait, after someone accidentally subscribed and couldn't remove it.
Joke aside, it allows PWAs to more fully replace native apps, which is great.