Every year tech media gets excited about the next device category that’s supposedly going to change everything. Foldables! AR glasses! Wearables! Smart displays! And every year, mobile developers face the same question: should we redesign our apps for these new form factors?
Here’s what rarely gets discussed in those breathless product announcements: while you’re optimizing for a foldable that 2% of your users might own, your app probably looks broken on the iPad someone’s grandmother actually uses, renders poorly in split-screen mode on Android, and has an awkward layout when someone tilts their phone to landscape.
After building apps that need to work across every device users actually have, I’ve learned a hard truth: getting the basics right matters infinitely more than chasing the cutting edge. Here’s why responsive layouts still deserve far more of your attention than any new form factor.
The Devices People Actually Use
Let’s ground this in reality. Pull up your analytics. What do you actually see?
For most apps: 60-70% phones in portrait, 15-25% tablets, 5-10% phones in landscape, and maybe—maybe—1-3% foldables or other exotic form factors. The bulk of your users are on “boring” devices that have existed for a decade.
But here’s what your analytics might not show clearly: how many of those users encounter broken layouts? How many people on a standard iPad see your app stretched awkwardly because you designed only for iPhone sizes? How many Android users in split-screen mode see half your UI cut off?
These aren’t edge cases. A tablet in landscape is not an edge case — it’s how millions of people use their iPads daily. Split-screen mode on Android isn’t exotic – it’s a standard feature people expect to work. Font size accessibility settings aren’t niche—they’re essential for a significant portion of users.
Your responsive layout problems affect more users than all the new form factors combined. They’re just silent failures that people work around rather than report.
The Foldable Paradox
Here’s the irony about foldables: if you’ve actually built proper responsive layouts, supporting foldables is straightforward. If you haven’t, adding foldable support won’t fix your underlying layout problems—it’ll just give you more variants to maintain.
Foldables don’t need special magic—they need apps that properly adapt to different screen sizes and aspect ratios. The same principles that make your app work well on phones, tablets, and in multi-window mode make it work on foldables. Master responsive layouts, and foldable support largely comes for free.
I’ve seen teams spend weeks optimizing their app for the Galaxy Z Fold’s unfolded state while their app still looks terrible on a standard iPad in landscape. They’re solving the wrong problem.
The reverse isn’t true. Build a foldable-specific layout without mastering responsive design, and you’ve just created another fixed-size variant that breaks when users resize the window or rotate the device.
We mentioned some of this in more detailed article: Do We Really Need Foldable Phones Anymore?
What Responsive Actually Means in 2026
Responsive layout isn’t just about phone versus tablet anymore. It’s about handling the reality of how people actually use devices.
Dynamic window sizing: On Android, users resize app windows freely in multi-window mode. On iPadOS, Stage Manager means your app might occupy any size from a small side panel to full screen. Your layouts need to reflow gracefully at any width, not just at specific breakpoints.
Orientation changes: People still rotate their phones, especially for media, forms, and games. If your layout breaks in landscape or you force portrait-only, you’re making a choice that frustrates users daily.
Accessibility text sizes: When someone increases their system text size, your carefully pixel-perfect layout shouldn’t explode. Elements should resize appropriately, text shouldn’t truncate, and the UI should remain usable. This isn’t optional accessibility—it’s basic functionality for a huge number of users.
Keyboard and external input: iPads with keyboards, Android tablets with mice, Samsung DeX mode—users increasingly expect desktop-like interactions on mobile devices. Responsive layouts need to accommodate these usage patterns, not just different screen sizes.
These scenarios affect 30-40% of your users easily. Contrast that with even the most optimistic foldable adoption projections.
The Maintenance Burden Nobody Talks About
Every form factor you specifically target creates maintenance overhead. Special layouts for foldables, custom flows for watches, dedicated designs for large tablets—each one is code you need to maintain, test, and debug.
When you change a feature, you need to update it across all these variants. When you fix a bug, you need to verify the fix works on every form factor. When you add a new screen, you need to design and implement it multiple times.
Compare this to truly responsive layouts: you define flexible constraints and let the system adapt. Change your component once, and it works across all sizes. Fix a bug once, and it’s fixed everywhere. Add a new feature once, and it scales automatically.
I’ve seen teams with separate layouts for phones, tablets, and foldables spend 40% more time on UI work than teams with properly responsive layouts that handle all sizes with the same components. The responsive approach isn’t just better for users—it’s more maintainable for developers.
When Small Screens and Large Screens Diverge
This doesn’t mean every screen should look identical at every size. There are legitimate cases where you want different layouts for different contexts—a list view on phones and a grid on tablets, a single column on small screens and multiple columns on large ones, compressed navigation on phones and expanded navigation on tablets.
The difference is whether you’re designing responsive components that adapt fluidly, or creating separate implementations for specific devices.
Good responsive design uses adaptive layouts: components that change their presentation based on available space, not based on detecting specific device models. SwiftUI’s adaptive stacks, Jetpack Compose’s adaptive layouts, and proper constraint-based designs all work this way.
Bad responsive design uses device detection: if iPad, show this layout; if phone, show that layout. This approach breaks down the moment someone uses your app in an unexpected context—and people always find unexpected contexts.
The Real Innovation in Layout Systems
The actually innovative layout work happening in mobile development isn’t about supporting weird new hardware—it’s about making truly adaptive UIs simpler to build.
SwiftUI’s grid system that automatically adjusts column counts based on available width. Jetpack Compose’s adaptive navigation components that seamlessly transition between bottom navigation, navigation rail, and permanent drawer based on screen size. Modern constraint systems that let you define relationships rather than fixed positions.
These tools make it easier to build UIs that work everywhere, not harder to build separate UIs for each device type. That’s the real innovation—reducing complexity while expanding capability.
Developers who master these systems can build apps that handle any screen size with less code than it used to take to support just phones and tablets separately. That’s the kind of advancement that actually matters.
What About AR and Wearables?
You might be thinking: “But what about genuinely different form factors like watches or AR glasses? Those need different UIs entirely.”
Absolutely. And here’s the thing—those contexts are so fundamentally different that they require completely different interfaces anyway. You’re not adapting your phone UI to a watch; you’re building a companion experience with limited, focused functionality.
That’s different from responsive layout work. When someone uses your app on a tablet versus a phone, they expect the same features and capabilities, just better optimized for the screen size. When someone uses your app on a watch, they expect a completely different, simplified experience.
Don’t conflate “different device category requiring a different UI paradigm” with “different screen size requiring responsive layout.” They’re separate problems with separate solutions.
The Boring Work That Matters
Here’s what I wish someone had told me earlier in my career: the boring, foundational work of making your layouts truly responsive pays dividends forever. Every new device that comes out, every new window mode, every new way users interact with their devices—your app just works.
Meanwhile, teams that chase specific form factors are constantly playing catch-up. Foldables arrive, and they scramble to support them. Multi-window mode becomes popular, and they realize their layouts break. Users start increasing text sizes more often, and suddenly their carefully designed screens are unusable.
The developers I respect most aren’t the ones showing off demos of their apps on the latest foldable prototype. They’re the ones whose apps work flawlessly on any device, in any orientation, with any text size, in any window configuration—because they built properly responsive layouts from the start.
The Practical Path Forward
If you’re maintaining an app right now, here’s what to prioritize:
First, audit your app on the devices people actually use. Not the flagship phone in your pocket—the three-year-old mid-range Android phone, the base model iPad, your app in split-screen mode. Find the broken layouts. Fix those first.
Second, test with accessibility text sizes and different orientations. Make sure your layouts adapt gracefully, not catastrophically.
Third, refactor toward truly adaptive components. Replace device-specific layouts with constraint-based designs that adapt to available space. This is the work that scales.
Then — and only then — if you have specific evidence that your users are on new form factors in meaningful numbers, optimize for those. But you’ll find that if you’ve done the responsive work properly, most of that optimization is already done.
The Bottom Line
New form factors make for exciting demos and compelling tech journalism. Responsive layouts make for apps that work properly for millions of users every day.
The developers who understand this distinction spend their time on work that compounds—building foundations that make every future device easier to support. The developers who don’t understand it spend their time chasing the latest hardware, always one step behind.
Your users don’t care whether your app has a cool unfolding animation on a device they don’t own. They care whether it works properly on the device they’re holding right now, in the way they’re using it right now.
Master responsive layouts. The rest will follow.