Skip to content
WM KeyboardWM Keyboard
Accessibility

Settings A–Z

How the settings app is organized: six home-screen groups, a search screen that indexes almost every row, and a map to every screen in this section.

WM Keyboard’s settings app opens to a Home screen with fifteen rows sorted into six groups. Tap any row to open its screen, or tap the magnifier at the top to search across almost everything in one field.

The Home screen: Typing, Keyboard, Features, Accessibility, Data and About, each its own card.

The Home screen: Typing, Keyboard, Features, Accessibility, Data and About, each its own card.

Home has no toggles of its own; it’s pure navigation, plus the setup card pinned above the groups. Each row below opens one screen, documented on its own page in this section:

Typing

  • Typing — autocorrect, suggestions, gestures
    • Dictionaries & words — personal dictionary, custom word lists, the blacklist, emoji keywords; a sub-screen reached from both Typing and Emoji, not a Home row of its own
  • Key press — haptics, key popup, long-press shortcuts
  • Languages — installed languages and layouts

Keyboard

Features

  • Emoji — suggestions, emoji row, emoji style, favourites
  • Tools — the master tool list; each tool’s own screen is documented on its guide page, not here
    • Phone number formats: the clipboard’s phone-number masks, reached from Tools → Clipboard; the one per-tool sub-screen with a page here, because the mask syntax needs the room
  • Addons — repositories, installed addons, sticker packs, and the plugin manager (the sticker-pack and plugin managers are also addon-install destinations, so they’re covered here rather than under Tools)

Accessibility

  • Accessibility — contrast, colour vision, TalkBack, reduced motion

Data

  • Privacy — on-device learning, incognito
    • Permissions: everything the keyboard can reach and what it holds right now; a sub-screen off the top row of Privacy, not a Home row of its own
  • Backup & restore: export your settings to a file, restore one, or set up the automatic backup that does it on a timer

About

  • About & diagnostics — version, licence, open-source notices, updates, storage, diagnostics
    • Statistics — how much you type, and the switch that stops the counting

That’s 22 screens in total: the 15 Home rows, plus seven sub-screens (Dictionaries, Themes, Fonts, Icons, Permissions, Statistics, Phone number formats) that earned their own page instead of folding into a parent’s.

Tap the magnifier on Home to open a full-screen search field, which grabs focus immediately so you can start typing without another tap. Before you type anything it shows a hint: Search every setting by name (like “haptic”, “number row”, or “incognito”), or by the tool it belongs to.

Typing a query in Settings search — each result carries a breadcrumb to the screen it lives on.

Typing a query in Settings search — each result carries a breadcrumb to the screen it lives on.

Every word you type has to match something for a result to show up: searching “emoji row” won’t surface every row that merely mentions emoji, only ones that match both words. Results rank exact and prefix title matches above ones that only match the description, and each one shows a breadcrumb (like “Tools › Camera”) under its title so you know where it lives before you tap it.

Tapping a result takes you straight to the owning screen, scrolls to that exact row, and gives it a brief highlight so you don’t have to hunt for it: the search doesn’t just open the right screen, it points at the right row. Toolbar tools are searchable too: every enabled tool gets an entry automatically, so a newly added tool is findable the moment it ships, without a docs or search-index update.

Any row you’ve moved off its shipped value grows a small restore button next to its control. Tap it and that one setting goes back to the default, without touching anything else on the screen.

The button only shows up on rows you’ve actually changed, so it doubles as a way to see what you’ve customised: scroll a screen, and the rows with a restore button are the ones that no longer match the app’s own defaults.

A few rows work differently, because “the default” means something else there:

  • Per-screen sizes (landscape, unfolded, tablet) don’t reset one slider at a time. The whole override goes back with Follow portrait at the bottom of that screen’s group, since the default for those screens is “whatever portrait does”.
  • Keyboard modes, AI actions and custom layouts are things you made, not settings the app shipped. A mode’s inherited values come back by switching its own override toggles off, and a custom layout or action is reverted by deleting it.
  • Lists you built (pinned tools, enabled languages, sticker packs) have their own reset actions where one exists, like Reset pinned tools on the Tools screen.
  • The whole app goes back at once from Backup & restore.

Two related topics live on their own pages rather than here:

  • The setup card that gets WM Keyboard enabled and active, and the first-run onboarding wizard. See Enable the keyboard.
  • Opening a settings screen from a launcher shortcut or a wmkeyboard://settings/ link. See Deep links & launcher shortcuts. Only six routes are linkable this way: Typing, Appearance, Themes, Languages, Tools, and Search.
  • Per-tool settings live on each tool’s own guide page under Tools, cross-linked from the Tools screen page, not documented separately here. Three screens are exceptions. The sticker-pack manager and plugin manager are both opened from a tool’s detail screen and from Addons (installing a sticker pack or a plugin addon lands you in the same manager), so they’re covered under Addons instead. The clipboard’s Phone number formats gets a page of its own because its mask syntax is reference material, not a guide.
  • Screen transitions are a quick 220ms slide-and-fade. If you’ve turned on reduced motion under Accessibility, that collapses to an instant cut with no animation at all.
  • Every screen in this section is reachable from Home in one or two taps; nothing here requires a hidden gesture or a developer option to reach.