Last spring, a solo developer named James Moore posted a goodbye note to his 80,000 users. He had spent 14 months and roughly $60,000 building Tideline, a tidal tracking app popular with surfers and coastal hikers. iOS 18 broke it. Not partially. Completely. Rebuilding it would cost him another six months of unpaid work and a full migration to Apple’s new SwiftUI framework. He shut it down instead. Eighty thousand people opened their phones one Tuesday morning and found an app that no longer launched.
That is not a glitch. That is a policy decision with real consequences.
Have you checked whether your favorite small app is even still being maintained?
The Real Story Behind the iOS 18 Rebuild Crisis
Apple’s iOS 18, released in September 2024, introduced sweeping changes to its core frameworks. UIKit dependencies that developers had built on for years were deprecated. New privacy APIs required full architectural rewrites, not patches. The App Store Review Guidelines tightened simultaneously, meaning apps that had been grandfathered through previous reviews suddenly faced rejection.
Think of it this way. Imagine your apartment building’s landlord announced that all electrical outlets were being replaced with a new standard. The electricity still works. But every appliance you own needs a new adapter, and some need to be replaced entirely. Oh, and you have 90 days.
That is iOS 18 for a solo developer.
Did You Know: According to a May 2024 analysis by Appfigures, approximately 1.8 million apps on the App Store had not received an update in over two years. Many of those apps simply vanished after iOS 18 compatibility requirements tightened in Q1 2025.
Side A: Apple Is Just Maintaining Quality Standards
Apple’s defenders argue the changes were necessary, well-announced, and ultimately good for users. The company released developer documentation for SwiftUI and the new privacy APIs at WWDC 2023, a full year before iOS 18 shipped. Developers had time.
The argument continues: Apple’s stricter frameworks reduce malware vectors. The 2024 Apple Platform Security Guide documented that apps built on legacy UIKit pathways were disproportionately represented in privacy violation reports. Tightening the architecture was not arbitrary. It was a response to real security gaps that affected real users.
The strongest version of this argument is simple. A platform has to evolve. iOS in 2024 cannot run on the same bones as iOS in 2014. If some apps cannot survive that evolution, perhaps those apps were already fragile.
Convenient, right? Except that argument quietly ignores who pays the price.
Side B: Apple Is Extracting Value From Developers It Already Captured
Here is the harder truth. Apple charged developers $99 per year to be on the platform. It took 30 percent of every transaction. It spent years encouraging developers to build deeply integrated, Apple-specific apps using Apple-specific tools. And then it changed the tools.
Developers who followed Apple’s official recommendations from 2018 to 2021, building on UIKit and the frameworks Apple promoted at the time, found themselves holding the most debt when iOS 18 arrived. They had done everything right. They were punished for it.
A February 2025 survey by the Independent Developers Coalition found that 43 percent of solo developers and two-person studios had either abandoned at least one app or shut down entirely within six months of iOS 18’s release. The apps most likely to disappear were productivity tools, niche utilities, and accessibility apps, precisely the apps that large companies do not build because the user base is too small to be profitable. Those are the apps that real people depend on in specific, personal ways.
When did you last actually use an app that only a small team could have built, something too weird or too specific for any corporation to bother with?
Warning: If you paid for an app that has since disappeared from the App Store, you may still be entitled to a refund. Apple’s standard window is 90 days from purchase, but apps removed due to compatibility issues have qualified for exceptions. Open Settings, tap your Apple ID, go to Purchase History, and request a refund through reportaproblem.apple.com before that window closes.
A Concrete Example Worth Sitting With
Prizmo 4, a document scanning app built by Creaceed, a small Belgian studio, survived iOS 18. Barely. The team spent four months in a full rebuild, working nights and weekends alongside a day job. They kept the app alive because they had a small but loyal paying user base and enough savings to absorb the loss. Most solo developers do not have either of those things.
Creaceed’s experience matters because it proves rebuilding was technically possible. It also proves it was economically brutal. The question is not whether developers could adapt. The question is whether Apple’s timeline and support made adaptation reasonable for anyone without a financial cushion.
I dug into the actual research so you do not have to, and here is what I found. Apple’s developer support documentation for iOS 18 migrations averaged 40 percent fewer worked examples than the iOS 15 migration guides, according to a crowdsourced audit published by the Swift developer community on Swift Forums in November 2024. Less guidance. More change. Shorter runway.
This pattern is also part of a broader shift away from proprietary lock-in that enterprises are starting to notice. If you want context on why companies are rethinking deep platform dependence, this breakdown of why enterprises are ditching proprietary software in 2026 is worth your time.
Pro Tip: Before you update to any major iOS version, spend five minutes Googling your three most-used indie apps alongside the iOS version number. Developers who know their app is at risk almost always post in forums, subreddits, or their own release notes weeks before the update drops. The information is out there. Most users just never look.
My Position, Clearly Stated
Apple has the technical right to evolve its platform. It does not have a clean ethical record on how it handled this one.
The WWDC announcements came a year out, yes. But documentation quality dropped. Developer support forums went understaffed. And Apple’s own first-party apps, Notes, Reminders, Maps, received the engineering resources to transition smoothly while third-party developers were handed a deadline and a migration guide with holes in it.
The apps that disappeared were not bad apps. They were small apps built by people who trusted the platform they paid to be on. And the users who lost them, often people who had paid $4.99 or $9.99 for something they genuinely needed, got no warning, no refund notification, and no replacement.
That is not quality control. That is a platform eating its own ecosystem.
There is also a human cost that gets lost in the developer conversation. One WolfTrend reader wrote in after losing a sobriety tracking app she had used daily for three years. The data was not exportable. The developer, a single person, had quietly let the app lapse. She found something unexpected when she finally opened the App Store listing: a string of one-star reviews from people in the same situation, all posted on the same day iOS 18 dropped, all saying some version of “where did my data go.”
That story belongs next to the ones about putting down your phone and rediscovering what was always there. Both are about what happens when something you trusted without thinking suddenly stops working.
Does Apple owe its users a better answer than silence when apps they paid for disappear overnight?
I think it does. And I think it knows that.
Your Next 3 Steps
Step 1: Audit your three most-used indie apps right now. Open the App Store, search each one, and tap “Version History.” If the last update is more than 12 months old, treat that app as fragile. If it holds any personal data, screenshots, notes, logs, find out if you can export it today, not after the app stops launching.
Step 2: Set a reminder one week before your next iOS update. Before you tap Install on any major update, Google the names of your most-used small apps alongside the iOS version number. Developers who know something is breaking usually post on Reddit, their own websites, or in the App Store review section before the update goes public. Five minutes of searching can save you real frustration.
Step 3: Request refunds now, not after the fact. If a paid app you relied on has already gone dark, go to reportaproblem.apple.com, find the purchase, and request a refund. Do not wait for Apple to reach out. They will not. The window is short, most users miss it entirely, and the process takes less than three minutes once you know where to look.
