Compare Jianlai themes: preview, active keyboard and restoration

Compare two visible themes with the same text, keeping previews separate from active-keyboard results.

1. Preserve the starting theme and text

Identify the current Jianlai theme by its name and recognisable colours, then prepare a nonsensitive passage. Preserve the original rather than delete or overwrite a personalised style. If configuration export is unavailable, record key settings externally without claiming a full theme backup feature. Include ordinary characters, digits and punctuation for label and candidate readability. Change only built-in themes here, retaining font, layout and input language so several simultaneous changes do not obscure the comparison.

2. Choose two actual built-in options

Official screenshots show a built-in theme list and preview/edit entries. Follow the installed version’s actual names and count. Choose two distinguishable readable options and record their names. Do not assume every pictured theme is currently free or permanently available. If an option has an additional acquisition condition, read its real explanation and choose an already available alternative for this exercise; no unknown purchase is needed. Preserve the list and do not invent a theme name from an online example.

3. Limit preview conclusions to what is shown

Open the first visible preview and inspect key labels, background, candidate area and space bar. A preview may use one layout or fixed text; it does not certify every language and orientation. Leave missing digits, symbols or long candidates for actual input rather than imagine them. For a strong pattern, check whether text merges with the background instead of judging only the cover’s attractiveness. This comparison concerns a usable typing interface, not a subjective ranking of theme artwork.

4. Apply it and check an ordinary note

Use the installed version’s identifiable apply or enable action, return to an ordinary note and confirm Jianlai is active. Enter the prepared passage and compare the actual theme with its preview. Check candidate insertion and deletion rather than focus only on colour. If only the containing-app preview changed, establish whether the theme was applied, the keyboard redisplayed and the correct extension selected before diagnosing damage. Do not invent a save button; record the real control you used.

5. Change only the appearance for the second round

Save the first result before selecting the second theme. Keep note, language, layout and passage fixed. Inspect ordinary labels, digits/symbols and candidate text only on pages actually visited. A theme change is not an input-language change. Larger-looking keycaps do not establish enlarged touch targets without evidence. Record specific readable or difficult labels and colour relationships for both options, rather than unsupported claims that a theme is more advanced or makes typing faster.

6. Record light/dark comparisons separately

Finish the two-theme comparison before optionally changing the system’s light/dark appearance in a separate round. Published themes and appearance examples do not mean every theme behaves identically in every system state. Inspect actual controls for system-following versus independent choices. Record system state, theme state and active keyboard separately. Changed screen brightness alone does not prove changed theme colours. Defer this optional comparison when inconvenient; testing every theme at every brightness is not required.

7. Separate application and readability problems

If the active keyboard is unchanged, check extension identity, theme selection and application. If colours change but text is unclear, compare foreground/background on the same passage. If only one page is affected, record that layout and page. Reinstallation or deleting all personal styles is not the first comparison for these distinct problems. Restore the original theme and change one appearance condition at a time. A screenshot describes one display, not every key or long-term stability; insertion failure also needs document-focus and candidate-confirmation checks.

8. Restore the original and deliver the comparison

Restore the recorded original or deliberately chosen final theme. Redisplay Jianlai and enter a short marker to verify the everyday state. Deliver both real theme names, preview observations, active-input results and restoration. Leave untested layouts, languages and system states unknown. Acceptance includes explaining preview, application and document insertion as three steps rather than saving an attractive cover. Re-identify names and conditions after theme-list or device changes; two options do not certify every built-in theme on physical devices.

Related tutorials and sources

Background readability, Font and size.

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.

Official Apple screenshot: built-in themes.