Plan cross-browser and cross-device compatibility testing
A prioritized browser and device test matrix, tooling choices, and checklist so your site or app works for your real users.
The prompt
Help me plan compatibility testing for my website or app across browsers, operating systems, and devices.
Product: [website / web app / hybrid or native mobile app, tech stack]
Who uses it: [ANALYTICS SPLIT by browser, OS, device, screen size - or "unknown"]
Must-support list (if any): [contract or policy requirements]
Team and budget: [testers, automation experience, tool budget]
Release cadence: [e.g. weekly]
Known problem areas: [e.g. "Safari date pickers", "older Android WebView", "small screens"]
Give me:
1. A support policy: tiers (Fully supported / Functional / Not supported) with criteria, based on my analytics or, if I have none, sensible defaults marked [CONFIRM WITH ANALYTICS].
2. A test matrix table: Browser/OS/device | Tier | Manual or automated | Frequency (every release / monthly).
3. What to test: layout and responsiveness, forms and input types, fonts, media, JavaScript and CSS feature support, touch vs. mouse, accessibility with built-in screen readers, performance on low-end devices, and app store OS-version requirements for native apps.
4. Tooling options: local browsers and emulators, cloud device labs, and automated end-to-end frameworks that run across engines, with trade-offs rather than one forced pick.
5. Prevention: feature detection, progressive enhancement, browserslist/polyfill config, and linting for unsupported features.
6. A bug report template for compatibility issues (environment, steps, screenshot, expected vs. actual).
7. A pre-release smoke-test checklist that takes under 30 minutes.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Software Development prompts
What to fill in
- website / web app / hybrid or native mobile app, tech stack
- contract or policy requirements
- testers, automation experience, tool budget
- e.g. weekly
- CONFIRM WITH ANALYTICS
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Plan a feature flag rollout and rollbackDesigns a staged release behind a feature flag, with audience steps, metrics to watch, kill criteria, and flag cleanup.
- Analyze logs to find what went wrongReads logs to identify errors, patterns, and the likely root cause.
- Get a beginner-friendly code review of my first projectA ranked set of the five improvements that matter most, explained simply, plus what you did well and what to learn next.
- Plan a touchscreen UI for an ESP32 or other microcontrollerA memory-aware screen design, library choice, and code structure for a display-based embedded project.