From browser to input app

Install with a way back.

Your download is a configuration ZIP, not an input-method installer. Use it with the target app shown in the workbench.

Device verification is still pending. Browser composition and package checks do not establish native installation or rollback on your device. Keep your current input method available while testing.

Choose the right package

Desktop Rime
For an existing Rime client, such as Weasel on Windows, Squirrel on macOS, or a Rime integration on Linux. Use the official Rime client links and configuration guide for the user directory and deployment action.
Yuanshu
For the Yuanshu app. Packages include schema resources and a matching keyboard skin. Compact layouts marked “Yuanshu only” are not desktop Rime packages.

Before import

  1. Keep a recoverable copy. Back up your input app's current user configuration and personal dictionaries. Record the app/version and where the backup lives. Do not replace files you cannot restore.
  2. Inspect the ZIP. Unzip into a separate folder. Read the included instructions and preview images. Review default.custom.yaml and any name collisions before merging; do not overwrite your entire user directory with the package.
  3. Import using your app. For desktop Rime, merge the intended configuration and redeploy through your client. For Yuanshu, follow its schema and skin import workflow. This guide does not change your operating system or install a client.

Accept it on the actual device

Use a temporary document and your own sample phrases. Check candidate selection, deletion, shift, punctuation, switching back to your existing input method, and any gestures you need. Browser previews cannot verify native keyboard switching, dismissal or the system emoji picker.

If something goes wrong

Switch to your previous input method first. Follow your client's supported restore procedure to return the backed-up configuration and redeploy if required. Test the old configuration before resuming everyday typing. Keep the downloaded package separate while diagnosing the problem; do not delete personal dictionaries as a troubleshooting shortcut.

Record the package, selected layout, target app/version, expected input and actual result. A failed native test remains a failed test even when the browser preview works.

Need a different layout?

Prepare a customization brief with concrete examples. The brief is a starting point for source work, not a completed custom keyboard.