How to Recreate the iPhone Duo Fold Animation on Android

Apple unveiled iPhone Duo — its first foldable — at the September 9, 2026 keynote covered in explainx.ai's full event recap. One detail from that keynote turned into its own viral moment within a day: the software transition Apple showed as the phone unfolds, where the screen content appears to stay fixed in space while the phone physically reorients around it. By September 10, an Android developer had already rebuilt a working version of that exact effect on a Samsung Galaxy Z Fold 8.

TL;DR

What Apple actually showed

Apple's iPhone Duo demo made the fold transition look almost like a physical illusion: the cover-screen content — icons, the current app — appears to hold its position in space as the hinge opens, with the display content blending smoothly into the larger inner tablet-style screen rather than simply cutting from one screen to the other at a fixed angle threshold. It's a book-style fold (inner tablet panel, outer phone cover), and explainx.ai's iPhone Duo hardware breakdown covers the device's specs, pricing, and finishes in full if you need that context first.

The animation itself isn't a hardware feature — it's software, timed to the phone's actual fold speed via a hinge-angle sensor, which is exactly the property that made it possible for someone outside Apple to reverse-engineer the effect, if not the exact implementation, on a different device within hours.

How the Android recreation actually works

According to reporting on the recreation (Android Authority, 9to5Google), the build combines three specific pieces:

1. Real-time hinge-angle data. The Galaxy Z Fold 8 exposes its internal hinge-angle sensor through an Android API, giving the app a continuous stream of "how open is the phone right now" values as the user unfolds it — not just a binary open/closed state.
2. Android's Presentation API. This is the standard Android mechanism for controlling what content renders on a secondary display — in this case, coordinating what shows on the cover screen versus the inner screen as the fold state changes.
3. A blur shader over two screenshots. Rather than rendering the actual live UI mid-transition, the app takes one screenshot of the cover-screen content and one of the inner-screen content, then uses a shader to blur and cross-fade between them as the hinge-angle value moves — creating the illusion of one continuous scene rather than a hard cut.

The result, per the reporting, holds up well head-on but breaks down at an angle — because it's compositing two static screenshots with a blur effect timed to sensor data, not actually re-rendering a 3D scene that accounts for viewing perspective. That's a meaningful technical distinction from what Apple's own implementation likely does natively at the display-compositor level, where it has full control over how content is drawn during the transition.

Why this can't ship as a real app (yet)

The creator was explicit about the ceiling on this technique: it's a proof of concept, not something installable as a general-purpose app. The reason is a permissions and access problem, not a difficulty problem — applying this effect system-wide, across every app on the phone rather than just inside the demo app itself, requires the kind of display-compositor-level access that only the OEM (Samsung, in this case) has through its own SystemUI. A third-party Android app is sandboxed well short of that level of control by design — the same sandboxing that keeps apps from reading each other's screens or hijacking system animations is exactly what blocks a universal version of this effect from shipping outside of Samsung's own software.

What it would take to build your own version

If you want to explore the same technique rather than waiting for an OEM to ship it, the ingredients are all publicly documented Android APIs:

• Foldable state and hinge-angle data — via Jetpack's WindowManager library, which exposes FoldingFeature state (including angle, where the device supports it) in a standardized way across supporting foldables, rather than requiring a vendor-specific API for every device
• Secondary-display coordination — via the Presentation API used in the original demo, for apps that need to render different content to each physical panel
• A cross-fade/blur shader — implementable with Android's RenderEffect (blur) combined with a custom Shader or a compositing library, applied to two captured bitmaps rather than live content

This gets you the same demo-scope result the original recreation achieved — a convincing effect inside your own app, not a system-wide replacement for Android's default fold transition, which remains gated behind OEM-level access.

Why this specific effect was reverse-engineerable so fast

Most Apple software features that get "recreated" on Android within hours are cosmetic — an icon shape, a color palette, a notification style — because they're visual choices, not novel technical mechanisms. iPhone Duo's fold animation is a different category: it's a timing-driven effect, meaning its entire visual identity comes from being synced to a physical sensor signal (how far the hinge is open, at every instant) rather than from any proprietary rendering technique Apple invented from scratch.

