What I'm Actually Hoping WWDC Announces for Indie Developers (And What I've Already Given Up On)
WWDC is three days out. Here's the honest indie dev take — what platform changes would actually matter to someone shipping six apps alone, and what I've learned to stop expecting.
WWDC is three days out and I've been doing this long enough to know how it goes. The keynote will be polished. The demos will be seamless. Someone will describe something as "magical." And then you'll spend the next six months finding out which of the announced features actually shipped in a state where you can build on them.
This isn't cynicism — it's calibration. There's a version of every WWDC announcement that's real and a version that's a year away. Learning to tell the difference quickly has saved me a lot of wasted sprint planning.
Here's what I'm actually watching for on Monday.
What Would Actually Move the Needle
Better background task handling for small apps. This is the one I care most about and the one Apple is least likely to touch in a meaningful way. If you're shipping a utility or a productivity app that needs to do work when it's not in the foreground, the current system is hostile to indie developers in a way it isn't for companies with engineering teams dedicated to working around it. I've built three different workarounds across three different apps. I would pay for a first-class API.
SwiftUI layout reliability at edge cases. Core SwiftUI is genuinely great now — I'm not complaining about the fundamentals. But there are still edge cases with dynamic type, specific device configurations, and certain animation combinations where behavior diverges from what the documentation describes. I'm not expecting a complete fix. I'd take a stable way to file a bug and know it's actually going to land somewhere.
App Store improvements that aren't cosmetic. More keyword space. Better handling of the review queue for small publishers. Clearer rejection reasons that don't require a human appeal to interpret. Any one of these would have a larger practical impact than most of the new APIs I'll spend the fall exploring.
Anything that makes on-device AI actually usable without a subscription model. The promise of local inference is real. The current state of the tools for shipping it in a production app is not there yet. If WWDC moves this forward by a year, that changes how I think about a project I've had in a holding pattern.
What I've Already Given Up On
A meaningful change to the 30% cut for small publishers. I know there's the Small Business Program. I also know how the math works at the tier most indie developers are actually at. This gets mentioned at conferences and in antitrust filings. It doesn't change at WWDC.
Same-day documentation. The frameworks that get announced on Monday will have documentation that catches up to them over the following weeks and months. I've accepted this. I now build a deliberate lag into anything I want to use a freshly announced API for.
Anything that significantly reduces the App Review wait time for genuine emergencies. There's an expedite process. It works sometimes. You can't build a shipping strategy around it.
Widget interactivity that doesn't feel like a workaround. I want to be wrong about this one. The current interaction model for widgets is clever but it's not what I want. Maybe this is the year.
The Actual Approach
I'll watch the keynote. I'll read the session descriptions. I'll download the first beta. Then I'll spend two weeks actually building with the new APIs before I decide which ones are ready to integrate into shipping code.
The announcements that matter to indie developers are usually the quiet ones — a performance improvement in a framework you already use, a new capability in Core Data or CloudKit that's not headlined, a SwiftUI addition that fixes something you've been routing around for eighteen months.
Those don't get the stage time. They're worth hunting for anyway.
WWDC is Monday. I'll be watching.
XenneX is a one-person studio shipping iOS apps. See what's in the lineup →