Enabling and appearance
Switch Jianlai across two ordinary editors and identify the active keyboard
Compare the system keyboard and Jianlai with one short passage, distinguishing enabled from currently active.
On this page
Compare the system keyboard and Jianlai with one short passage, distinguishing enabled from currently active.
1. Preserve a known starting state
Confirm that both the system keyboard and Jianlai are enabled. Prepare two ordinary editable locations you can save, such as a note and a draft; no test message needs to be sent. Record both host names and their current keyboards so a switch in one app is not attributed to another. Preserve existing text and create a small practice area. Replace a read-only view or special field with a normal editor first instead of attempting to cover every app immediately.
2. Fix one passage for both keyboards
Create a short passage containing Chinese, ordinary punctuation and a few digits, and enter it first with the familiar system keyboard. Save it as a content reference. Avoid real verification codes, addresses or private chats. This is not a precise candidate-speed benchmark or a test of obscure vocabulary. Record candidate selection versus direct entry, then check the final document with Jianlai. The two keyboards need not present identical candidate orders for the same correctly inserted text.
3. Select Jianlai through the actual switcher
In the first ordinary editor, invoke the keyboard and choose Jianlai through the available system switcher. A globe-key hold may expose a named list; use the actual interface if it differs, without prescribing a tap count for every device. Pause to identify layout, name or input behaviour before typing. Presence in the enabled list is not evidence that Jianlai is active, and similar theme colours do not establish identity. If uncertain, inspect the switcher again rather than record an expected selection as fact.
4. Check insertion, then return to the system keyboard
Enter the same passage with Jianlai and verify that candidates, punctuation and digits reached the document. Switch back through the visible control and add a practice marker. This confirms a usable return path, not a need to delete or reinstall Jianlai. Keep both passages identifiable by input method. A changed keyboard appearance without insertion is not the complete task. If text appears at the wrong location, adjust the insertion point before comparing content instead of immediately blaming keyboard switching.
5. Re-identify the state in the second host
Open the second ordinary draft and identify its current keyboard before deciding whether to switch. Jianlai’s use in the first editor does not guarantee the second inherits it; host, system and field type can affect presentation. Enter the same passage, make one deletion/correction and save. Return to the first document to verify its text. This covers two specific locations, not a universal default or cross-app document synchronisation by Jianlai. Record any keyboard-memory behaviour as an observation rather than a promise.
6. Separate changing keyboards from changing languages
Switching keyboard extensions is different from changing an input language or Chinese layout inside Jianlai. Keep one language and layout here while comparing system keyboard versus Jianlai; use the layout lesson for nine-key versus 26-key input. If a language label changes, record the control used. English candidates alone do not prove a switch to the system keyboard. Theme changes are not a unique identity signal either. Separating tool, language and appearance lets you explain what actually changed.
7. Diagnose a missing entry by scope
If Jianlai is missing from the switcher, inspect the enabled list. If only one location fails, compare an ordinary field in that host, then another host. Do not try to bypass secure or phone-pad boundaries by enabling every permission. If Jianlai appears but text is not inserted, inspect candidate confirmation and document focus. For failures in both hosts, retain version and actual symptoms before clearing anything. Change one host or field condition per round; unknown causes do not establish incompatibility with all software.
8. Retain evidence from both hosts
Return to your preferred keyboard and confirm both practice texts remain accessible. Save host, field type, switching control, active identity and document result. Acceptance includes explaining why enabled-list presence and active use need different evidence, and how to return to the original input method. Leave untried apps and fields pending. Repeat the small comparison after relevant system, host or keyboard-setting changes. Success in two editors does not certify one permanent default state throughout every app.
Related tutorials and sources
First enablement, Input and interface languages.
Checked on November 15, 2026 against Apple public lookup and the official App Store information and screenshots it lists: version 1.0.5, requiring iOS / iPadOS 16.0 or later, with identity and version cross-checked against China lookup. Tasks use published capabilities; identify actual controls in your installed version. External records are acceptable. Keep expectations separate from observations; no physical-device or universal input-environment test is claimed.
