How to compare device capabilities for a web app

A web app works on one device but not another, or it feels slower on a new computer than you expected. The difference might be hardware, but it could also be the browser, a permission, a display setting, or the network.

Use the System Info test to compare the device details available to a browser. Then check browser features and network quality separately, so you do not mistake one kind of limit for another.

Compare the devices

1. Open System Info on each device in the browser you plan to use for the web app. Note the processor, graphics, screen, battery, and network details that the report shows.
2. Make a short list of what the web app needs. For example, it may need a large screen, a camera, a microphone, a supported graphics feature, or a stable internet connection.
3. Keep the test conditions as similar as possible. Use the same Wi-Fi network, connect or disconnect power on both devices in the same way, and close demanding apps you do not need.
4. Open the web app on both devices and try the same task. Note whether a feature is missing, a control is hard to use, or an action takes longer.
5. If the app depends on a browser feature, open Browser Info on each device and compare the browser version and supported features it reports.

Do not treat the System Info report as a full hardware inventory. Browsers expose only some device details, and the information available can differ by browser and operating system.

What the differences mean

The processor or graphics information differs

This can help explain why a demanding page, animation, or calculation runs differently. It does not prove how fast the web app will be: the browser, power mode, background activity, and the app's own code also matter. If one device feels slow, compare the same action under the same conditions rather than relying on a hardware label alone.

The screen information differs

A screen's reported dimensions do not always match the space available to a web page. Browser zoom, display scaling, a narrow window, or a phone's orientation can change the layout the app sees. If the app is cramped on one device, maximize the browser window and compare it at the same zoom level before deciding that the screen is too small.

The battery or power conditions differ

A laptop or phone may reduce performance when it is in a power-saving mode or running low on charge. Repeat the comparison with both devices plugged in, or both on battery, and use the same power mode where possible. Battery information may not appear on every device because it depends on what the browser reports.

The network details look similar, but the app behaves differently

System information is not a complete test of connection quality. A page can load quickly but still pause during live collaboration if the connection has delays or dropouts. Use the Speed Test to compare download speed, upload speed, ping, and jitter on the same network. Run each test separately and avoid large downloads during the comparison.

A detail is missing or a feature is unavailable

A blank or unavailable detail does not always mean the device lacks that hardware. The browser may not provide it, or a permission may be blocked. For example, camera and microphone access requires browser permission. Some web apps also rely on browser features that are not tied to processor speed or screen size.

How to make the comparison fair

1. Match the power state. On Windows 11, check Settings › System › Power & battery › Power mode. On a Mac laptop, check System Settings › Battery and keep Low Power Mode in the same state for both runs. On Android, check Settings › Battery › Battery Saver; on iPhone, check Settings › Battery › Low Power Mode. Menu names can vary by Android manufacturer.
2. Use the same browser conditions. Compare the same browser when possible, with the same zoom level and a similar window size. If you compare different browsers, record that difference because their feature support and performance can vary.
3. Check permissions. If a camera, microphone, or location feature fails, check the browser's site permissions first. On Windows 11, review Settings › Privacy & security for the relevant device permission. On macOS, check System Settings › Privacy & Security. A site permission and an operating system permission may both need to allow access.
4. Repeat a slow result. Close video streams, file transfers, and other heavy tasks, then try the same web app action again. A single slow run can reflect temporary system or network load rather than a device limit.
5. Compare the actual feature. If the app uses camera capture, audio, or graphics, test that part directly in the app. A general device report cannot confirm that the app itself supports every feature or that its settings are correct.

What the browser cannot tell you

A browser-based report is useful for a first comparison, not a guarantee that a web app will work perfectly. Browsers may show only a rounded hint about RAM instead of the exact installed amount, and a processor label may not reveal its full model or performance. A browser test also cannot confirm that a web app's server, account, or internal code is working correctly.

Use the report to spot meaningful differences, then verify the web app's required features in the browser you will use. If a required feature is missing in Browser Info, try a current browser that supports it before replacing or upgrading the device.