iOS developer CV skills for foldable apps in 2026

Why does the iPhone Duo change what belongs on your CV?

Apple's first foldable iPhone, the iPhone Duo, went on sale on 23 October 2026 at $1,999 with a 7.6-inch inner display and a 5.4-inch outer screen — and that single device turned adaptive layout from a nice-to-have into a named line item in iOS job ads. More than 2,000 developers attended Apple's Duo-focused workshops ahead of launch, and over 50 apps shipped custom foldable interfaces on day one, Netflix, Microsoft Word and Zoom among them. Optimised apps carry a "Made for iPhone Duo" badge on the App Store. When a platform holder creates a badge, product managers start asking for it, and recruiters start screening for the people who can earn it.

The app roundups that followed launch week made the point better than any spec sheet. The apps that got attention weren't the ones that merely resized without breaking — they were the ones built around the fact that there are two screens of different sizes. A retro cassette player that turns the folded device into a Walkman. A flight tracker with a tent-mode view for the tray table. Virtual notebooks that use the fold as a spine. Even a digital toaster. Every one of those is a design decision made possible by posture, not a layout fix. That distinction is exactly what a hiring manager is probing for in a screening call.

Here's the part job seekers underrate. A new device category rewrites the keyword list your CV gets matched against, and it happens fast. Job ads posted this quarter are already asking for iOS 27 Split View, fold and unfold transitions, and scene lifecycle work — phrases that didn't appear in mobile postings a year ago. Applicant tracking systems match on the literal terms in the ad, so a CV that says "built responsive interfaces" scores nothing against a requirement that says "adaptive layout across size classes". Same skill, different words, and the words are what gets read first.

Which iOS developer CV skills matter most for foldable apps?

Four skill clusters carry the most weight right now: adaptive layout, scene and window handling, state continuity across posture changes, and multi-posture testing. Adaptive layout is the foundation, and in iOS 27.1 it has specific names. SwiftUI's ArrangementView — UIArrangementViewController in UIKit — arranges a primary and secondary view by configurable rules, switching between side-by-side and stacked presentations. Reserved regions let you ask the geometry proxy where the fold sits, so content never lands across the crease; the fold reports as a division region, active only when folded and zero-width when flat. If you've used these, name them. If you've used size classes and AnyLayout to get the same result, name that instead.

Scene and window work is the second cluster, and it's where senior candidates separate themselves. The Duo supports multiple simultaneous scenes on the inner display, the way an iPad does — but new windows can only open on the inner screen, never the outer one, so your code has to handle a scene request that fails rather than assume it succeeds. Content on the outer display goes through the system-controlled scene accessory mechanism, with the system deciding whether it appears at all. A bullet that says you migrated a multi-window app and handled unavailable-scene paths gracefully tells a hiring manager far more than "familiar with foldables" ever could.

State restoration is the third, and honestly the most valuable thing on this list. When a user unfolds mid-task, the scene resizes, and anything you derived from a fixed screen size goes wrong — which is why Apple's own porting guidance pushes teams off UIScreen.main and onto view or window bounds. Audit work here covers hard-coded frames, manually computed coordinates, custom tab bars, modal sizing, keyboard handling and third-party UI components. The fourth cluster is testing across postures: folded, unfolded, tent, partially open, Split View alongside another app. Say how many postures your test matrix covers. Specifics like that survive scrutiny; adjectives don't.

How do you name adaptive layout skills as keywords a parser will match?

Use the exact term from the job ad, then the API name, then the proof — in that order, in the same bullet. Parsers and recruiters both scan for literal strings, so "adaptive layout" and "size classes" need to appear as written, not implied by a description of what you built. A working bullet reads like this: "Rebuilt the browse screen with ArrangementView and reserved regions so content never crossed the fold; adaptive layout across both displays shipped with the iOS 27.1 release, no device-specific branching." One sentence, four matchable keywords, and a claim a tech lead can interrogate in an interview.

