Every major software platform, including Windows, Android and iOS, eventually reaches a published end-of-support date for a given version, and the practical question isn't whether that date exists, it's what actually changes on that date versus what a device owner can reasonably expect to keep working for a while longer. The general pattern across platforms: security updates are the first and most important thing to stop, and their absence is a real, growing risk the longer a device runs past that date; the device itself does not stop functioning on that date, and many apps continue working for a meaningful further stretch before compatibility requirements catch up with the older platform version.
Knowing which stage a device is in (not yet at end of support, past it but still broadly functional, or past it and losing app compatibility) separates a genuine reason to replace a device from an assumption based on the date alone.
Security updates are the first thing to stop, and the risk is cumulative, not immediate
The end-of-support date each platform publishes is specifically the date security updates for that version stop, which means a newly discovered vulnerability after that date will not be patched for a device still on it. That is a real and growing risk, but one that accumulates over time rather than causing an immediate failure the day support ends. A device that continues to be used carefully (cautious about what's installed, ideally on a network segmented from more sensitive use) past its security-update end date is not instantly unsafe on that date, but the risk increases the longer it continues in that state, which is why manufacturers frame the published date as the point to plan a replacement around, not a date to react to only after something goes wrong.
The device itself keeps functioning: app compatibility is what erodes gradually
A phone or computer does not stop turning on or stop running its existing apps on its platform's end-of-support date; what happens afterward is that app developers, over time, raise their own apps' minimum supported platform version to take advantage of newer platform features, which gradually (not all at once) excludes an older, no-longer-updated platform version from receiving the app's newest updates and eventually from installing the app at all. This is why a device just past its end-of-support date often still works normally for months, while a device several platform generations past it can start hitting a real wall of apps that decline to install or update.
The timeline for that erosion varies by which specific apps matter most to the person using the device, not a fixed date the platform itself publishes.
How to check where a specific device actually stands, rather than guessing from its age
Each platform publishes its own official lifecycle or support-schedule page listing exactly which versions are still receiving security updates and which have reached end of support, and checking a specific device's exact platform version against that published page is a more reliable way to know where it stands than estimating from the device's purchase date alone, since actual support windows vary by platform and sometimes by device model. For a device already past its security-update end date, checking whether the specific apps that matter most (a banking app, a specific work application) still install and update normally is the practical test for whether app-compatibility erosion has reached a point that affects that particular use, rather than assuming it has just because time has passed since the published end-of-support date.
At a glance
What changes at each stage of a platform's end-of-support timeline
| Stage | Security updates | Device basic function | App compatibility |
|---|---|---|---|
| Before end of support | Regularly published for known vulnerabilities | Normal | Normal: apps generally support this version fully |
| Just past end of support | None going forward: known future vulnerabilities won't be patched | Normal, unchanged | Generally still normal for most apps, for a while |
| Well past end of support | None, and the unpatched-vulnerability risk has been accumulating | Still functions for existing installed apps | Gradually erodes as individual apps raise their own minimum version requirement |
| Long past end of support | None; cumulative risk is now significant | Still physically functions | Many current, actively updated apps may decline to install or update |
Evidence ledger
Sources behind this post
Microsoft's own official lifecycle page publishing exact support-end dates per Windows 11 edition.
Google's own published update-support window per Pixel model, on the Pixel Phone Help hub; see this post's other citation for why the hub URL is used instead of the specific article path.
Exact questions
Common follow-ups
What actually happens the day a platform version reaches end of support?+
Nothing changes on the device itself that day. It keeps functioning exactly as it did the day before. What changes is that the platform's publisher stops issuing security updates for that version going forward, starting a cumulative risk rather than causing any immediate visible change.
Is it dangerous to keep using a phone or computer past its end-of-support date?+
The risk is real but cumulative, not immediate. A device that continues receiving no security patches becomes gradually more exposed to newly discovered vulnerabilities the longer it runs in that state, which is why manufacturers recommend planning a replacement around the published date rather than treating the date itself as an emergency.
Will my apps stop working the moment my platform version reaches end of support?+
Generally not immediately. Most apps continue working normally for a meaningful stretch afterward. App compatibility erodes gradually as individual developers raise their own app's minimum supported platform version over time, not all at once on the platform's own end-of-support date.
How do I find out exactly when my specific device's platform version reaches end of support?+
Each platform publishes an official lifecycle or support-schedule page listing every version's support window; checking your device's exact platform version against that page is more reliable than estimating from the device's age or purchase date.
Why do some apps stop working on my older phone before others do?+
Each app developer independently decides when to raise their own app's minimum supported platform version, based on which newer platform features that specific app wants to use, so different apps drop support for an older platform version at different times rather than all together.
Does end of support mean the device is broken?+
No. End of support is specifically about security updates and eventual app-compatibility erosion, not about the device's basic hardware or software function, which continues working for existing installed apps well past that date in most cases.
Should I replace my device the exact day it reaches end of support?+
Not necessarily. Checking whether the specific apps that matter most for your use still install and update normally is a more practical test than reacting to the calendar date alone, though the security-update risk is worth weighing into that decision regardless.
Do smart TVs and streaming boxes have the same kind of end-of-support timeline?+
Many do, through their own platform's software-update policy, though the publishing and clarity of that timeline varies more by manufacturer for TVs and streaming boxes than it does for the major phone and computer platforms this post focuses on.
Why does my manufacturer recommend upgrading before support actually ends?+
Recommending a plan ahead of the actual end-of-support date gives time to research and choose a replacement without pressure, and avoids the period of accumulating security risk that begins immediately once the published date passes.
Is there a way to extend security updates past the official end-of-support date?+
For the platforms this site covers, no official mechanism extends security updates past the manufacturer's own published end date for consumer devices; the published date is generally the definitive end of that update path for that specific device and platform version.
How is this different from a phone getting slower after a new model launches?+
This post covers Windows/Android/iOS's published security-update lifecycle; a separate pattern (feature-rollout priority and trade-in value shifting at a new phone's launch) is covered in this site's phone launch-season post and is a different mechanism entirely from a platform's own end-of-support schedule.
From the troubleshooting library
Records related to this post