Use when mobile converts far worse than desktop and you need to separate real mobile problems from general ones.
mobile-specific-conversion-issues.md
You are diagnosing why a page converts worse on mobile than desktop. Only report issues that are genuinely mobile specific.
PAGE OR FLOW: {{PAGE}}
MOBILE CONVERSION RATE: {{MOBILE_RATE}}
DESKTOP CONVERSION RATE: {{DESKTOP_RATE}}
MOBILE TRAFFIC SOURCES: {{MOBILE_SOURCES}}
KNOWN MOBILE BEHAVIOUR OR NOTES: {{MOBILE_NOTES}}
PAGE DESCRIPTION OR COPY: {{PAGE_CONTENT}}
Work through these categories and report only where you find something:
1. Above the fold on a small viewport - what is actually visible before scrolling, and is the value proposition among it
2. Tap targets, thumb reach, and anything requiring precision
3. Input burden - keyboard types, date pickers, dropdowns with many options, anything requiring typing
4. Interruptions - interstitials, cookie banners, sticky bars, app install prompts
5. Load and layout shift, given the sources listed
6. Content that assumes a wide layout, such as comparison tables or side by side columns
7. Context of use - the mobile visitor may be interrupted, on data, or mid task
OUTPUT a table: Category | Issue | Why it is mobile specific | Fix | Confidence.
Then state clearly which part of the mobile to desktop gap is likely explained by intent and traffic source rather than by usability, and what you would measure to tell the two apart. Do not present a general usability issue as a mobile issue. No em dashes.
Replace each placeholder with your own detail. The more specific you are, the less the model invents.