One-handed layout and font evidence

Jianlai one-handed width: check percentages and placement only on a nonfloating iPhone keyboard

Use one fixed input card to compare a full-width baseline with left- and right-handed states, changing only one available width value. Deliver percentage, available-frame and actual-input records. The official image explicitly limits this width setting to nonfloating iPhone keyboards; seeing its setting on iPad does not establish the same effect there.

English translation of the Chinese original, translated on . Original publication dates, attribution, code and version notes are retained.

Use one fixed input card to compare a full-width baseline with left- and right-handed states, changing only one available width value. Deliver percentage, available-frame and actual-input records. The official image explicitly limits this width setting to nonfloating iPhone keyboards; seeing its setting on iPad does not establish the same effect there.

1. Verify device conditions before following the iPad image

In an ordinary note on your own iPhone, confirm the visible keyboard is Jianlai and record device category, installed version, orientation and keyboard state. Although the high-resolution settings image is presented on iPad, its note limits one-handed width to nonfloating iPhone keyboards. Without a suitable phone, retain image reading and calculations while leaving device comparison pending; an ineffective iPad value is not a diagnosed fault. Hold theme, language and layout fixed, without also rotating or changing windows. If only a physical keyboard is available, wait for a real on-screen keyboard instead of substituting hardware input. Preserve existing documents and use a new private practice draft.

2. Save full-width input and the original value

First enter the card below in a confirmed full-width state; otherwise label the baseline type unknown. Commit and check Chinese, uppercase letter, digits and one ASCII space. In the installed keyboard settings, find the actual one-handed-width label and record its original value and percent sign. Eighty in the published image is an example, not every device’s current value. Record full-width mode, one-handed mode and its width parameter separately; seeing eighty does not prove the whole keyboard has already narrowed. Mark an unknown original value rather than infer it from a reset. Save committed text before settings and summon the keyboard again on return, without assuming pending candidates survive page changes.

山河 R31

3. Distinguish available keyboard width from device pixels

On paper, let the available keyboard frame be three hundred sixty consistent units wide. Eighty percent gives two hundred eighty-eight, leaving seventy-two. This illustrates a fraction of available width, not a claim about a device’s screen size or measured keycaps or touch targets. If eighty-five percent is actually selectable, the same frame gives three hundred six, leaving fifty-four and increasing width by eighteen. The example does not require either value in every installation and does not scale height. Without measured units, use states and relative edges rather than convert screenshot pixels directly into app layout units.

paper W = 360 units
80%: width 288, remainder 72
85%: width 306, remainder 54
width increase: 18 units

4. Observe left-handed placement at the original value

Following the image’s reference to keyboard quick settings, select a left-handed state only through a recognizable actual control. If unavailable, stop that item instead of inventing an icon position. Keep the original width, return to the same note and re-enter the card, observing the letter region, candidates and return-related control. Record regions separately if they do not scale alike; uniform scaling is not assumed. Identify keys rather than tap old full-width coordinates. Check committed text against the card, not placement alone. Stop and retain evidence if legibility or accidental input becomes uncertain instead of treating random taps as adaptation training.

5. Change placement first, then width separately

After retaining the left result, switch only to an actually available right-handed state, keeping width, language and theme, then reidentify controls and input. Record left/right anchoring from visible edges rather than infer a width change from movement. In a separate width trial choose one supported nearby value while staying right-handed, then compare in the same draft. If the selectable value is not eighty-five, record and recompute it rather than claim the example was applied. Placement and percentage are separate factors. Do not change both together and attribute everything to width, or invent drag-to-resize behavior absent from the interface.

6. Check text and reachability without claiming speed gains

For each performed state, check actual card characters, candidate commitment and access to essential controls, separately recording the main keys, candidates and edges. A narrower or moved key does not prove better error rates, speed or ergonomics; no timed typing or touch-area measurement is performed. For host wrapping, check source characters instead of attributing a newline to one-handed mode. Missing saved input first calls for document and commitment checks, not another width change. Preserve three evidence types: parameters show choices, display shows observations and body text shows committed input. None substitutes for universal passes in the others.

7. Diagnose device, mode and parameter separately

For a changed parameter without visible effect, first check the nonfloating iPhone condition, then actual one-handed mode and extension identity. Changed anchoring and unchanged width can coexist; blank edges alone do not establish a lost value. Restore accidentally altered font or theme separately before a new trial, rather than reset everything. If quick settings cannot be found, retain installed version and visible interface instead of transferring Apple system-keyboard gestures to Jianlai. With an unknown original width, restore a known-usable replacement and label it as such, not an exact restoration. Unperformed comparisons remain blank, with no iPad screenshot substituted for an iPhone observation.

8. Restore daily use and retain the width map

Restore the recorded daily mode and width through confirmed controls, then enter and reopen the saved card in an ordinary note. Pass restoration and saving only if performed. Deliver original value, left/right positions, actual new value, paper calculations and observed text, listing untested devices or modes. Explain that the percentage refers to available keyboard width and that placement is a separate condition. Eighty is not a fixed size valid on every iPad. New devices, orientations, versions or layouts require fresh scope checks rather than a universal one-handed compatibility or long-term performance certification.

iPad input-space map; Settings recovery baseline.

Checked on 18 November 2026: Apple’s Finland lookup and China lookup both list Jianlai 1.0.5, requiring iOS / iPadOS 16.0 or later. The official store describes themes, backgrounds, fonts and multilingual input. Use controls actually present in the installed version; system editing and host processing are distinguished separately. These are repeatable instructions and paper expectations, not claims of completed device input, host compatibility or format-parser tests.

Method references: Official Apple keyboard-settings image at full reading size.