Dev.to WebDev πŸ›  Dev πŸ‘ 0 πŸ“– 4 min read

Your AI agent copied the web page onto iOS. Start from the platform.

Say you already have a web tool at example.com for logging a site visit, and you ask your AI agent for the iOS screen. The reply is the web page, transplanted: a left sidebar, hover-only extra actions, and a floating but

Say you already have a web tool at example.com for logging a site visit, and you ask your AI agent for the iOS screen. The reply is the web page, transplanted: a left sidebar, hover-only extra actions, and a floating button copied from another platform. On a phone held in one hand, the sidebar is gone, and so are the actions that lived on hover.

The agent copied a familiar surface onto the wrong platform.

This is a fictional illustration of how Design Decision Method handles platform guidance, not a case study or a measured result. The product details below are invented for the example.

Start from the platform you are actually building

The live docs already put the device in establish context. When choosing a visual system, they say to keep a system the project already has, and when it has none, to select from the platform. For other web work, the fallback is Material 3. Borrow an interaction pattern when it solves the task. Do not copy another organization's branding.

The docs are plain that this is not a ranking: the procedure routes work across Material 3, platform guidelines, and a project's own rules, among other sources, and does not rank those sources or copy their branding.

What the live introduction does not spell out is how that choice changes on iOS versus Android versus the web. That detail lives in the agent procedure.

What the procedure actually selects

If a suitable existing system, brand, or platform direction is already in place, the procedure says to retain and extend it. A new iOS screen is not automatic permission to invent a second identity.

When there is no existing system, the procedure gives conditional rows, not a favourite:

  • For a native Apple interface, use Apple's Human Interface Guidelines and system controls for the supported OS and SDK. Do not mandate the newest material or an OS upgrade.
  • For Android or Compose, use Material 3, and only use Expressive options where the brief or project calls for them and the installed library supports them.
  • For other web or cross-platform work, Material 3 is the fallback, with implementation support checked.

The routing guidance is just as direct for a native mobile screen: use the platform's guidance for navigation and controls. Avoid mimicking one platform's material on another.

A short note for the example.com iOS screen might look like this:

Platform: A native iOS screen, not a wrapped copy of the website.
Keep: The product's existing brand colour roles, if they already exist.
Follow the platform: System navigation and controls for the supported OS and SDK. Every action that existed on the web stays reachable without hover.
Do not copy: The web sidebar, hover-only overflow, or a floating action pattern brought over from another platform.
Do not add: A new visual material the brief did not ask for, or a required OS upgrade.

Choose the visual system still starts with what the project already has. Platform selection is the next question: which conventions this surface should actually follow.

Brand can travel. Chrome often should not.

Choosing the visual system is separate from borrowing an interaction pattern. The procedure's visual-system reference adds a practical split: native platform conventions can coexist with brand typography and imagery when behaviour stays coherent. The site-visit log can keep its colours. It should not keep a sidebar that iOS does not use, or actions that disappear without a pointer.

The same split runs the other way. A later Android screen should not be dressed in iOS chrome to look "consistent." A web page should not assume a gesture that only exists on a phone. Rebuild the pattern in the target stack β€” meaning, behaviour, focus, and feedback β€” instead of pasting another platform's markup.

Structure each view already asks the agent to adapt the layout to the device without dropping a capability the task needs. Hover-only actions on an iOS screen fail that test.

Keep it proportional

Name the platform, keep a suitable existing brand, and write down the conventions you will not transplant. The method is a shared procedure, not mandatory for every small edit. It does not claim this saves time. That has not been measured. It also does not guarantee a better native screen. What it gives you is a place to catch a copied surface before it ships on the wrong platform.

Try it

Design Decision Method is a lightweight design decision workflow for developers building interfaces with AI agents. It follows the open Agent Skills format and is MIT licensed. Install paths for Claude Code, Cursor, Gemini CLI, and Codex are in the README.

πŸ“° Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.