Jump to content

Bloatware

From Consumer Rights Wiki
Revision as of 06:40, 15 March 2026 by Rudxain (talk | contribs) (OSS is irrelevant, source-available is technically correct. A bit pedantic, I know)

This article is a stub. You can help by expanding it.

A moderator needs to check the page before this notice can be removed. Visit the noticeboard or the #appeals channel in either Zulip or Discord to request removal.
More info ▼

An article may be flagged as a stub when it is missing major elements needed to make it useful to a reader. You can help by adding missing sections, verifiable sources, relevant company policies and communications, etc. to make the article more complete.

There are multiple definitions of bloatware within the context of software. They include:

While the term "bloatware" is commonly ascribed to software, hardware bloat also exists.[1] See IoT devices for examples.

Bloat can be a symptom of a decline in quality of devices and services, colloquially referred to as enshittification.

Why it is a problem

Bloatware often arises as pre-installed software and applications because the device manufacturer (OEM) has a contract or partnership with another corporation. The terms and processes leading to these partnerships, however, lack transparency. One study determined that personal data collection and user tracking was prevalent in pre-installed apps, with the data collection including personally identifying info (PII) and geo-location data, personal email and phone call metadata, contacts, behavioral and usage statistics as well as isolated malware samples.[2]

Bloat, in any of its forms, raises privacy and security concerns[3]. As a rule of thumb, every added branch of code can make a program exponentially harder to prove for correctness[4], making it impractical or impossible to verify that a program is not malicious (such as spyware) or has an exploitable vulnerability. The problem is exacerbated if the app is not source-available, since reverse engineering is difficult and (in some cases) illegal. This means that user is unable to control or ensure the safety of their devices.

Bloat is known for causing sub-par user experience:

  • Increased latency, "slowness", when using programs and applications[5]
  • High memory use prevents or impedes multitasking[6]
  • High power usage increases energy bills and reduces battery lifespan
  • Over reliance on network connections (e.g., internet) preventing data from being cached locally[7], which can both impede access as well as increase cellular-data billing
  • Instability issues due to difficulty in testing and verifying big code-bases[8]

If non-sustainable energy sources are used to power these devices with bloatware, bloat can contribute to climate change. This is true for any excessive processing (CPU, GPU, etc.) and network abuse (such as AI training).

See also

References

  1. Ionescu, Bogdan (2025-09-13). "Hosting a WebSite on a Disposable Vape". BogdanTheGeek's Blog. Archived from the original on 9 Feb 2026. Retrieved 2026-01-15.
  2. J. Gamba, M. Rashed, A. Razaghpanah, J. Tapiador and N. Vallina-Rodriguez, "An Analysis of Pre-installed Android Software," 2020 IEEE Symposium on Security and Privacy (SP), San Francisco, CA, USA, 2020, pp. 1039-1055, doi: 10.1109/SP40000.2020.00013. https://ieeexplore.ieee.org/document/9152633 Accessed 26 Feb 2026. (Archived)
  3. Hubert, Bert (2024-02-08). "Why Bloat Is Still Software's Biggest Vulnerability". IEEE Spectrum. Archived from the original on 31 Jan 2026. Retrieved 2025-11-21.
  4. Howard, Gavin (2024-03-26). "What Computers Cannot Do: The Consequences of Turing-Completeness". Gavin D. Howard. Archived from the original on 2025-12-14. Retrieved 2026-01-06.
  5. https://developer.mozilla.org/en-US/docs/Web/Performance (Archived)
  6. https://en.wikipedia.org/wiki/Thrashing_(computer_science) (Archived)
  7. "Local-first software: You own your data, in spite of the cloud". Ink & Switch. 2019. Archived from the original on 30 Jan 2026.
  8. Muratori, Casey (2018-05-12). "The Thirty Million Line Problem". Molly Rocket. Retrieved 2026-03-15 – via YouTube.{{cite web}}: CS1 maint: url-status (link)