What is compatibility testing?

Compatibility testing checks that your product works correctly across the browsers, devices, operating systems, screen sizes, networks and other software your users have. It finds problems that only appear in certain environments.

Which browsers and devices do you test?

The ones your users actually have. We build a matrix from your analytics and markets, usually covering recent versions of Chrome, Safari, Edge and Firefox, recent and older iPhones and Android phones, and the desktop operating systems you support.

Do you test on real devices?

Yes. We test the most important combinations on real devices and use device clouds such as BrowserStack, Sauce Labs and LambdaTest for wider coverage. Emulators and simulators are used for fast checks during development.

How many browsers and devices should we test?

Enough to cover most of your users, not every device on the market. A tiered matrix with must-test, should-test and spot-check combinations keeps coverage high and effort reasonable. The matrix builder on this page gives a first suggestion.

What is cross-browser testing?

Cross-browser testing checks that a website or web app looks and works the same across different browsers and versions, such as Chrome, Safari, Edge and Firefox, on desktop and mobile.

What is backward compatibility testing?

It checks that a new version of your product still works with older data, older app versions, older clients and existing integrations, so users who haven’t updated aren’t left behind.

Do you test new OS and browser versions before release?

Yes. We test on beta versions of iOS, Android and major browsers so problems are found and fixed before the update reaches your users.

Do you test on slow or unstable networks?

Yes. We throttle connections to slow 3G or poor Wi-Fi, switch networks mid-task and test offline behaviour, retries and sync.

Can compatibility testing be automated?

Much of it can. Key journeys can run on many browsers and devices in CI using Playwright, Selenium or Appium on a device cloud. New features and visual checks still benefit from manual testing.

Do you test with printers, scanners and other hardware?

Yes, where your product depends on them. We test with printers, scanners, barcode readers, cameras, Bluetooth accessories and point-of-sale hardware as needed.

Do you test plugins and integrations?

Yes. We check your product alongside the platforms and plugins your customers use, such as Shopify, WooCommerce and Magento, as well as browser extensions and desktop software.

A compatibility matrix, a coverage plan, issues logged with exact browser, device and OS details and screenshots, a compatibility report grouped by environment, and an automated suite where agreed.

How is this different from your platform testing pages?

This page covers the compatibility matrix across all environments. Our web, mobile, Android and iOS pages go deeper into each platform’s specific testing.

How do we get started?

Book a call or send the form on this page. We start with a free one-week proof of concept: we build your matrix from your analytics and test one key journey across your must-test combinations.

Compatibility Testing Services

Your users don’t all have the latest iPhone, the newest Chrome or fast Wi-Fi. Your product has to work for them anyway.

We test your product across the browsers, devices, operating systems, screen sizes and networks your customers really use. The matrix comes from your own analytics, the most important combinations run on real devices, and device clouds cover the rest.

Get in touch Build your matrix

Matrix from your analytics
Real devices and device clouds
Automated runs in CI
Free one-week POC

What we do

Your matrixTest what matters Cross-browser testingChrome, Safari, Edge, Firefox Mobile devicesiOS and Android OS versionsEvery supported version Screen sizesEvery width Backward & forwardOld and new together Networks3G, slow Wi-Fi, offline HardwareBeyond the screen Third-party softwareYour ecosystem Servers & databasesUnder the hood Automated runsEvery build

[ Why compatibility testing ]

It works on your machine. Does it work on theirs?

Teams usually build and test on fast laptops, recent phones and the latest browsers. Customers use older Safari versions, budget Android phones, tiny screens and patchy connections. Problems that only show up in those conditions are easy to miss and hard to reproduce. Compatibility testing finds them on purpose, starting with the environments most of your users have.

Need platform-specific depth? See platform testing →

Works for every user

The same experience on the browsers, devices and networks your customers really use.

Focused, not endless

A matrix built from your analytics, so testing time goes where users are.

Ready for updates

New OS and browser versions checked before they reach your users.

Clear evidence

Every issue logged with the exact browser, device, OS and screenshots.

What a compatibility matrix covers

Six dimensions, narrowed down to what your users really have.

Browsers

Chrome, Safari, Edge, Firefox; latest and recent versions

Mobile OS

iOS and Android; newest plus your oldest supported

Desktop OS

Windows, macOS and Linux where relevant

Devices

Phones, tablets and laptops your users own

Screen sizes

Small phones to wide monitors, zoom and text size

Networks

Fast Wi-Fi to slow 3G and offline

[ What we test ]

Eleven areas of compatibility, one matrix

From browsers and phones to printers and servers. Each one lists what we test, when you need it and the problem it prevents.

Compatibility matrix from your analytics

Test what matters

We build your test matrix from real data: the browsers, devices, operating systems and screen sizes your users actually have, not a generic list.

What we test

Analytics reviewed for browsers, devices, OS and regions
Must-test, should-test and spot-check tiers
Agreed minimum supported versions
Matrix reviewed as usage changes

When you need it

At the start, and every few months after.

The problem it preventsTesting dozens of devices nobody uses while missing the ones that matter

Cross-browser testing

Chrome, Safari, Edge, Firefox

View service

Your web app checked on the browsers and versions your users rely on, where rendering and behaviour often differ.

What we test

Latest and recent versions of Chrome, Safari, Edge and Firefox
Layout, fonts, forms and media per browser
JavaScript features and browser-specific bugs
Safari on Mac and iPhone checked on real hardware

When you need it

Before releases and after front-end changes. More in web app testing.

The problem it preventsA feature that works in Chrome and silently fails in Safari

