Who it is forA Flutter developer whose app needs to run well on iPhone Duo and who has learned that the fold data is not exposed in the usual place.
The problemFlutter's MediaQuery.displayFeatures is documented as populated only on Android, so it returns an empty list on iPhone Duo. Developers may look for fold data there and get nothing.
The outcomeA plan that separates what works in Flutter today from what needs a platform channel to a native iOS layer.
What you need first
- An AI coding agent such as Claude Code, Cursor or Gemini
- Node.js with npx, since the README install uses npx
- An existing app or design to work on, native iOS or a supported cross-platform stack
- For native work, Xcode with the iOS 27.1 SDK, which the README calls the gate for edge-to-edge content, vertical bars, reserved regions and arrangements
Steps
- Run
npx skills add mirzaaghazadeh/iphone-duo-skills --skill iphone-duo-flutter(inferred, check the README) - Run
npx skills add mirzaaghazadeh/iphone-duo-skills --skill iphone-duo-design-review(inferred, check the README) - Ask the agent to read iphone-duo-flutter first, then review your screens with the design review skill.
- Identify any fold-state needs and plan a bridge through platform channels.
- Test your layout on a physical iPhone Duo.
Prompt for your agent
Using the iphone-duo-flutter and iphone-duo-design-review skills from mirzaaghazadeh/iphone-duo-skills, review <path-to-flutter-project> for code that relies on MediaQuery.displayFeatures or other fold data. Output a list of what works now in Flutter and what needs a platform channel, and verify that no suggested fix depends on displayFeatures returning fold data on iOS.
Caveat. The README says neither Flutter nor React Native supports iPhone Duo yet, so bridged features will need native iOS code and testing.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page