Documentation
How to embed PressboardKit in your own iOS keyboard extension: installation, the action and styling APIs, and the full 51-parameter behaviour reference.
PressboardKit is a keyboard engine, not a keyboard app. It draws a resolved layout and reports what the user did; your extension owns the text document and decides what to insert. Every behaviour is a parameter whose default reproduces the native iOS keyboard, so you opt out of things rather than opting in to get parity.
If you want the short version: the PressboardKitApp module assembles the whole keyboard for you, and a working extension is a subclass with one overridden method.
Start here
Introduction
What PressboardKit is, what it deliberately is not, and how the five modules divide the work.
Installation
Adding the package, choosing which modules to link, setting up the keyboard extension target, and sharing settings through an App Group.
Quick start
A working keyboard extension end to end — the controller, the settings screen that drives it, and an in-app preview you can type into.
Behaviour reference
Every property on KeyboardBehavior — name, type, default, and what it does — grouped the way the type itself is.
Getting started
What the engine is, how to add it, and a keyboard you can paste and run.
- IntroductionWhat PressboardKit is, what it deliberately is not, and how the five modules divide the work.
- InstallationAdding the package, choosing which modules to link, setting up the keyboard extension target, and sharing settings through an App Group.
- Quick startA working keyboard extension end to end — the controller, the settings screen that drives it, and an in-app preview you can type into.
- LicensingPressboardKit is free, but it is licensed. What you have to do today, what the engine does about it, and what it never does.
Guides
One page per subsystem — actions, theming, layouts, autocomplete, emoji, performance.
- Keyboard actionsEvery user intent the engine reports, what it means, and how a host turns it into an edit on the text document.
- ThemingThe style seam, the six built-in themes, building a palette of your own, and why the native keyboard's backdrop has to stay clear.
- Layouts and languagesHow a layout is resolved from context, the five key arrangements, adapting to the edited field, and what adding a language actually involves.
- AutocompleteThe suggestion provider protocol, the bundled dictionary, autocorrection through a layered spell checker, next-word prediction, and slide-to-type.
- EmojiThe emoji panel — showing it, sharing recents across app and extension, skin tones, and full-text search.
- PerformanceThe extension memory budget, keeping the key grid off the per-keystroke render path, sizing the input view, and measuring a process you cannot attach to.
Reference
The complete parameter surface, and the questions integrators ask first.