51–60 of 178 posts
Predictable in a user application is the same result from the same action every time. UX changing based on opaque logic and heuristics is anything but predictable.
Earlier quoted context omitted.
Adding a "click to start the experience" button changes the experience. In particular, some users might not see the button if it's subtle, and be unimpressed or think the site is broken. And if the button is not subtle that's bad too. It's also annoying to have to do such a change to your art for a single browser. Overall I think the artist's frustration is understandable, but I agree "destroyed" is perhaps too stron…
Do we really have to pander to people who can’t find a play button? How do these people function at crosswalks or in elevators?
> This way, Chrome gives you a personalized, predictable browsing experience. > predictable What could possibly be more predictable than disabling autoplay altogether? Google says it enabled autoplay for 'over 1000 sites', but we all know Google only cares about one thing and that is playing more ads on YouTube.
Cynicism aside, YouTube is a typical example of a good use for autoplay. A user clicking a link to YT almost always wants to watch the video. "Predictable" probably wasn't the right word for them to use, but I think this is a reasonable move by Google.
> Chrome does this by learning your preferences... This way, Chrome gives you a personalized, predictable browsing experience. In my experience, "learning" and "predictable" do not go together.
But "fi" never launches Firefox anymore because of that one time you accidentally launched Finder instead. And since you keep accidentally launching Finder that way, it never learns that you want Firefox.
So you try "f" but you accidentally launch Flux. And because you keep forgetting it thinks "f" = Flux, it always launches Flux.
So you have to use "fir" to launch Firefox. But "fire" somehow launches Firewatch, a game you forgot you had installed on your laptop.
It's the most obnoxious system ever where each additional keystroke reorders the entire fuzzy result list in the name of "learning." It really is the opposite of predictable.
Bret Victor's response: https://twitter.com/worrydream/status/993167096992288771
I genuinely do not understand the artist in the replies who says this has destroyed their work. Can't the website require you to click/tap once to start its thing, without negative impact? I feel like I must be missing something. (There's a mention about not updating code for existing work, which might be it?)
I start by asking a user whether they want to view the experience in “Stereo Mode” or “Normal Mode”. Whatever they click on, I use that click event to start playing a 500ms long mp3 of silence. When that clip finishes, I use its ‘ended’ event to start it up again. Meanwhile in the render loop, if the user enters an area where I have some auto playing narration, I set a global flag and store the track name in a global variable. Those flags get picked up the next time the 500ms track finishes, and the named track is substituted in.
This is ridiculous, and this is just to play sound files at various points in time. I wouldn’t be surprised to find out that some of Cabbibo’s work uses multiple Audio Contexts or other complicating factors that would make it difficult to retrofit.
summary: google allow 800 of the international youtube domains to autoplay, plus some 200 other publishers to pretend they are neutral.
> summary: google allow 800 of the international youtube domains to autoplay, plus some 200 other publishers to pretend they are neutral. What? How is that an accurate summary? The whole post is about how Chrome will learn your preference for whether to autoplay on domains, not about how it is whitelisting certain domains.
Imagine if someone makes a YouTube competitor. They won't have autoplay for an user's first 20 sessions at minimum! That's significant
The best way to improve autoplay is to disable it. chrome://flags/#autoplay-policy
> This way, Chrome gives you a personalized, predictable browsing experience. > predictable What could possibly be more predictable than disabling autoplay altogether? Google says it enabled autoplay for 'over 1000 sites', but we all know Google only cares about one thing and that is playing more ads on YouTube.
Cynicism aside, YouTube is a typical example of a good use for autoplay. A user clicking a link to YT almost always wants to watch the video. "Predictable" probably wasn't the right word for them to use, but I think this is a reasonable move by Google.
(for the record, at least half the time I open a youtube video I don't want it to play immediately)