Software Support Becomes the Next Test for Connected Devices
Connected products have a habit of outliving the attention paid to them at launch. A smart thermostat, a fleet of industrial sensors or a building-management controller may remain in service for years after the model disappears from the shop shelf. How long its software will be supported is therefore not an administrative detail. It determines whether the device can be kept secure, repaired and used, or whether it becomes a liability that is cheaper to replace than to trust.
That shift is putting software support periods at the centre of product quality. For the Global Tech Awards, which recognises engineering across the technology sector, the issue sits where security, sustainability and design meet. A support commitment is a promise about the future of a product. Manufacturers that treat it as part of the design brief, rather than a footnote in a manual, are likely to find it easier to earn confidence from buyers.
When patches stop, risk starts
End-of-support is often described as the point at which a manufacturer stops adding features or answering help-desk questions. The security consequence is more serious. Once a product stops receiving updates, vulnerabilities discovered later can remain unaddressed in devices that are still connected and still in use. The device does not need to be new to be attacked; it only needs to be reachable and imperfect.
Connected devices often sit in homes, factories and public infrastructure, where replacement is disruptive and sometimes dangerous. A security flaw in a sensor or controller can expose a network, interrupt an operation or force an emergency upgrade. The risk is not limited to the device itself. An unsupported product can become a weak point that others have to defend against.
Support policies are frequently vague. A vendor may promise ongoing updates without defining what that means, or may blur feature releases with security maintenance. A clear policy states how long security updates will be provided, what kinds of fixes are included, and what happens at the end. It also explains how customers will be told when a support period is coming to a close.
Support commitments become buying criteria
For enterprise and public-sector buyers, the support period is becoming part of due diligence. Procurement teams already ask about warranties, spare parts and service levels. Software support belongs in the same conversation. A device that will stop receiving security fixes before the end of its expected service life creates a future cost: replacement, isolation, compensating controls or a difficult migration.
Buyers can ask vendors to state update commitments, spare-parts availability and repair paths. They can require that support terms survive the sale of a product line or the failure of a supplier. They can also plan asset refreshes around published dates rather than discovering them when a patch stops arriving. These are not exotic requirements. They are the connected-device equivalent of asking whether a building has a fire exit.
Public commitments also act as a trust signal. A manufacturer that publishes a support period, explains how it will communicate changes and offers a route for repair is making itself easier to compare with rivals. The absence of such information is equally informative.
Design and business models determine longevity
Support periods cannot be extended by policy alone. They depend on engineering choices made long before the first update ships. Modular hardware, replaceable components and accessible connectors can make repair economic. Secure update mechanisms, signed firmware and a clear process for handling cryptographic keys make long-term patching feasible. Long-term component sourcing and documentation help a manufacturer keep producing fixes after the original supply chain has moved on.
Software architecture matters too. Devices built on platforms that can receive security patches independently of major feature releases are easier to maintain. So are products with a clear separation between safety-critical functions and general-purpose services. The opposite pattern — tightly coupled software, undocumented dependencies and update paths that require a full replacement — makes every fix more expensive and every support extension harder to justify.
Repairability and security are often treated as separate goals. In practice they reinforce each other. A device that can be opened, diagnosed and fitted with a replacement part is more likely to remain in service long enough for software support to matter. A device that cannot be repaired has a de facto support period set by its weakest component.
The traditional model for consumer electronics has been simple: sell a new device, support it for a period, then encourage an upgrade. Connected products complicate that model because the cost of replacement is not only the purchase price. It includes installation, configuration, data migration and the disruption of removing a device from a working system. Manufacturers can respond by offering lifecycle services: extended support contracts, refurbishment, managed replacement and take-back programmes. These models can align revenue with the useful life of the product rather than solely with the next sale.
A lifecycle test for awards
The Global Tech Awards can play a useful role by recognising products and programmes that combine security engineering, repairability and lifecycle planning. Awards often reward what is visible at launch: performance, design, novelty. A lifecycle commitment is harder to demonstrate in a product demo, but it is part of whether a product is genuinely well engineered.
Categories that examine connected devices can ask how long security updates will be provided, how repairs are handled and how end-of-support is communicated. They can also recognise the less glamorous work behind a product: update infrastructure, component sourcing, documentation and take-back systems. That kind of recognition matters because it shifts the definition of quality from the first day of use to the whole period in which a product is expected to work.
The end of software support is no longer a customer-service issue that can be handled by a notice on a website. It is a security event, a sustainability question and a design constraint. As connected devices spread through homes, factories and public infrastructure, the length and clarity of support commitments will become part of how products are bought, regulated and trusted. Manufacturers that publish clear periods and design for long-term patching will not simply be better at support. They will be making a more credible claim about the quality of the product itself.