Tech Talk
Insights · Tech Talk

Bloatware: When Software Goes Back for Thirds

Bloatware is software carrying more than it needs. Here's where it comes from, what it costs, and how to keep it off your plate.

TL;DR: Bloatware is software carrying more than it needs, whether that’s apps you never asked for or features piled on until the useful ones get buried. It’s slower, harder to use, and more expensive to maintain. Here’s where it comes from and how to keep it off your plate.

You know the moment. The plates are cleared, someone brings out a third pie, and you say yes anyway. An hour later you’re on the couch, moving slowly, wondering what came over you.

Software gets there too. Feature by feature and app by app, it takes on more than the job calls for, until it’s slow to open, hard to navigate, and much heavier than anyone planned. There’s a word for that: bloatware.

What is bloatware?

Bloatware is software that includes more than users need. The word covers two different kinds of excess, and most of us have met both.

Starting with extras you never ordered

The first kind shows up on day one. Open a new laptop or phone, and you’ll often find it already loaded: a trial antivirus that starts nagging in thirty days, a game you’ll never play, a manufacturer’s app that does something your system already does. Chances are it’s there because the device maker struck a deal with a software company. You weren’t part of that conversation.

These extras take up storage, run quietly in the background, and slow down startup. You can remove most of them once you figure out which ones are safe to delete.

Piling on one feature at a time

The second kind grows slowly. A program starts out doing one job well. Then it adds a feature for one group of customers, a setting for another, a new toolbar, a sidebar, and a pop-up announcing the new toolbar. Every addition made sense to someone. Together, they bury the thing you opened the program to do.

Computer scientist Niklaus Wirth saw this coming in 1995. In an essay called “A Plea for Lean Software,” he pointed out that software was getting slower faster than hardware. People still call that Wirth’s law, and thirty years of software updates have done little to disprove it.

Paying for seconds you didn’t eat

Every feature in a system is a feature someone has to look after. It needs testing when anything around it changes, updates when the tools underneath it change, and a spot on the screen that something more useful could have had. An unused feature keeps costing money long after no one clicks it.

Bloat adds up in three ways:

So how do you keep software lean?

Ordering off the menu

Custom software has a head start here. It’s built for one organization’s work, so it never has to carry features for a thousand other customers with a thousand other workflows.

The rest comes down to how features get chosen. We plan every project feature by feature, so each one gets looked at on its own, like dishes on a menu. That makes the useful question easy to ask out loud: does this one earn its spot?

Sometimes the answer is yes. Sometimes it’s “not yet.” We’ll often build a minimum viable product (MVP) first, the smallest version that does the job well, alongside a roadmap that shows where the system is headed. The “not yet” features wait their turn on that roadmap, until the people using the system can tell us whether they still want them.

It’s also worth asking now and then about the software you already have. Which features does anyone still use? Which ones just sit there, costing upkeep and taking up space?

Leaving room for what matters

Whether it’s a laptop that came preloaded or a system that’s quietly put on weight over the years, we’d love to help you sort out what to keep and what can go. Just maybe wait until after the leftovers.

Talk to us

Bring us the hard version of your challenge.

Thirty minutes with a senior engineer, no pitch and no pressure. Whatever you decide, you'll leave with a clearer map of what you're about to do.

Start the conversation Keep reading