Jaiho91: record what disappears when the phone turns sideways

Investigate a Jaiho91 display question with a portrait-to-landscape observation sequence that separates hidden information from changed task state.

A Rules tab appears in portrait view and disappears when the phone turns sideways. The reader wonders whether the rules have been removed. The first useful step is to describe the same page in both orientations. Jaiho91 readers can use this observation exercise to distinguish a change in visible layout from a change in the underlying task. We begin with what the phone actually shows, keeping explanations provisional until the comparison supplies evidence.

Keep the page constant

In our invented example, the portrait page shows a title, a selected Rules tab, an instruction paragraph and a bottom Continue button. The page is at its top position and no keyboard is open. Write those details before rotating. If a later image shows a different tab, a scrolled page or an open keyboard, it is no longer a simple orientation comparison. The baseline allows us to identify those extra changes rather than blaming everything on rotation.

Android's developer documentation recognises orientation as a configuration change and explains that available screen space changes when a device rotates. Apps need to handle that change and preserve relevant state. This technical context explains why layout and state both deserve attention; it does not identify the cause of any particular missing control. For this reader exercise, there is no need to inspect programming code or assume every application handles rotation in the same way.

Turn to landscape once and pause. In the sample, the title remains, the Rules label is replaced by a small menu icon, the instruction paragraph wraps into fewer lines and Continue is outside the visible area. Those are four separate observations. “Everything vanished” would discard the surviving title and paragraph. “Rules deleted” would add a claim about removal that the image alone does not justify. Accurate description leaves several explanations available to test.

Follow the hidden information

Scroll down without selecting another tab. Suppose Continue becomes visible. The control was below the visible area in this sample, not absent from the page. Then return to the top and inspect the menu icon. If its list contains Rules, the label has moved into another navigation presentation. Record that result separately from scrolling. Two missing-looking items can have two different explanations, even though both were noticed immediately after the same rotation.

Now check the task state. Is Rules still selected after opening the menu? Does the same instruction paragraph remain? If a selection field existed before rotation, has it retained the same visible choice? Layout and state should not be confused. A menu that changes shape can still represent the same selection. Conversely, an unchanged title does not prove every field was preserved. Compare the particular fields that matter to the reader's current task.

Rotate back to test the account

Return to portrait without pressing Continue. In our sample, Rules reappears as a full tab, the text wraps into more lines and the button remains reachable after scrolling. The selected task has not changed in this sequence. The reversible layout change supports the explanation that presentation adapted to available space. It does not establish how another phone will behave or whether an unrelated issue is fixed; the finding belongs to this observed page and sequence.

A different result deserves a different report. If rotation returns the reader to a home page or clears a previously visible selection, say so. That concerns a navigation or state change, not merely a compact menu. We would preserve the before state, the rotation action and the after state rather than repeatedly turning the phone and losing track. One clear reproduction can be more informative than many unrecorded attempts with different tabs open each time.

For a Jaiho91 display discussion, a useful pair of images includes matching page headings and orientation labels. Add short observations such as “Continue appears after scrolling in landscape” or “Rules is inside menu”. Avoid cropping away the very navigation area under discussion. Irrelevant personal details can be excluded, but enough of the interface must remain to locate the control. A close-up of blank space rarely explains which part of the page the reader expected there.

Our sample ends with the original task intact: Rules remains selected, its text is readable and Continue can be reached. What seemed like removed information was a shorter navigation presentation plus content outside the initial view. The Jaiho91 lesson is resolved through a complete sequence, not a guess from one screenshot. Turning the phone changed where information was visible; checking the same page established which information and choices still belonged to the task.