TL;DR
A product designer argues companies should be required to publish software interfaces and hardware specs once devices reach end-of-life so communities can keep them usable. The proposal cites Right to Repair progress, a personal smart-scale example, and calls for EU-level enforcement while stopping short of demanding full source releases.
What happened
In a short essay published January 13, 2026, Marciano Planque contends that when consumer hardware reaches end-of-life (EOL), manufacturers ought to make at least the necessary software interfaces and hardware documentation public. Planque recounts owning a smart weight scale that still pairs over Bluetooth but lost its companion app, which previously stored multi-user history; the hardware still works but is far less useful without maintained software. Citing occasional exceptions such as Bose and the 2024 shutdown of Spotify’s Car Thing, Planque frames the change as a follow-up to the Right to Repair movement and urges enforcement — preferably by the European Commission — so companies must publish basic GitHub repositories with hardware specs and connection protocols. The author clarifies the ask is not to open-source entire platforms tied to larger services, and notes that easier development tools make community-driven replacements more attainable.
Why it matters
- Reduces avoidable electronic waste by preserving device functionality after vendor support ends.
- Gives consumers ways to keep devices useful without relying on companies to maintain apps.
- Extends the practical life of hardware and supports sustainability goals.
- Enables maker and developer communities to build replacement software when vendors stop support.
Key facts
- The essay was published January 13, 2026 by Marciano Planque.
- The author owns a smart weight scale that still connects via Bluetooth but has lost app functionality; the device’s display still shows weight while the app previously stored data for up to five users.
- Planque proposes firms should publish basic GitHub repos containing hardware specifications and connection protocols after products reach EOL.
- The piece references the Right to Repair movement as a precedent and suggests the European Commission as a preferred enforcer of such rules.
- The author cites Bose as an example of a company that sometimes makes resources available, and contrasts that with Spotify’s retirement of its $200 Car Thing at the end of 2024.
- Planque explicitly says the proposal does not demand open-sourcing an entire codebase when an app is part of a larger platform.
- The essay notes that more accessible development tools (referred to as 'vibe-coding') make it easier for non-expert users to tinker and potentially replace software.
What to watch next
- Whether the European Commission will take up or propose any regulatory mandate to require publication of specs and protocols when hardware reaches EOL — not confirmed in the source.
- If more manufacturers follow examples like Bose and publicly release documentation or reference repos for discontinued products — not confirmed in the source.
- The emergence of community-built replacement apps or projects for discontinued devices enabled by published specs — not confirmed in the source.
Quick glossary
- End-of-life (EOL): The point at which a manufacturer stops selling, supporting, or updating a product.
- Right to Repair: A movement and set of policies aimed at giving consumers and independent shops the ability to fix and maintain products.
- Open-source: Software whose source code is made publicly available for use, modification, and redistribution under a license.
- Firmware / Companion app: Software that runs on a device (firmware) or on a connected phone/computer (companion app) to enable functionality and features.
- Bluetooth: A short-range wireless communication standard commonly used to connect devices like phones and peripherals.
Reader FAQ
Who proposed this requirement?
The idea comes from Marciano Planque in a January 13, 2026 essay.
Is the author asking companies to open-source all their code?
No. The author specifically says they do not expect entire codebases to be open-sourced when apps are tied to larger platforms.
Does the proposal say the EU will enforce this?
The author suggests the European Commission as a preferred enforcer, but actual regulatory action is not confirmed in the source.
Will publishing specs guarantee devices keep working?
The essay argues published specs and protocols would enable communities to build replacement software, but outcomes depend on community interest and resources.
Home January 13, 2026 · 2 min read EOL. When hardware products reach end-of-life (EOL), companies should be forced to open-source the software. I think we've made strides in this…
Sources
- When hardware goes end-of-life, companies need to open-source the software
- Keeping tech alive: The open-source communities fighting …
- Why End-of-Life Open Source Is a Hidden Audit Risk
- Understanding EOL OSS risks – and what to do
Related posts
- When hardware hits EOL, companies should release the software
- Google Nest Wifi Pro drops to half price — a simple, capable mesh router
- Capitol Hill Battle Over the Repair Act Seeks Easier Car Fixes