Mobile device compatibility

iOS and Android

View service

Phones and tablets differ in screen size, hardware, OS version and manufacturer changes. We test on the ones your users own.

What we test

Recent and older iPhones and iPads
Android phones from Samsung, Google, Xiaomi and others
Notches, foldables and different pixel densities
Camera, GPS, biometrics and other hardware features

When you need it

Before every app release. More in Android and iOS testing.

The problem it preventsCrashes or broken layouts on the phones your testers don’t own

Operating system & version testing

Every supported version

Your product checked on each operating system version you support, from the newest release to your oldest supported one.

What we test

Windows, macOS and Linux versions you support
iOS and Android versions, including the newest
OS updates and beta releases before they ship
Permissions, settings and system dialogs per version

When you need it

When OS updates arrive and before dropping support for older versions.

The problem it preventsA new OS update breaking your product on launch day

Screen size, resolution & responsive

Every width

Layouts checked at every breakpoint and the awkward sizes in between, plus zoom and text-size settings.

What we test

Small phones to wide monitors
Portrait, landscape and split-screen
High-density and standard displays
Browser zoom and larger text settings

When you need it

For every UI change and new page or screen.

The problem it preventsA layout that breaks just above or below a breakpoint

Backward & forward compatibility

Old and new together

We check that new versions work with older data, clients and integrations, and that your product is ready for upcoming platform changes.

What we test

Upgrades from older app versions with real data
Older clients against new APIs
Files and exports from earlier versions
New OS and browser betas before release

When you need it

Before major releases, migrations and API changes.

The problem it preventsUsers on an older version locked out after an update

Network condition testing

3G, slow Wi-Fi, offline

Not everyone has fast, stable internet. We test how your product behaves on slow, unstable and lost connections.

What we test

Throttled 3G, 4G and slow Wi-Fi
Switching networks and losing signal mid-task
Offline mode, retries and sync
Large images, videos and downloads on slow networks

When you need it

For mobile apps and any product used on the move.

The problem it preventsLost data or frozen screens when the connection drops

Hardware & peripheral compatibility

Beyond the screen

Products that use printers, scanners, cameras, card readers or other devices need testing with real hardware.

What we test

Printers, scanners and barcode readers
Cameras, microphones and headsets
Bluetooth devices and accessories
Point-of-sale and kiosk hardware where relevant

When you need it

For desktop, retail, healthcare and field-service products.

The problem it preventsA product that works until it meets the customer’s real hardware

Third-party software & plugins

Your ecosystem

Your product rarely runs alone. We check it alongside the plugins, platforms and software your customers use.

What we test

Plugins and extensions such as Shopify, WooCommerce and Magento
Browser extensions and ad blockers
Office suites, PDF readers and email clients
Antivirus and security software on desktop

When you need it

For plugins, integrations and products installed alongside others.

The problem it preventsA plugin update that breaks your product on customers’ stores

Database & server environments

Under the hood

For products installed or hosted in different environments, we test on the servers and databases you support.

What we test

Database engines and versions you support
Web and application server versions
Cloud and on-premise environments
Containers and runtime versions

When you need it

For self-hosted, enterprise and on-premise software.

The problem it preventsA release that works in your cloud but fails on a customer’s server

Automated cross-browser runs in CI

Every build

View service

Key journeys run automatically across browsers and devices on every build, so compatibility issues are caught before they reach testers.

What we test

Playwright and Selenium suites across browsers
Appium suites across devices
Runs on BrowserStack, Sauce Labs or LambdaTest
Screenshots and videos for every failure

When you need it

Once your core journeys are stable.

The problem it preventsCompatibility bugs found days after the change that caused them

[ Real devices vs device clouds vs emulators ]

The right mix for each stage

We use all three: emulators while you build, device clouds for breadth and real devices for what matters most.

	What it gives you	Strengths and limits
Real devices	Real hardware, sensors, performance and touch	Most accurate; costly to cover everything
Device clouds	Hundreds of real browsers and devices on demand	Wide coverage; less control over hardware
Emulators & simulators	Fast checks during development	Quick and cheap; not enough on their own

Sample compatibility issueHigh

Environment: Safari 16 · macOS Monterey · MacBook Air
Screen: Booking · choose date
Issue: Date picker opens behind the modal and can’t be selected
Works in: Chrome, Edge and Firefox on the same machine; Safari 17
Impact: High · users on older Safari can’t book
Evidence: Screen recording, console log, browser details

Example only. Real issues are logged in your tracker.

[ How we work ]

Six steps from analytics to a living matrix

You always know which combinations are covered, how, and what still needs attention.

Step 1 of 6
Build the matrix

Your analytics, markets and supported versions turned into a tiered test matrix.

You getCompatibility matrix
Step 2 of 6
Plan the coverage

Which journeys run on which combinations, manually or automated.

You getCoverage plan
Step 3 of 6
Test on real devices

Must-test combinations on real hardware, with device clouds for breadth.

You getIssues with device and browser details
Step 4 of 6
Automate the repeatable

Key journeys running across browsers and devices in CI.

You getAutomated cross-browser suite
Step 5 of 6
Report by environment

Results grouped by browser, device and OS, with screenshots.

You getCompatibility report
Step 6 of 6
Keep it current

Matrix updated as usage changes and new versions arrive.

You getUpdated matrix

Free one-week POCWe build your matrix and test one key journey across your must-test combinations.
Real devices firstMust-test combinations on real hardware, with device clouds for breadth.
Exact details, every timeBrowser, device, OS and version recorded on every issue, with screenshots.

[ Tools ]