Keep the terminology precise, because precision is itself a signal. Foldable-aware layout is not the hinge API. SwiftUI's onHingeChange and UIKit's UIHingeInteraction report hinge status — closed, partially open, fully open — plus a continuous angle, and Apple is explicit that they're for interactions driven by physical movement, not for computing frames. Here's my contrarian take: a CV that lists the hinge API as its headline foldable skill reads as a weaker candidate than one that lists arrangement and reserved regions, because it signals you reached for the showy API instead of the correct one. Interviewers at iOS-heavy teams notice that inversion immediately.

Spread the keywords rather than stacking them. A skills block that reads "SwiftUI, UIKit, size classes, ArrangementView, reserved regions, scene lifecycle, Split View, state restoration, snapshot testing" is fine as an index, but each term should also appear once inside an experience bullet with context attached. Screening tools weight the whole document, and humans trust a term more when it sits next to an outcome. If you're rebuilding the document from scratch rather than patching a 2023 version, an AI CV builder that keeps the structure ATS-friendly will hold the single-column format that parsers read cleanly while you focus on the wording.

What shipped example proves you can build for a foldable?

One shipped artifact beats a paragraph of API names, and it doesn't have to be a famous app. A single screen you adapted in a production release, a TestFlight build with a posture-aware feature, or a weekend project in the App Store all qualify — what matters is that someone other than you can open it. Remember that the app which drew the most attention in Duo launch coverage started life at a hackathon, built by an indie developer who turned the folded device into a cassette player. Scope was small. The idea used the hardware. That's the bar, and it's lower than most candidates assume.

Write the example up in three moves: what the posture made possible, which API carried it, and what changed as a result. "Added a folded-state now-playing view using a scene accessory so users could skip tracks without unfolding; session length on the outer display rose over the first month post-launch" works because every clause is checkable. Avoid the trap of describing the feature's charm instead of your engineering. Hiring managers for mobile roles have spent the past month looking at clever Duo apps; they're no longer impressed by novelty on its own. They want to know whether your layout survived a resize and whether your state came back intact.

If you have no foldable work yet, say what transfers and be straight about it. iPad multi-window, Stage Manager, Split View, trait collections, snapshot tests across size classes — all of it maps directly, and teams know it. An honest line like "adaptive layout experience from iPad windowing; currently porting a side project to the iOS 27.1 arrangement APIs" reads as credible and current. For the rest of the document, the standard engineering CV rules still decide whether anyone reads that line at all — stack section parsed correctly, commits and incidents written as measurable bullets. A role-specific walkthrough of what an engineer's CV has to clear on the first screen covers that groundwork.

How do you tailor a mobile developer CV to each 2026 job ad?

Tailor by extracting the ad's own vocabulary and checking your CV contains it, in context, before you send. Read the posting and pull out the framework split it names — production SwiftUI and UIKit together is the common 2026 ask — plus the oldest iOS version supported, the architecture pattern, the concurrency expectations, and any foldable or resizable-window language. Then confirm each one appears somewhere in your document. An ad that mentions "fold and unfold transitions" wants to see that phrase; an ad that says "size classes" wants that one. This takes fifteen minutes per application and it's the highest-return fifteen minutes in a mobile job search.

Watch the deployment-target reality too, because it's an easy trap. The arrangement, reserved-region and hinge APIs are iOS 27.1 and later, so a team whose floor is iOS 24 can't use them yet and will value your size-class and AnyLayout work far more than your knowledge of the newest containers. Read the ad for that floor and lead with whichever matches. Showing you can build adaptive interfaces without the latest APIs is a genuine senior signal — early Duo reviews pointed out how few apps were fully ready at launch, and a lot of that gap is legacy support constraints, not laziness.

Then verify the file itself, not just the wording. Pasting the job description into an analysis tool and getting back the missing skills, the score and the ATS-compatibility read is faster than guessing, and it catches the mismatch you can't see in your own draft. HRLens gives you a score out of 100 free, with five category scores covering experience, tech stack, impact and ownership, clarity and structure, and ATS compatibility. Paste the ad text rather than a link for LinkedIn or Indeed listings, since those sites block fetching. You can check your CV against the job ad for free before you apply, which is the point where tailoring stops being guesswork.

Frequently asked questions