I need to be straight with you before we go any further. The iPhone Fold apps not resizing launched yet. There’s no review unit sitting on my desk, no real customer forum thread full of angry owners. So if you searched “iPhone Fold apps not resizing” expecting a pile of complaints from people who already own one, that’s not where we are right now. What we do have is something almost as useful, a truly massive trail of developer betas, leaked framework code, and Apple’s own WWDC26 presentation, all pointing at exactly how big a problem app resizing is shaping up to be for this device before it even ships.
And honestly, that’s the most interesting story anyway. Because the app scaling issue isn’t some hypothetical worry. It’s the single thing that’s already tripped up every major Android foldable maker for the better part of a decade, and Apple is now staring down the same problem in public, through its own developer tools, months ahead of launch.
I’ve been tracking the leaks, testing what I can through the public betas, and reading through the reactions from current iOS developers who are the ones who’ll have to make this work. Here’s where things actually stand.
Wait, How Do We Even Know Apps Won’t Resize Properly Yet?
Fair question, since the phone doesn’t exist commercially. The evidence comes from two places: what Apple has said publicly, and what developers have found digging through the iOS 27 code itself.
On the public side, Apple used its WWDC26 developer conference to explain a new concept called app “resizability.” During the Platforms State of the Union session, Apple noted that iPhone apps are now showing up on more screens than ever, and that when they do, people expect apps to actually take advantage of the extra space rather than just floating in a tiny box in the middle of a big screen. Apple’s answer, according to a writeup from Stuff magazine covering that session, is to make iPhone apps responsive by default by going forward, stretching and reflowing to fill whatever space they’re given.
That sounds great in theory. In practice, it only applies to apps that are actually built and compiled against the newer SDK. Older apps, the millions already sitting in the App Store, don’t automatically gain this behavior. Developer Sam Henri Gold, digging through the iOS 27 code, found direct references to strings like foldState and angleDegrees buried in the frameworks, things that only make sense if a device physically folds around a hinge. There’s also a new system key that reports the total number of built-in displays on a device, something no current iPhone would ever need unless a folding model with more than one usable display area was coming.
So the resizing conversation isn’t speculation dressed up as fact. It’s baked directly into code Apple has already shipped to developers, well before any hardware announcement.
The “Stretchy Apps” Approach, and Why It’s Not the Same as Getting iPad Apps
Here’s where a lot of the frustration is actually coming from, and it’s worth understanding clearly, because it’s different from what a lot of people assumed Apple would do.
For years, the assumption among Apple watchers was that a folding iPhone would essentially run iPad apps on its larger inner screen when unfolded, since iOS and iPadOS share so much underlying code already. That would’ve been the clean solution. Instead, based on what Apple showed at WWDC26, the current plan looks more like making regular iPhone apps stretchy, meaning they resize and reflow within their existing iPhone-style layout rather than switching over to a full iPad-style multi-column interface.
Early testing backs this up. One developer, testing on the iOS 27 beta using iPhone Mirroring resized to arbitrary dimensions, found that Apple’s own Weather app adapts nicely, spreading its dashboard of panels and widgets across the larger simulated screen. But Settings and a custom test app also switched into what looked like proper iPad-style layouts after being recompiled, while Apple Music strangely did not, at least in that early beta build. Control Center, when summoned from within a resized app, only appeared at its original small size, leaving half the screen blank and cutting off some of the bottom controls. The person testing this specifically noted that this is clearly unfinished and that Apple will likely fix it in future betas, but it shows how much is still being figured out this close to launch.
The Android Precedent Nobody at Apple Can Ignore
If you want a preview of exactly how messy this can get once real hardware and real third-party apps are involved, you don’t need to imagine it. Samsung and its competitors have been experiencing this exact problem for years.
Reviewers testing recent Android foldables have flagged this as an ongoing, unresolved issue. One reviewer testing the Galaxy Z Fold 8 specifically called out apps failing to dynamically scale when switching between portrait and landscape as a widespread frustration, noting that while Google’s own native apps like Gmail and YouTube reorganize themselves cleanly, the vast majority of third-party apps simply don’t, and that this is a shared complaint across virtually every Android foldable tested, not just one particular model. That same reviewer argued Apple’s real opportunity with its own foldable is to make app scaling invisible, so apps default into proper multi-column, tablet-optimized layouts rather than just stretching to fill space awkwardly.
And it’s not only a review-site observation. Real owners are living this too. One Galaxy Z Fold 7 owner posted in Samsung’s own community forum describing a specific, ongoing frustration: certain apps, including Facebook and their Ring doorbell app, simply wouldn’t auto-rotate properly when the phone was unfolded and held in landscape, forcing them into an awkward portrait layout on a screen that was clearly meant to be used wide. They noted this hadn’t been a problem on their previous Z Fold 6, meaning it wasn’t even a universal foldable limitation, just an inconsistent one that varies release to release and app to app.
This is the exact same category of problem developer and analyst chatter is now worried about for the iPhone Fold, except Apple gets the benefit of watching Samsung eat this pain publicly for years first.
App Resizing Approaches Compared: What Apple Is Attempting vs. What Android Foldables Actually Deliver
Since this is really confusing given how much of it is still theoretical on Apple’s side, here’s a breakdown of the two approaches side by side, based on what’s actually been demonstrated versus what’s been promised.
| Approach | Native first-party apps | Third-party apps | Orientation handling | Current maturity |
|---|---|---|---|---|
| Apple’s iOS 27 resizability (iPhone Fold, unreleased) | Adapts well in early betas (Weather, Settings) | Requires developers to rebuild against new SDK, unclear timeline for adoption | Still being finalized, some inconsistencies even in first-party apps like Music | Pre-release, actively changing between betas |
| Samsung and Android foldables (shipping today) | Google’s native apps (Gmail, YouTube) reorganize cleanly | Most third-party apps do not scale properly, a widely reported ongoing complaint | Inconsistent, varies by app and even by device generation (works on one model, breaks on the next) | Mature ecosystem, years of iteration, still unresolved for many apps |
| Legacy iPhone apps not rebuilt for iOS 27 | Not applicable, Apple controls these directly | Will likely default to a fixed size or letterboxed view rather than resizing | No dynamic behavior expected without a rebuild | Effectively the “old” behavior carried forward |
Looking at that table honestly, Apple isn’t starting from zero and it isn’t starting with a magic solution either. It’s attempting to force the issue by mandating resizability as a default for new builds, while Android’s ecosystem has spent years hoping developers would voluntarily adopt better scaling and getting mixed results. Apple’s deadline-driven approach might actually produce more consistent results faster, since Apple has also confirmed that eleven apps are compiled against the newer SDK, the system will automatically stop letterboxing unfamiliar screen sizes, a safety net that’s existed for every previous new iPhone screen dimension. That’s a real forcing function most Android manufacturers never had the leverage to impose on their own developer ecosystems.
Why Developers Are Nervous, and Why Some Users Think Apple Is Underestimating This
I want to give real space to the skeptics here, because their argument is a good one, not just internet noise.
One recurring argument showing up in forum discussions is that Apple’s biggest challenge with a foldable was never going to be the hardware or component sourcing, it was always going to be the software ecosystem, since every existing iPhone and iPad app has to be updated to gracefully handle multiple screen sizes and the ability to change size in real time as the device physically folds and unfolds. One commenter pointed out that Android has had roughly seven years of foldable devices to mature its app ecosystem, and while there are now plenty of apps that support foldables reasonably well, Apple is starting essentially from scratch on this specific front, since there’s currently no commercially available Apple foldable hardware for developers to have been building against.
Another commenter pushed back on the idea that this transition will be dramatically harder for Apple than it was for Android, arguing that iOS developers will simply have to do the same rebuilding work Android developers already did, and that Android apps didn’t magically scale to foldable screens either, developers had to manually resize bitmap assets and reposition interface elements to make it work. That’s a fair counterpoint. The work is comparable in kind. Whether Apple’s tooling and SDK deadlines get it done faster and more consistently than Android managed is genuinely an open question right now, not something either side can prove yet.
What This Means If You’re Already Anxious About Buying One
If you’re the kind of person already mentally budgeting for an iPhone Fold, here’s the honest, unglamorous truth based on everything above. Expect a rocky first year for third-party app support, almost certainly. Apple’s own apps will likely be in reasonably good shape at launch, since Apple controls those directly and has clearly been testing them internally already. Big, well-resourced developers, banking apps, major social platforms, will probably follow within the first several months. Smaller, less actively maintained apps, the ones you use daily but that haven’t been updated in a year or two, are the ones most likely to look awkward, stretched, or plain broken on the larger unfolded display for a while.
Is Apple Actually Behind Here, Or Just Being Cautious?
I go back and forth on this, honestly, and I don’t think there’s a fully satisfying answer yet. On one hand, Apple clearly saw Samsung’s multi-year struggle with foldable app scaling play out in public and had every opportunity to learn from it before writing a single line of iOS 27’s resizability code. That should count for something. On the other hand, being aware of a problem and actually solving it are different things, and Apple’s own early betas still show inconsistencies, like Apple Music not switching into the iPad-style layout that Settings and other apps do, which suggests even Apple’s internal teams haven’t fully ironed this out yet, let alone the broader third-party developer world.
Some people will tell you this is standard pre-launch beta noise and it’ll all be sorted by the real time hardware ships, and there’s a real chance they’re right. Apple has a track record of solving software transitions ahead of hardware launches, having done something similar with Mac, iPad, and Vision Pro in the past. But I don’t think that history guarantees a clean landing here, because the app ecosystem problem is fundamentally different in scale, this isn’t Apple’s own software needing to adapt, it’s millions of third-party apps built by developers with wildly different levels of ongoing maintenance and interest in rebuilding for a device most of them haven’t held in their hands yet.
FAQ: Common Questions About iPhone Fold App Resizing
Is the iPhone Fold already out, and are people complaining about apps not resizing? No, the iPhone Fold hasn’t launched as a real product yet. What exists right now are developer betas of iOS 27, leaked framework code referencing fold-related features, and Apple’s own WWDC26 presentation on app resizability, all of which point toward this being a real challenge Apple is actively working through ahead of any official hardware launch.
Will all my current iPhone apps automatically work properly on the iPhone Fold? Likely not right away. Based on what Apple has said, apps need to be rebuilt and compiled against the newer SDK to gain automatic resizability. Older apps that aren’t updated may default to a fixed size or a letterboxed view instead of properly filling the larger unfolded screen.
Why does the Galaxy Z Fold’s app scaling problem matter for the iPhone Fold? Because it’s the closest real-world preview available of what Apple is up against. Reviewers and current owners of Samsung’s foldables have reported ongoing, inconsistent app scaling problems for years, even with a mature ecosystem, which this suggests is a genuinely hard software problem rather than something either company can casually smooth over.
When will we actually know if iPhone Fold app resizing works well? Realistically, not until real hardware ships and enough third-party developers have had time to test and update their apps against it. Early betas and developer previews give hints, but the true test will come once ordinary users are using ordinary third-party apps on a physical folding device day to day.
Where I Land on This, For Now
I’m genuinely curious rather than pessimistic about this, and I think that’s the honest place to be given how much is still unfinished. Apple’s forcing function, no more automatic letterboxing once apps target the new SDK, is a smarter structural move than anything Android manufacturers have managed to impose on their own developer base. But watching Apple’s own apps behave inconsistently in early betas, Music not adapting the way Settings does, tells me this is still very much a work in progress internally, not a solved problem waiting for hardware to catch up. If you’re planning to buy an iPhone Fold whenever it actually arrives, go in expecting the apps you use every single day to look a little awkward for a while, and don’t be surprised if it takes a solid year of updates before the third-party app experience feels anywhere close to as polished as Apple’s marketing will inevitably make it look on stage.
Table of Contents
