Device Information

Device Information combines user agent parsing with screen and touch APIs to summarize whether you are on mobile, tablet, or desktop, which OS family appears, and whether touch input is available.

QA repro steps become reproducible when testers attach a standard device report alongside screenshots.

Mobile-only bugs need proof the tester was actually on touch hardware—not just a narrow desktop window.

Product managers planning PWA features check touch and standalone mode hints quickly.

• Attach device report to mobile layout bug tickets
• Verify iPad vs iPhone detection for responsive nav
• Document kiosk hardware in field deployment guides
• Compare Android WebView vs Chrome on same phone
• Onboard QA contractors with standard report format

1. 1Open the tool on the physical device under test when possible.
2. 2Review device type, OS, screen dimensions, and touch support fields.
3. 3Copy report text for ticket attachment.
4. 4Cross-check with Screen Resolution Checker for viewport specifics.
5. 5Repeat on second device when bug is device-specific.

• Desktop browser DevTools device emulation is not a substitute for real device reports on touch bugs.
• User Agent Parser helps when remote user pastes UA string instead of running this tool.
• Pair with Webcam Test and Microphone Test for full peripheral checklist on video apps.
• Corporate MDM browsers may mask OS version—note managed browser in ticket.

• User agent reduction in modern browsers may hide granular version numbers.
• Spoofed user agents produce misleading summaries.
• Common mistake — resizing desktop browser to mobile width and calling it mobile testing: use real devices.