Skip to content
Mobile experience

Checking mobile readability before opening a game

Check text size, navigation and screen orientation on your phone before opening a game, and record useful details when a page is hard to use.

Published 21 10 月 2026

Orange phone illustration with an M2 icon and a question mark

Check the page before the game

A comfortable mobile session starts with a screen you can read. Open the page at a normal viewing distance and make sure its title, navigation and main button are visible. If a browser toolbar changes the available height, let the page settle before tapping. An attractive illustration is not evidence that every game supports every phone.

Make small text readable

Use the browser’s normal accessibility or zoom controls when text is too small. Chrome on Android provides page zoom, although menu wording can vary with the version. After changing the view, check that you can still reach the menu and return to the page. Do not assume a game inside a separate frame will respond exactly like the surrounding website.

Check orientation and controls

Controls after changing orientation

If you rotate the phone, look again for close, back and information controls. Keep important buttons above the phone’s own system controls and avoid tapping while an overlay is moving. For a rules screen, read at your own pace rather than repeatedly opening and closing it. Close a popup with its visible close button before navigating elsewhere.

Keep the access routes clear

The M2 App page describes mobile access, while the game categories help you choose what to browse. Those are different tasks. Follow the existing site buttons for the relevant route; this article does not supply an APK file or promise that installation starts immediately. Keep the account and support routes separate from downloads.

Describe a display issue precisely

For a useful support enquiry, note the page, phone model, browser version, orientation and what is obscured. Say whether the problem occurs before opening a game or inside it. Do not include passwords or one-time codes in a screenshot. If essential controls remain inaccessible, stop using that view and seek clarification before continuing.

Useful site pages

Reference sources

Back to the blog