[whoopdedo]

> Maybe it's possible to build browsers and advertising and mobile devices that don't relentlessly erode privacy.

That's nice a nice sentiment. I'd be less skeptical if Firefox didn't change my default search engine behind my back. (After updating Android from 31 to 36.)

[rockdoe]

If you changed the defaults, it was kept. If you never set a search engine, the shipped default was changed (and clearly mentioned as such in the release notes not to mention all over the press, so saying "behind my back" is quite funny).

[talmand]

Just to play devil's advocate, what if the default was the choice the user wanted?

[rockdoe]

Then he can switch it after having read the release notes pointing it out? The behind the back part was unwarranted, so the only thing that's remaining really is "I preferred the previous default" which doesn't quite jive with the "I'm skeptical regarding privacy" complaint that was made.

[talmand]

Then that's just bad design. If there was a possibility of them switching out the pre-determined defaults then the default choices should have been asked of the user from the beginning.

But then, it's hard to make money that way so I can understand why they wouldn't do that.

EDIT: you edited, but I agree the "behind the back" isn't quite right.

[rockdoe]

Presenting modal dialogs to the users on first run is considered terrible UX design with a high bounce rate.

The way you state it, you'd have to ask the user to verify every single setting in your app. That is problematic.

Making money doesn't even have to factor in. (Ok, if nobody uses the apps, you're not making money either, but you get what I mean)

[whoopdedo]

There's default settings, and then there's "default" settings. I think of Debian's debconf and how there are different levels of prompts when installing a package.

A good compromise would be to ask on use. The first time someone searches say "What service do you want to complete this with?" and have Yahoo/Yandex pre-selected. Then never ask again.

The never asking again is the key part. IE's setup dialog is a problem because it's either answer a bunch of annoying questions now or answer a bunch of annoying questions later. It should be a choice of setup now or don't bother me again (unless I activate the setup wizard myself).

[talmand]

I don't think I stated they should ask for every single setting in the app. Exaggerating to support your claim is not the way to go.

But, considering we're discussing a rather popular and commonly used feature that is front-facing in the browser; yes, they should ask up front which search engine provider you would prefer to use. Especially if they plan for the likelihood to change the default, which may be a user's preferred choice.

Also, since they were receiving money from Google to have it be the default search engine and they switched to Yahoo because they got another/better deal; it is about the money.

EDIT: another thought, if the choice provided has a high bounce rate then obviously it would just go with a determined default in that case. Hopefully it wouldn't prevent them from using the app because they declined to set preferences on first run. If they chose not to set the preference and the default later changes, then it's on them.

[tomc1985]

I woke up one day (after clicking update) to find my default search engine set to Yahoo and ads in my new tab page. You can mention it all you want in the release notes, but users don't expect nor want those kinds of things to change.

The only thing more behind-the-back than that is Chrome yanking Java (well, NPAPI) with no warning in Update 42

[whoopdedo]

I had it set to DDG prior. After upgrade it was Yahoo.

I know that Hanlon's Razor tells me to suspect it was just a bug. But the current environment of money and politics makes it hard to ignore the alternative.

[UweSchmidt]

Come on, it's not really "behind your back" if it's something you can immediately see on the page. The search engine thing is the one thing you'd have to deal with as it just about pays for all of Mozilla.

[nosuchthing]

Feel free to revert back to 31 and write your own updates & bug fixes.

[whoopdedo]

I actually did revert to 31 but only because 36 was unusably slow.