That distinction is exactly why a single developer could get a convincing version working in a couple of hours rather than months. Android already exposes fold-angle data through Jetpack's WindowManager library and gives apps Presentation-API control over secondary displays — the raw materials were sitting in the public SDK the whole time. Nobody had to reverse-engineer Apple's private APIs or decompile iOS; they had to notice that Android's own foldable APIs, aimed at a slightly different use case, could be repurposed to drive the same kind of cross-fade Apple's marketing video showed. This is a recurring pattern in mobile software cloning generally: the fastest recreations aren't the ones copying the hardest engineering, they're the ones spotting that the platform already ships the primitive needed and just hadn't been assembled that way yet.

What Samsung (or Google) would need to change to ship this for real

Turning the demo into an actual Android feature — available system-wide, in every app, not just inside one demo app — requires closing a specific gap rather than a vague "more engineering effort." Samsung's own SystemUI already has the display-compositor access a third-party app is deliberately denied; the open question is whether Samsung (or Google, for a stock-Android version on Pixel foldables) considers a feature like this valuable enough to build and maintain as an OS-level transition, the same way "spatial" fold transitions have shown up in some OEM skins as one-off customization options in past years. Nothing in the public reporting suggests either company has announced plans to do so — this remains, for now, a demonstration of what's technically possible, not a roadmap item either OEM has confirmed.

A security note before you go looking for an APK

Every time a demo like this goes viral, copycat listings claiming to offer "the app" tend to show up on third-party APK sites and sometimes even slip into app stores — trading on a trend before anyone can verify what the file actually does. As of this writing there is no official app, APK, or GitHub repository released by the original creator; the only verified source is the Reddit video linked above. explainx.ai has not tested, downloaded, or verified any file claiming to be this app, and isn't linking to one. If you go looking, treat any "iPhone Duo animation APK" or similar download you find outside of an update from moomanjohnny's own Reddit account as unverified: don't sideload it, don't grant it accessibility or display-overlay permissions, and check requested permissions against what the technique above actually needs (camera roll/screenshot access and a fold-angle sensor reading — nothing that justifies contacts, SMS, or accessibility-service access).

Honest limitations

• This is a per-app demo, not a system feature. Every source covering the recreation is explicit that it doesn't touch Samsung's actual SystemUI fold transition — it's a standalone app faking the effect using screenshots of its own content.
• The angle-dependent breakdown is real. The illusion only holds up viewed head-on; any perspective shift reveals it's a 2D composite, not a true spatial re-render.
• Hardware-specific sensor access. The Galaxy Z Fold 8's hinge-angle exposure isn't universal across every Android foldable — porting this to a different device may require different sensor access depending on what that OEM exposes.
• No public code release found at time of writing. The demo was shared as a video on Reddit; no GitHub repository or installable APK has been published alongside it, based on available coverage.

The takeaway

The iPhone Duo fold-animation recreation is a good example of how fast a specific, well-defined software effect can get reverse-engineered once it's shown publicly — from keynote to working Android demo in under 24 hours, built by one person using entirely public Android APIs (WindowManager's folding-feature data, the Presentation API, and a shader). What it can't do yet is ship as a real, system-wide feature, because that requires OEM-level display access no third-party app gets — which is exactly the gap that separates "a clever demo" from "a shipped Android feature," and the reason nobody should expect this on the Play Store anytime soon.

Related on explainx.ai:

• Apple September 9 Event: iPhone Duo Fold, iPhone 18 Pro, and Ternus's First Keynote — full specs, pricing, and keynote breakdown for the device this animation comes from
• Apple September 9 Event Preview — the pre-keynote leaks that anticipated iPhone Duo's launch
• Tim Cook Steps Down, John Ternus Becomes Apple CEO — the leadership change behind this keynote
• Top 10 AI Tools for Coding — if you're building your own version of this demo, tooling for the Android/Kotlin side

Original source and video:

• Reddit — "Tried to recreate the iPhone Duo animation on my Z Fold 8" — the original post and demo video by moomanjohnny
• Android Authority coverage
• 9to5Google coverage
• TechRadar coverage

This post reflects reporting and the original Reddit demo as of September 10-11, 2026. No downloadable app or public source code was available at time of writing — check the original Reddit thread for any updates from the creator.