How we select and check iPhone Duo apps

What the labels mean

Label	What it establishes	What it does not
Apple-showcased	Apple publicly named and demonstrated a third-party app’s Duo use case.	A specific shipping build or our own device test.
Apple system app	Apple demonstrated the app as part of a system workflow.	That every device state, account or region behaves identically.
Developer preview	A developer describes a specific workflow in public product documentation.	An Apple showcase, a shipping release, a Duo-adapted layout or our own hands-on result.

The directory distinguishes these three labels. The Dashow preview is included under Beyond the fold, not certified as Duo-adapted. “Not listed” is not another word for “not compatible.” The compatibility guide explains why.

One claim, one scope

Apple’s preview supports Netflix’s outside Clips and expanded inside viewing. It does not establish a measured streaming resolution. A generic Netflix support page can establish an iOS plan requirement; it cannot certify the Duo layout. We place sources beside the claims they actually support.

Sources are ranked by directness: a platform or developer statement first, then a reproducible test with recorded versions. Third-party reporting can point at a primary source, but it does not turn a speculative detail into a verified capability.

How a profile is produced

Identify a specific task that benefits from the display or device state.
Record the primary source, check date and exact claim scope.
Write an app-specific explanation and a repeatable test plan.
Check links, arithmetic, metadata and consistency against the recorded source.
Publish the scope and the related next steps.

AI-assisted research, drafting and code checks are part of the production workflow. They are not represented as independent human review or hands-on testing. Corrections can be submitted against any claim. We do not invent reviewers, ratings, usage counts or device-test records.

What a hands-on entry would require

A future test must record the app build, iOS build, device or Simulator, date, screen states and observed outcomes. A Simulator result remains a Simulator result. A single successful task is not blanket certification for the whole app.

The public test record separates checks performed from pass or fail outcomes. A source-based profile will not automatically become “tested” when the device reaches retail availability.

Original illustrations

Artwork on this site illustrates tasks and layouts. It is not a product screenshot. The 3D mockup studio draws a supplied model as a visual asset; its geometry is not used to assert shipping dimensions, and every render it exports is an illustration.

Dates and corrections

Published dates indicate when content was created for this edition. Modified dates change after a substantive edit, not on every build. Source checks have their own dates. The change log records meaningful additions and corrections.

Send the page URL, the disputed sentence and a supporting source. Suggestions are reviewed before publication. App links do not use affiliate tracking in this build; a promotional request does not establish app compatibility or comparative performance.

Sources before adjectives.