Compatibility
Know where it breaks across devices and browsers.
Your players do not all use the phone your team uses. We run the same agreed cases across phones, computers, operating systems and browsers, and document where the layout or the interaction differs.
What we check
- The same agreed cases on each phone, computer, operating system and browser
- Portrait and landscape orientation
- Layout and interaction differences between combinations
What you receive
- An environment matrix
- A result for each combination
- The affected screens
- Steps to reproduce each difference
- A likely cause and suggested fixes from engineers experienced in iGaming
What it looks like
Every finding comes with the evidence behind it.
This is the shape of a single record in your report.
Examples of what this can surface
- A button is cut off on compact phones
- A flow works in one browser and fails in another
- Rotating the phone resets a form
- A layout that is fine on a desktop is unusable on a small screen
CN-UI-03P3
Bonus action label clips on a narrow screen
- Screen
- Promotions › Bonus detail
- Expected
- Action label fully visible
- Observed
- Label clipped on the narrowest phone width; other widths fine
- Environment
- Compact Android phone · Chrome · portrait
- Evidence
- Screenshots across three widths
- Likely cause
- A fixed-width layout assumes a wider screen than the narrowest supported phone.
- Suggested fix
- Use flexible widths and test at the narrowest supported width.
Before we start
We agree the details before any test runs.
What we need from you
- The devices, operating systems and browsers in scope, or your analytics so we can propose a list
- The journeys to repeat on each combination
What we agree up front
- Target market and test location
- The build, accounts and access we will use
- Devices and networks
- Steps and expected results
- Number of attempts, delivery timing and retests
Functional QA does not constitute security testing, game-math validation or certification. Additional work is scoped separately. Likely causes and fixes are our engineers' assessment from observation and experience. Please confirm them against your own logs and code.
Related services
Often run together.
Want this tested in your markets?
Tell us the product, the markets and the journeys that matter. We will come back with a scope and a plan.