IM7 Game — Using casino and live-game screens on a phone

Screen space can hide context

A desktop view can show a room name, rules panel and history side by side. A phone may place those items behind separate controls or below the visible area. A number or button can therefore appear without the label that explains it. Before interpreting the display, identify which panel is open and whether another part of it is off-screen.

Scroll the relevant panel rather than assuming the page has ended at the bottom of the phone. An overlay may have its own scrolling area while the background stays still. Look for the title or close control that identifies the overlay. This helps distinguish the game's information from a browser message or an account dialog placed above it.

Orientation changes presentation, not the rules

Turning a phone can rearrange the video, controls and information panels if the interface supports it. That visual change does not establish a new game variant or a different round. Keep track of the room and round identifiers when comparing views, especially if the layout changes during a live presentation.

If a control disappears after rotation, inspect menus and the visible area before concluding that the function has been removed. Some interfaces prioritise the video in one orientation and the controls in another. This is a possibility to check, not a promise about IM7. The actual application's supported layout determines what can be displayed.

A touch should be interpreted through its confirmation

On a small screen, it can be difficult to tell whether a touch selected an item, opened information or submitted an action. Read the response that follows. A highlight can indicate a current choice without proving acceptance. A loading indicator can indicate work in progress without establishing completion.

Avoid repeated taps while the status is unclear. Instead, inspect the relevant confirmation or history when the interface responds. The point is to reconstruct what the service recorded, not to infer it from how many times the screen was touched. For the stages between a choice and a record, see the IQ7 action-confirmation guide.

Keep browser controls separate from game controls

A browser's back button, refresh control and download prompt belong to the browser environment. A room exit, rules button or account sign-out belongs to the service. Their effects can be different even when they appear near one another. Returning to a previous browser page does not necessarily explain the status of an accepted game action.

When following an IM7 access link, read the destination and the information it provides about browser or application access. A download label alone does not establish compatibility or package identity. Use the service's stated installation information rather than treating the directory icon as technical evidence about a file.

Distinguish a slow stream from an account failure

A live video can pause while other parts of an interface remain responsive. A full page can also fail before the account opens at all. These symptoms point to different parts of the experience. Note whether the problem affects the stream, a single room, the rules panel or the whole sign-in process.

After reconnecting, review the relevant record before interpreting the last visible frame. A paused image is a snapshot of what reached the device, not a complete record of what the service processed. If a round continued during the interruption, its history is more useful than a remembered animation.

Describe a mobile display issue clearly

Record the device orientation, the affected screen and the action immediately before the problem. State whether the issue occurs in the browser or the application, if that distinction is known. A description such as “the rules panel opens but its lower text cannot be reached in portrait view” gives more useful context than “mobile is broken.”

For an account or result issue, add the relevant reference rather than sharing access secrets. The IY7 change-review guide is useful when the display started behaving differently after an update. An interface change should be described separately from an unexplained account movement, even when both were noticed during the same visit.

IM7 phone questions

Does rotating the screen start a new round?

The orientation change alone does not establish that. Use the game's round and entry records to determine what activity occurred rather than inferring it from the rearranged view.

What should I record if only the dealer video freezes?

Note the room, the time and whether the account controls still responded. Keep any relevant round reference so the service can distinguish a stream display problem from an accepted-action question.