My feeds this week have been almost entirely one story: the European Commission fining Google 4.34 billion euros over Android. The headline number is the thing everyone fixates on, and it is a genuinely enormous number, but the number isn't the interesting part. The interesting part is what the Commission said Google had actually done, because it's a thing I think about a lot in a much smaller and less newsworthy context. It's about defaults. It's about who gets to decide what's already there when you open the box.
I'm not going to relitigate the legal argument, partly because I'm an engineer and not a competition lawyer, and partly because the full reasoning runs to hundreds of pages that I have not read. The short version, as I understand it, is about the conditions attached to shipping Android with the Play Store: bundle our search, bundle our browser, set them as the defaults, or you don't get the bit your phone is commercially useless without. Whatever you think of the remedy, the underlying observation is hard to argue with. The default is the product. Almost nobody changes it.
defaults are a form of power
I know this from the small end of the same telescope. I run a homelab and a handful of services, and I have spent real evenings of my life on the question of what the default should be, because I have watched, over and over, that whatever I ship as the default is what people use. Not what's best. Not what they'd choose if they sat down and compared. The default.
Set a sensible default on a config flag and ninety-something percent of installs will run with it untouched, forever. Pick the wrong one and you've made a decision on behalf of every user who never opened the config file, which is nearly all of them. This is enormously useful when you get it right, because most people genuinely don't want to make the choice, they want a thing that works. It is a quiet kind of authority when you get it wrong, because you've shaped behaviour at scale without anyone noticing they were shaped.
That's the homelab version, where the stakes are me being mildly annoyed at myself. Scale it up to an operating system on the majority of the phones on the planet, and the default stops being a convenience and becomes the entire market. If the search box that's already on the home screen is the one nearly everyone uses, then owning that default is, functionally, owning search on mobile. The fine is the Commission saying the quiet part out loud: this is not a small thing.
the bit I keep chewing on
Here's where I find myself genuinely conflicted, because I don't think bundling is automatically wrong, and I think the engineer's instinct to want "batteries included" is a good one.
I like software that comes with sensible defaults. A database that ships with a config that works for the common case, a Linux distribution that picks a desktop and a package manager and an init system so I don't have to assemble one from parts, a phone that works the moment I turn it on. Those are all defaults imposed on me by someone else, and I am grateful for nearly all of them. The "do everything yourself" alternative is not freedom, it's homework. Plenty of people have neither the time nor the inclination, and telling them to go and configure their own search engine is not a serious answer.
So the line isn't "bundling bad". The line, and I think this is roughly what the Commission was reaching for, is about whether you can leave. A default you can change is a convenience. A default you can't change, or that's made deliberately annoying to change, or that's tied to something else you need so leaving costs you the thing you actually came for, is a lock. The first is good engineering. The second is the thing that gets you a ten-figure fine.
what it means for the rest of us
For those of us building much smaller things, there's a usable principle in here that has nothing to do with billions of euros.
- Choose defaults like they're the only setting most people will ever experience, because they are.
- Make the off-ramp real. If you ship an opinionated default, make changing it a single obvious step, not a treasure hunt through three config files and a restart.
- Don't tie the thing people need to the thing you want them to use. Bundling a useful default is generous. Bundling it so that declining it breaks something unrelated is the bit that turns a convenience into leverage.
I have no settled opinion on whether 4.34 billion is the right number, or whether the remedy will change anything users actually notice. Past fines in this space have a habit of being absorbed as a cost of doing business and then nothing much shifts. But the story has done the useful thing of making me look again at my own defaults, the ones I set without much thought because someone has to set something. Every one of those is a small decision made on someone else's behalf. The difference between me and the headline is several billion euros and a continent's worth of phones, but it is, underneath, exactly the same decision. The default is the product. It's worth getting right, even when nobody's watching, and especially when they can't easily leave.