Will the iPhone 6s sitting in your kitchen drawer actually open your banking app tomorrow morning? It opens every app on the home screen today, which is exactly why an old iPhone still running years after launch feels like proof that nothing's wrong. The home button still clicks, the battery still gets through most of a day, and nothing about the hardware looks broken. None of that tells you what you actually need to know: which version of iOS that specific model is still allowed to run.
Apple draws a hard line with every major iOS release, and that line typically moves forward by a chip generation or two each year, according to Apple's own compatibility documentation. An iPhone 8 and an iPhone X both run on the A11 chip, and iOS 16 needed exactly that; iOS 17 then raised the requirement to the A12 chip inside the iPhone XS and XR, stranding the 8 and the X for good. Whether your particular phone still qualifies for new app updates and current security patches depends on which chip is soldered inside it, not how clean the screen looks or how long the charge lasts.
That's the real tension buried inside the question of whether an old iPhone is still running fine: opening an app and being fully supported by that app are two different states, and the gap between them can sit quietly for months before it shows up as anything you'd actually notice.
Why Apple Cuts Off Older iPhones
Apple's support cutoffs follow a pattern that rarely gets explained plainly, even though it decides the fate of every iPhone eventually. Each major iOS release targets a specific band of chips, typically covering roughly five to six years of hardware, and anything older simply isn't offered the update. No jailbreak, no hidden settings toggle, and no amount of patience changes which chip generation a given iOS release supports. That's the ceiling, full stop.
Developers work against the same ceiling from the other side. When a developer raises an app's minimum supported iOS version, usually to use a newer framework or meet Apple's current technical requirements for new submissions, every iPhone running an older OS loses access to that specific update immediately, even while the previous build keeps working for a while. Apps are built against a deployment target, and any device below that target can't install the new version at all. The app doesn't break the day that happens. Check the chip generation before you assume anything else about a phone's future.
What 'Still Running' Actually Means for Your Apps
Here's where the common shorthand falls apart. Saying an old iPhone still runs a given app usually just means the icon sits on the home screen and opens when tapped, and that's the lowest bar an app can clear: nothing about automatic updates, and nothing about whether its connection to its own servers still meets current encryption standards.
Or rather: an app opening is the minimum signal of health, not a reliable one. The better evidence is whether the app has shipped an update in the last few months that your specific iOS version can actually install, because that tells you whether the developer still counts your device as part of the supported fleet. The real deadline isn't your iPhone's age, it's the iOS version Apple stopped shipping to it.
What you'll notice when you set an iPhone 8 next to an iPhone 12 is that both open identical apps today. The difference only shows up later, one update at a time.
AppWanderer's own tracking backs up that distinction. The site's Supports the Oldest iOS board ranks the subset of apps, 1,088,906 of them as of November 2026, by how far back their minimum supported iOS version reaches, and the current top five, including DutchArtMavens and Vision Hoops, all score a perfect 1.0, meaning they still accept the oldest iOS version that board tracks. AppWanderer tracks more than 1,105,000 App Store apps in total, and the overwhelming majority of that catalog requires something newer than that floor. A tiny sliver, nothing more.
Which Old iPhones Still Handle Today's Apps
Four iPhone generations account for most of what's still in active use, and each one sits in a different support zone right now.
Current iOS support snapshot:
- iPhone 6s, 7, and original SE: capped at iOS 15, with security updates now occasional.
- iPhone 8 and iPhone X: capped at iOS 16, no new app updates since.
- iPhone XS, XR, and iPhone 11: still receiving current iOS releases and app updates.
- iPhone 12 and newer: fully current, no compatibility concerns for years to come.
None of this makes the capped tier suddenly dangerous to own. It means the safety margin for sensitive tasks, mobile banking, health portals, anything tied to a password manager, keeps shrinking every time a new security requirement reaches newer devices only. TLS, the encryption standard behind secure app connections, gets updated through the operating system itself, not through the app alone, which is exactly why a capped iPhone can't keep pace no matter how often the app updates. Match your model to that list before deciding anything else.
Keep It or Retire It
This isn't a battery-replacement guide or a breakdown of which brand-new flagship to buy instead, and it doesn't cover jailbroken or enterprise-managed iPhones, where the support rules work differently. It's about reading your current device's support status honestly before deciding either way.
The decision rarely needs to be dramatic. An iPhone 8 or iPhone X used mostly for music, casual games, and reading is arguably fine to keep running for years past its last iOS update, because none of those uses depend on the security layer that stopped improving. Weigh three things before deciding anything else: which apps you actually use for money or health, how recently those specific apps shipped an update, and whether Settings still shows your iOS version receiving anything new. A browser tied to financial accounts is a different story entirely.
Here's the boundary that actually matters. Anyone using an iPhone stuck on iOS 15 or iOS 16 for mobile banking, a password manager, or health-portal logins should, as a practical guideline, treat that phone as unsuitable for those specific tasks, not because the app will obviously crash, but because the underlying network security stack no longer receives the fixes that keep login sessions genuinely safe. That's a real exclusion, not a vague caution: if your financial life runs through that device, the standard of it still opening fine doesn't apply to you. But that exclusion is narrow. It doesn't touch casual use at all.
Ignore that boundary and keep banking from a capped device anyway, and the risk doesn't announce itself. It accumulates quietly until a credential gets intercepted on a connection the phone can no longer verify correctly. So migrate those logins first.
Plenty of owners have heard the just-upgrade advice so often that it stopped meaning anything, and that skepticism is fair, given how often it's pitched by someone trying to sell a new phone. The realistic alternative isn't doing nothing, it's usually a certified refurbished iPhone SE (third generation) or iPhone 12, both of which cost meaningfully less than new hardware while landing comfortably inside Apple's current support window for years to come. Hardware longevity and software longevity aren't the same fight: under California's Right to Repair Act (SB 244), manufacturers must make parts and repair documentation available for seven years on devices in this price range (a worn battery or cracked screen can usually still get fixed years after Apple stops shipping new iOS versions to that model), but the law says nothing about software support timelines. That's exactly why a phone can be perfectly repairable and still functionally stuck, and that's not great if the device in question is the one holding your banking app.
If your iPhone is an iPhone 8, iPhone X, or anything older and you only use it for media, casual apps, and reading, keep using it until the hardware itself gives out: the software ceiling isn't a safety issue for those tasks. If that same device is the one you check your bank balance or a health portal on, treat the iOS cap as a real deadline and move those specific logins to a phone still inside Apple's current support window, an iPhone XS or newer at minimum. If you're not sure which category you fall into, open Settings, then General, then About, and compare the iOS version listed there against Apple's current compatibility page for the app you're worried about; that single check settles more than any general rule can. None of this means retiring a phone the moment it ages out of new features. It means being honest about which specific uses already crossed the line.
