4 ms·
> Then you're out of step with what users want these days. Two things: 1. The person you respond to is also a user, no reason to dismiss their point of view
by dgellow 7y ago
> Then you're out of step with what users want these days.
Two things:
1. The person you respond to is also a user, no reason to dismiss their point of view
2. I don’t think browsers asked users for what they want! It’s a bit disingenuous to say “that’s what users want” when the communication is one way only.
- onion2k 7y agoTry talking to some developer relations people from the Google Web team, Mozzila, Microsoft etc. They're all very receptive to feature requests. It absolutely isn't a one way street.
- wtallis 7y agoHow are feature requests from web developers to browser vendors evidence that browser vendors are paying attention to the desires of end users?
- onion2k 7y agoThe evidence is that the end users use these things when they're implemented in browsers and web developers adopt them in their apps.
- pjmorris 7y agoI promise that I have never asked for a notification or a pop-up. They 'work' from the point of view of web sites and browser vendors, maybe more so than from the perspective of users.
- onion2k 7y agoI promise that I have never asked for a notification or a pop-up. Very few people ask for a specific implementation of a feature unless they want you to clone something they've seen elsewhere. People don't do that. In user focus groups I've been in though users have told me that they find it hard to know when they need to pay attention to something, or when they've been tagged in to something, or to know when a server side task has completed, or when a long-running webworker process has completed. All of those things are obvious use cases for some sort of notification, and when the feature has been implemented users both enable them and click on them. Heck, I got a Google Calendar notification pop-up while I was writing this comment. The problem is that you don't want notifications so you want them to be removed from browsers and then no one gets notifications even if they want them. That's not reasonable. The answer is that you need to be able to block them easily; to turn that feature off for yourself. This exists (in Chrome) - chrome://settings/content/notifications You can disable them for all sites. And yet you'd rather complain that they exist instead.
- WarOnPrivacy 7y agoTurn off notifications by default so that people who need/want them (the minority) can get them from the relevant sites (the exceptions). After that turn off stickies, floaters, modals, etc by default & those who wish to have their browsing experience assaulted into a 1 inch box can opt in.
- hackmiester 7y agoThis is how notifications work in Firefox and Chrome today. The site prompts you to allow notifications. If you do nothing, they are not enabled.
- WarOnPrivacy 7y agoBy default, the user gets notified that the site wants to send notifications.
- endemic 7y ago> They're all very receptive to feature requests. I think that's part of the problem.
- onion2k 7y agoBeing receptive to hearing them is very different to actually implementing them.
- WarOnPrivacy 7y agoVoted most insightful comment.
- handedness 7y agoExactly. Default browser settings ≠ user preference. Default browser settings = what the browser developer believes will best server the browser developer's interests.